Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1940678 - pulp3: excess memory consumption when importing errata during pulp3 migration
Summary: pulp3: excess memory consumption when importing errata during pulp3 migration
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Repositories
Version: 6.9.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: 6.9.0
Assignee: Justin Sherrill
QA Contact: Tasos Papaioannou
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-03-18 20:39 UTC by Justin Sherrill
Modified: 2021-04-21 13:26 UTC (History)
2 users (show)

Fixed In Version: tfm-rubygem-katello-3.18.1.22-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-04-21 13:26:20 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 32142 0 Normal New excess memory consumption when importing errata during pulp3 migration 2021-03-19 16:10:47 UTC
Red Hat Product Errata RHSA-2021:1313 0 None None None 2021-04-21 13:26:54 UTC

Description Justin Sherrill 2021-03-18 20:39:25 UTC 
Description of problem:

On a system with a LOT of repositories, during migration the sidekiq worker for dynflow will consume ~16GB, which is way too much. 

We need to look at breaking up the errata import process to not consume as much memory.

In this case, there were ~25,000 errata, and 21,153,436 errata <-> repo associations (the biggest issue)
Comment 1 Justin Sherrill 2021-03-18 20:40:08 UTC 
And here was we witnessed in /var/log/foreman/production.log:

2021-03-18T15:07:35 [E|bac|] failed to allocate memory (NoMemoryError)
 |
2021-03-18T15:07:35 [I|bac|] Task {label: Actions::Pulp3::ContentMigration, id: 91601a75-10d2-47bb-af1e-891c91efeb2e, execution_plan_id: ac7599d1-e114-42ec-9db4-02ae0eadb41d} state changed: stopped  result: warning
2021-03-18T15:07:35 [I|bac|] Task {label: Actions::Pulp3::ContentMigration, id: 91601a75-10d2-47bb-af1e-891c91efeb2e, execution_plan_id: ac7599d1-e114-42ec-9db4-02ae0eadb41d} state changed: stopped  result: warning


There was also a dynflow traceback in /var/log/messages, but that was likely more of a side effect
Comment 2 Justin Sherrill 2021-03-19 16:10:46 UTC 
Created redmine issue https://projects.theforeman.org/issues/32142 from this bug
Comment 4 Tasos Papaioannou 2021-03-29 20:39:10 UTC 
Verified on 6.9.0 snap 19.1.
Comment 7 errata-xmlrpc 2021-04-21 13:26:20 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: Satellite 6.9 Release), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2021:1313
Note You need to log in before you can comment on or make changes to this bug.