Bug 2029606

Summary:	[RFE]: Allow configuration of BACKLOG option in /usr/lib/systemd/system/foreman.socket
Product:	Red Hat Satellite	Reporter:	Taft Sanders <tasander>
Component:	Installation	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED MIGRATED	QA Contact:	Gaurav Talreja <gtalreja>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	6.9.7	CC:	ehelms, gtalreja
Target Milestone:	Unspecified	Keywords:	FutureFeature, MigratedToJIRA, Performance, Triaged
Target Release:	Unused	Flags:	bbuckingham: needinfo? (ehelms)
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-06-06 02:17:29 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:
Bug Depends On:	2022240
Bug Blocks:

Description Taft Sanders 2021-12-06 21:08:25 UTC

Description of problem:
For tuning, the default backlog option of 1024 is not large enough to handle the incoming requests. The option to tune this BACKLOG option is needed to survive updates/upgrades.

Version-Release number of selected component (if applicable):
foreman-service-2.3.1.25-2.el7sat.noarch

How reproducible:

Steps to Reproduce:
1.
2.
3.

Actual results:
BACKLOG key variable is reset with every update/reinstall of the foreman-service RPM

Expected results:
To have a custom hiera value to control this value and survive updates/upgrades

Additional info:

Comment 1 Eric Helms 2022-05-24 12:56:41 UTC

As a work around, you can place a systemd drop-in file with this parameter configured that will survive updates and reinstalls.

Comment 2 Eric Helms 2022-05-25 14:28:57 UTC

Also worth noting is to look at https://bugzilla.redhat.com/show_bug.cgi?id=2022240 which talks about how the BACKLOG parameter is gated by a kernel parameter and that the two must be adjusted in-sync with one another to notice a difference.

Comment 4 Brad Buckingham 2023-07-21 21:06:39 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 6 Brad Buckingham 2023-09-01 19:51:59 UTC

Based upon feedback during auto-closure, leaving this bugzilla open a while longer for additional investigation; however, it may be closed in a future iteration.

Comment 7 Eric Helms 2024-06-06 02:17:29 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.