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 2238915 - Very large content import fails with subtask error
Summary: Very large content import fails with subtask error
Keywords:
Status: CLOSED DUPLICATE of bug 2226950
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Pulp
Version: 6.11.5
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.15.0
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-09-14 10:02 UTC by Keith Williams
Modified: 2024-02-07 17:00 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-10-12 00:06:32 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 2238914 0 unspecified CLOSED Pulp workers taking days to import large content-export 2023-10-12 00:05:28 UTC
Red Hat Issue Tracker SAT-20085 0 None None None 2023-09-14 10:04:02 UTC

Internal Links: 2238914

Description Keith Williams 2023-09-14 10:02:18 UTC 
Description of problem:
During very large (2.1TB) content-export, the import fails after about 12 days with error "7 subtask(s) failed for task group /pulp/api/v3/task-groups/....."

This BZ is raised in relation to support case #03609607.

Version-Release number of selected component (if applicable):
6.11.5.4

How reproducible:
Everytime

Steps to Reproduce:
1. place 2.1TB tar.gz file in to /var/lib/pulp/imports
2. run command: time hammer content-import version --organization-id=1 --path/var/lib/pulp/imports/z1d-export/


Actual results:
import fails after about 12 days with error "7 subtask(s) failed for task group /pulp/api/v3/task-groups/....."

Expected results:
import does not fail

Additional info:
Please see the support case #03609607 which has a lot more contextual information.
Please see https://bugzilla.redhat.com/show_bug.cgi?id=2238914.
Test of importing a 2.1TB content export that contains:
Repositories: 151 (both Red Hat and 3rd party repos)
RPM Packages: >200,000
Size of export: 2.1TB
I did find a knowledgebase article https://access.redhat.com/solutions/6967697 which relates to a lack of memory. This was fixed in 6.11.2 and we are running 6.11.5.4. Also on this host it has 24cpu and 192GB of memory and no out of memory issues were observed when the import failed.
Comment 2 Ina Panova 2023-10-03 14:20:24 UTC 
I went through the customer case - I did not find any attachments to it with any additional info as well went through the comments searching for the logs or tracebacks.
To facilitate the bugzilla investigation and invest the time into its resolution - can logs, tracebacks, task info output be shared directly on the BZ?
Comment 3 Daniel Alley 2023-10-12 00:06:32 UTC 
The main issue here is 2226950

We're working on some additional memory improvements beyond that that will be covered by a new BZ

*** This bug has been marked as a duplicate of bug 2226950 ***
Note You need to log in before you can comment on or make changes to this bug.