Project

Profile

Help

Issue #9406

Trivial OOM on sync for a particular Microsoft repo

Added by dalley about 1 month ago. Updated 1 day ago.

Status:
ASSIGNED
Priority:
High
Assignee:
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
3. High
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Sprint 108
Quarter:

Description

Syncing https://packages.microsoft.com/rhel/8/prod/ results in an OOM even on a box with ~10gb of available memory


Related issues

Related to RPM Support - Issue #9399: sync error: invalid memory alloc request sizeASSIGNED<a title="Actions" class="icon-only icon-actions js-contextmenu" href="#">Actions</a>

History

#1 Updated by dalley about 1 month ago

  • Subject changed from Triviai OOM on sync to Trivial OOM on sync

#2 Updated by dalley about 1 month ago

  • Related to Issue #9399: sync error: invalid memory alloc request size added

#3 Updated by dalley about 1 month ago

  • Subject changed from Trivial OOM on sync to Trivial OOM on sync for a particular Microsoft repo

#4 Updated by dalley about 1 month ago

  • Triaged changed from No to Yes
  • Sprint set to Sprint 105

#5 Updated by dalley about 1 month ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to dalley

In a non-Pulp reproducer that merely calls parses the metadata with createrepo_c using the same code as Pulp RPM, it's clear that for some reason in this case there is a pathological behavior with the custom hybrid iterative parser.

The traditional "all at once" parsing peaks at 900mb, the new iterative parser peaks around 600mb, but our custom parser blows through the 15.5gb available on my VM and triggers the OOM killer.

#6 Updated by rchan 29 days ago

  • Sprint changed from Sprint 105 to Sprint 106

#7 Updated by rchan 14 days ago

  • Sprint changed from Sprint 106 to Sprint 107

#8 Updated by rchan 1 day ago

  • Sprint changed from Sprint 107 to Sprint 108

Please register to edit this issue

Also available in: Atom PDF