1998309 – Change Puma defaults to match recommendations from Puma documentation

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.

Bug 1998309 - Change Puma defaults to match recommendations from Puma documentation

Summary: Change Puma defaults to match recommendations from Puma documentation

Keywords:
Status:	CLOSED ERRATA
Alias:	None
Product:	Red Hat Satellite
Classification:	Red Hat
Component:	Installation
Sub Component:
Version:	6.8.0
Hardware:	Unspecified
OS:	Unspecified
Priority:	unspecified
Severity:	high
Target Milestone:	6.9.6
Assignee:	Eric Helms
QA Contact:	Devendra Singh
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2021-08-26 19:35 UTC by James Jeffers
Modified:	2021-09-21 14:37 UTC (History)
CC List:	5 users (show)
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Clone Of:	1998291
Environment:
Last Closed:	2021-09-21 14:37:27 UTC
Target Upstream Version:
Embargoed:

Attachments	(Terms of Use)

Links
System	ID	Private	Priority	Status	Summary	Last Updated
Foreman Issue Tracker	33277	0	None	None	None	2021-08-26 19:35:58 UTC
Red Hat Product Errata	RHBA-2021:3628	0	None	None	None	2021-09-21 14:37:32 UTC

Description James Jeffers 2021-08-26 19:35:45 UTC

+++ This bug was initially created as a clone of Bug #1998291 +++



--- Additional comment from  on 2021-08-26T18:44:50Z 

Created from redmine issue https://projects.theforeman.org/issues/33277

--- Additional comment from  on 2021-08-26T18:44:52Z 

Upstream bug assigned to ehelms

Comment 4 Devendra Singh 2021-09-13 14:47:39 UTC

Verified on 6.9.6 Snap2.

1- Created the base version of the Satellite setup using 6.9.4 GA template.
2- Checked the thread FOREMAN_PUMA_WORKERS, FOREMAN_PUMA_THREADS_MIN and FOREMAN_PUMA_THREADS_MAX and they were 2, 0, and 16 respectively.

# systemctl cat foreman.service
# /usr/lib/systemd/system/foreman.service
[Unit]
..........
..........
Environment=FOREMAN_PORT=3000
Environment=FOREMAN_PUMA_THREADS_MIN=0
Environment=FOREMAN_PUMA_THREADS_MAX=16
Environment=FOREMAN_PUMA_WORKERS=2

3- Ran the upgrade from 6.9.4 to 6.9.6 Snap2.
4- Upgrade completed successfully.
5- The CPU and Memory of this machine were 20Gig's of RAM and 6 Core CPU.
6- As per the puma documentation, the size of the worker should be a multiplication of 1.5, On this setup, we have 6 cores hence the worker count is 9 correct.

6 * 1.5 = 9

# ps -aux | grep puma
foreman  35613  0.3  2.7 997128 550276 ?       Ssl  03:33   1:20 puma 4.3.6 (unix:///run/foreman.sock) [foreman]
foreman  36247  0.0  3.4 1167712 707832 ?      Sl   03:34   0:15 puma: cluster worker 0: 35613 [foreman]
foreman  36254  0.1  3.4 1120788 694336 ?      Sl   03:34   0:37 puma: cluster worker 1: 35613 [foreman]
foreman  36262  0.0  3.3 1134368 685904 ?      Sl   03:34   0:10 puma: cluster worker 2: 35613 [foreman]
foreman  36270  0.0  3.4 1131160 711956 ?      Sl   03:34   0:10 puma: cluster worker 3: 35613 [foreman]
foreman  36278  0.0  3.3 1109400 691760 ?      Sl   03:34   0:15 puma: cluster worker 4: 35613 [foreman]
foreman  36285  0.0  3.4 1149776 701932 ?      Sl   03:34   0:15 puma: cluster worker 5: 35613 [foreman]
foreman  36290  0.0  3.3 1134832 691620 ?      Sl   03:34   0:14 puma: cluster worker 6: 35613 [foreman]
foreman  36299  0.0  3.4 1169760 697060 ?      Sl   03:34   0:12 puma: cluster worker 7: 35613 [foreman]
foreman  36304  0.0  3.4 1167712 701440 ?      Sl   03:34   0:13 puma: cluster worker 8: 35613 [foreman]
root     45946  0.0  0.0 112816   972 pts/0    S+   10:31   0:00 grep --color=auto puma

7. Checked the thread  FOREMAN_PUMA_THREADS_MIN and FOREMAN_PUMA_THREADS_MAX and they were equal.

# systemctl cat foreman.service
# /usr/lib/systemd/system/foreman.service
[Unit]
..........
..........
[Service]
Environment=FOREMAN_PUMA_THREADS_MIN=5
Environment=FOREMAN_PUMA_THREADS_MAX=5
Environment=FOREMAN_PUMA_WORKERS=9

Comment 9 errata-xmlrpc 2021-09-21 14:37:27 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Satellite 6.9.6 Async Bug Fix Update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2021:3628

Note You need to log in before you can comment on or make changes to this bug.