Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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.

Description of problem:

Very big library (complete export of 1.5Tb). When trying to generate an incremental export of the library (all repositories), a very long time is spent on some DB queries. 

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


How reproducible:
Unsure. All the time on customer's environment

Steps to Reproduce:
In theory, that's what customer did:

1. Generate complete export of big library
2. After a while, generate incremental exports using fs-export (syncable method)


Actual results:
Export works, but is very slow. Last test from customer took 24h running. Result had 3.5Gb of data (which is not wrong, just time to generate it is considered too long)

Expected results:

Export to finish faster.

Additional info:

I don't know that this is one issue, but perhaps a combination of https://github.com/pulp/pulpcore/pull/4161 (which is already tracked by BZ https://bugzilla.redhat.com/show_bug.cgi?id=2226950) and https://github.com/pulp/pulpcore/issues/3969 ?

We have that work in progress currently for other stakeholders anyway, so we can check back in shortly when it is finished and see if the situation is improved.

These 3 BZs ought to be tested together as they involve essentially the same setup process

https://bugzilla.redhat.com/show_bug.cgi?id=2238906
https://bugzilla.redhat.com/show_bug.cgi?id=2228592 (this one)
https://bugzilla.redhat.com/show_bug.cgi?id=2244521