Bug 1728420

Summary:	Add httpd LimitNOFILE setting or default file configuration during installation.
Product:	Red Hat Satellite	Reporter:	Mike McCune <mmccune>
Component:	Installer	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED WONTFIX	QA Contact:	Devendra Singh <desingh>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	Unspecified	CC:	ehelms, ekohlvan, mvanderw, ngupta, zhunting
Target Milestone:	Unspecified	Keywords:	Performance, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-08-10 21:37:00 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Mike McCune 2019-07-09 23:34:01 UTC

We have the ability to set LimitNOFILE for qdrouterd and qpidd but not httpd, this is required at scale.

eg:

qpid::open_file_limit: 65536
qpid::router::open_file_limit: 150100

we need to either just install a file by default on all installations into 

/etc/systemd/system/httpd.service.d/limits.conf

[Service]
LimitNOFILE=640000

or have a custom-heira override. Since this setting is harmless on all installations we can consider just doing this by default for all installs of Satellite 6.

Comment 3 Ewoud Kohl van Wijngaarden 2019-07-18 13:30:47 UTC

It would be helpful to know why we have this limit. There are multiple applications running. If it's because of Katello itself, then we don't need to apply it on the Foreman Proxy for example. It also goes the other way around if it's because of Pulp. When we move from Passenger to Puma + reverse proxy it would also impact how we apply this limit.

Comment 4 Mike McCune 2019-08-08 14:37:40 UTC

For the qpid/router tuning:

This is purely for the combination of Candlepin + Katello + Pulp and all the connected katello-agents combined usage of the QPID infrastructure. I don't think the shift to Puma would have any effect on qpid's resource use. 

For httpd, shifting to Puma may eliminate the need for this and I'd consider holding off on this specific installer tuning until we get to Puma.

Comment 6 Ewoud Kohl van Wijngaarden 2021-05-31 08:42:45 UTC

(In reply to Ewoud Kohl van Wijngaarden from comment #3)
> It would be helpful to know why we have this limit. There are multiple
> applications running. If it's because of Katello itself, then we don't need
> to apply it on the Foreman Proxy for example. It also goes the other way
> around if it's because of Pulp. When we move from Passenger to Puma +
> reverse proxy it would also impact how we apply this limit.

The change from mod_passenger to Puma landed in 6.9. In 6.10 Pulp 3 will land which switches from mod_wsgi to a standalone gunicorn setup. I do believe this will remove the need for tuning this since then there will be a lot less file handles open.

It should be noted that upstream has already dropped Pulp 2 and mod_passenger support.

Comment 7 Mike McCune 2021-07-13 21:54:48 UTC

Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.

Comment 8 Mike McCune 2021-08-10 21:34:00 UTC

Thank you for your interest in Red Hat Satellite. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this feel free to contact your Red Hat Account Team. Thank you.