Description of problem:
Swift deployed by tripleo using OSPd deploys single swift-object-server, swift-container-server, and swift-account-server processes which can/will affect the scalability and performance of your Swift. General Swift tuning guide recommends a one to one ratio of physical cpu to process counts for these processes with a single concurrency for the background tasks with ther exception of the replicators [0]
Version-Release number of selected component (if applicable):
OSP10
How reproducible:
Always
Steps to Reproduce:
1. Deploy overcloud and review process counts of the swift services
2.
3.
Actual results:
Expected results:
Additional info:
Related bug https://bugzilla.redhat.com/show_bug.cgi?id=1411391
[0] http://docs.openstack.org/developer/swift/deployment_guide.html#general-service-tuning
This may be covered by some WIP and doc changes coming, over to Swift to comment/triage.
Comment 2Christian Schwede (cschwede)
2017-08-25 10:33:26 UTC
It's possible to set the workers count using a template with the proposed patch for puppet-swift applied like this:
parameter_defaults:
ControllerExtraConfig:
swift::storage::all::account_server_workers: 3
swift::storage::all::container_server_workers: 5
swift::storage::all::object_server_workers: 7
Comment 3Christian Schwede (cschwede)
2017-08-25 11:43:07 UTC
Also proposed a t-h-t patch to simplify this:
parameter_defaults:
SwiftAccountWorkers: 3
SwiftContainerWorkers: 5
SwiftObjectWorkers: 7
Comment 4Christian Schwede (cschwede)
2017-09-21 15:35:51 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, 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/RHEA-2018:2086