Problem:
With pulp container running we received an error when a large number of concurrent connections from hosts pulling rpms for upgrades. This resulted in new connections to the pulp content failing until the container was restarted. Still investigating where the limitation was hit but with the default container with 2 workers is there a defined max expected concurrent consumer number?
Expected outcome:
All clients able to access the rpms without issue
Pulpcore version:
3.54.0
Pulp plugins installed and their versions:
“component”: “ansible”,
“version”: “0.21.5”,
“component”: “container”,
“version”: “2.20.0”,
“component”: “deb”,
“version”: “3.2.0”,
“component”: “gem”,
“version”: “0.5.1”,
“component”: “maven”,
“version”: “0.8.0”,
“component”: “ostree”,
“version”: “2.3.0”,
“component”: “python”,
“version”: “3.11.1”,
“component”: “rpm”,
“version”: “3.25.3”,
“component”: “certguard”,
“version”: “3.54.0”,
“component”: “file”,
“version”: “3.54.0”,
Operating system - distribution and version:
Red Hat Enterprise Linux release 9.4
Other relevant data:
Still investigating if it was perhaps a limitation on nginx, ulimit etc but when the limit was reached pulp status also failed with error:
Max retries exceeded with url: /pulp/api/v3/status/ (Caused by NewConnectionError(’<urllib3.connection.HTTPSConnection object at 0x7fd01a96ed90>: Failed to establish a new connection: [Errno 111] Connection refused’))
When container was restarted issues resolved and so far have remained stable.