Bug 1651680

Summary:	Swift has too many worker processes
Product:	Red Hat OpenStack	Reporter:	Sai Sindhur Malleni <smalleni>
Component:	openstack-tripleo-heat-templates	Assignee:	Pete Zaitcev <zaitcev>
Status:	CLOSED EOL	QA Contact:	Mike Abrams <mabrams>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	14.0 (Rocky)	CC:	cschwede, mabrams, mburns, scohen, smalleni, stchen
Target Milestone:	---	Keywords:	Reopened, Triaged, ZStream
Target Release:	---
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:	2020-09-30 19:41:10 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 Sai Sindhur Malleni 2018-11-20 14:57:46 UTC

Description of problem:
Description of problem:
In OSP14, swift has number of workers set to number of cores for all its services like swift-proxy-server, swift-account-server, swift-container-server, swift-object-server.

On a 56 cores machines, we have 57 swift-proxy-server processes for example.
Ideally we should cap workers at min(cpu-cores/2, 12)


Version-Release number of selected component (if applicable):
OSP13

How reproducible:
100%

Steps to Reproduce:
1. deploy director with defaults
2.
3.

Actual results:
Too many swift processes

Expected results:
Max of 12 swift workers

Additional info:

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Christian Schwede (cschwede) 2018-11-28 14:58:00 UTC


*** This bug has been marked as a duplicate of bug 1647510 ***

Comment 3 Christian Schwede (cschwede) 2018-11-28 15:06:13 UTC

This can be also set by using some extra parameters during deployment, for example:

parameter_defaults:
  SwiftWorkers: 12
  SwiftAccountWorkers: 12
  SwiftContainerWorkers: 12
  SwiftObjectWorkers: 12

Comment 6 Sai Sindhur Malleni 2018-12-11 21:10:28 UTC

Christian,

But shouldn't we shipping with more conservative defaults?

Comment 7 Mike Abrams 2018-12-12 12:44:57 UTC

*** Bug 1651678 has been marked as a duplicate of this bug. ***

Comment 8 Christian Schwede (cschwede) 2018-12-12 12:50:39 UTC

(In reply to Sai Sindhur Malleni from comment #6)
> Christian,
> 
> But shouldn't we shipping with more conservative defaults?

Yes, for future versions we should do this and we can change the default. However, as mentioned earlier this might have a severe impact on customers if we change the default for an already shipped product and it gets applied automatically during an upgrade. In that case please use a different default like written in https://bugzilla.redhat.com/show_bug.cgi?id=1651680#c3

Comment 11 Sai Sindhur Malleni 2018-12-12 16:10:47 UTC

Christian, This bug is for OSP14 and we haven't yet shipped OSP14 right?

Comment 14 stchen 2020-09-30 19:41:10 UTC

Closing EOL, OSP 15 has been retired as of Sept 19, 2020