Issue #9406: Trivial OOM on sync for a particular Microsoft repo - RPM Support - Pulp

Actions

Send by e-mail Copy link

Issue #9406

closed

Trivial OOM on sync for a particular Microsoft repo

Added by dalley about 3 years ago. Updated almost 3 years ago.

Status:

CLOSED - NOTABUG

Priority:

High

Assignee:

dalley

Sprint/Milestone:

Start date:

Due date:

Estimated time:

Severity:

3. High

Version:

Platform Release:

OS:

Triaged:

Yes

Groomed:

Sprint Candidate:

Tags:

Sprint:

Sprint 111

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

Actions

Copy link

Updated by dalley about 3 years ago

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

Actions

Copy link

Updated by dalley about 3 years ago

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

Actions

Copy link

Updated by dalley about 3 years ago

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

Actions

Copy link

Updated by dalley about 3 years ago

Triaged changed from No to Yes
Sprint set to Sprint 105

Actions

Copy link

Updated by dalley about 3 years 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.

Actions

Copy link