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.

Created attachment 1153694 [details]
apache scale

Description of problem:

Every new host registration takes huge number of apache open connections on satellite. 

I started registering hosts in bunch of 50's concurrently to satellite.  After 700-800, satellite server rejects all new registrations due to lot of open apache connections. 

As shown in attachment, for every batch of 50, number of open apache connections increases. Once it reach 110 open apache connects, satellite stops accepting  any new registrations. 

 lsof | cut -d ' ' -f 1 | sort | uniq -c | sort -n | tail

<snip>
110534 httpd






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


How reproducible:


Steps to Reproduce:
1. Scale satellite 
2.
3.

Actual results:

There are too many apache open connections per registration. For every 50 host registrations about 4k-5k apache open connections are left.

Expected results:

Not many apache open connections
Additional info:

IN attchmanent: 

x axis: time
y axis: Number of open apache connections

Work around:  Increase number of apache connections limit

cat /etc/systemd/system/httpd.service.d/limits.conf
[Service]
LimitNOFILE=20000

systemctl daemon-reload
systemctl restart httpd

This is just a workaround. Would be interesting to find out why do we need these many apache connections

Hi Pradeep, is this a dupe of bug 1328984 ?

(In reply to Brad Buckingham from comment #3)
> Hi Pradeep, is this a dupe of bug 1328984 ?

yep

*** This bug has been marked as a duplicate of bug 1328984 ***