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:
update_subscription_facet_backend_data upgrade steps takes too long with 6k hosts registered. It is still running, currently at >1 hour for 6k registered hosts on a HW: 24xIntel(R) Xeon(R) CPU X5650 @ 2.67GHz and 50GB RAM, load is slightly below 1.


Version-Release number of selected component (if applicable):
Upgrade from 6.2.6 to 6.2.7


How reproducible:
1 of 1


Steps to Reproduce:
1. Upgrade Satellite 6.2.6 with 6k content hosts registered (through
   4 capsules) to 6.2.7


Actual results:
It takes above 1 hour to execute step update_subscription_facet_backend_data, load is below 1.


Expected results:
Would be nice to have this step faster.

At the end, it look 105 minutes to perform update_subscription_facet_backend_data upgrade step.

Performance test team did not see this in recent runs with 6.2.11.  I am moving this to Closed CurrentRelease. Please feel free to reopen if this issue is seen again.