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.
DescriptionPradeep Kumar Surisetty
2016-02-23 17:49:53 UTC
Description of problem:
Registered close to 2000 content hosts to satelitte server. tried multiple times concurrent connections as well ( 50, 100, 150, 200)
Noticed max number of java connections opened.
lsof | cut -d ' ' -f 1 | sort | uniq -c | sort -n | tail
364 sshd
944 qdrouterd
1052 Passenger
2305 postgres
2523 mongod
4340 httpd
7898 ruby
8767 celery
11574 qpidd
167041 java
[root@satserver elasticsearch]# ulimit -a | grep open
open files (-n) 1024
[root@satserver elasticsearch]#
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. Register content hosts in scale
2.
3.
Actual results:
Too many open connections
Expected results:
Expected to be lesser open connections
Additional info:
There is a lots of connections even when you are not at scale. I have Sat6 running for few days and have synced RHEL6 + RH Common repos and registered ~10 systems and I see this:
# lsof | cut -d ' ' -f 1 | sort | uniq -c | sort -n | tail
344 tuned
420 named
636 Passenger
720 qpidd
1950 postgres
1975 mongod
3521 ruby
4070 httpd
6489 celery
56592 java
# lsof | grep elastic | wc -l
40320
Description of problem: Registered close to 2000 content hosts to satelitte server. tried multiple times concurrent connections as well ( 50, 100, 150, 200) Noticed max number of java connections opened. lsof | cut -d ' ' -f 1 | sort | uniq -c | sort -n | tail 364 sshd 944 qdrouterd 1052 Passenger 2305 postgres 2523 mongod 4340 httpd 7898 ruby 8767 celery 11574 qpidd 167041 java [root@satserver elasticsearch]# ulimit -a | grep open open files (-n) 1024 [root@satserver elasticsearch]# Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Register content hosts in scale 2. 3. Actual results: Too many open connections Expected results: Expected to be lesser open connections Additional info: