Bug 1413157

Summary: Expose Tuning Swift Object, Container, Account server process counts
Product: Red Hat OpenStack Reporter: Alex Krzos <akrzos>
Component: openstack-tripleo-heat-templatesAssignee: Christian Schwede (cschwede) <cschwede>
Status: CLOSED ERRATA QA Contact: Mike Abrams <mabrams>
Severity: low Docs Contact:
Priority: medium    
Version: 10.0 (Newton)CC: aschultz, cschwede, jschluet, mabrams, mburns, pgrist, rhel-osp-director-maint, scohen, thiago, tshefi, tvignaud
Target Milestone: Upstream M1Keywords: Triaged
Target Release: 13.0 (Queens)   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: openstack-tripleo-heat-templates-8.0.0-0.20180122224017.el7ost puppet-swift-12.2.0-0.20180119083117.de58ee9.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-06-27 13:29:16 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:

Description Alex Krzos 2017-01-13 18:39:01 UTC
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):

How reproducible:

Steps to Reproduce:
1. Deploy overcloud and review process counts of the swift services

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

Comment 1 Paul Grist 2017-04-06 02:22:20 UTC
This may be covered by some WIP and doc changes coming, over to Swift to comment/triage.

Comment 2 Christian 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:

    swift::storage::all::account_server_workers: 3
    swift::storage::all::container_server_workers: 5
    swift::storage::all::object_server_workers: 7

Comment 3 Christian Schwede (cschwede) 2017-08-25 11:43:07 UTC
Also proposed a t-h-t patch to simplify this:

  SwiftAccountWorkers: 3
  SwiftContainerWorkers: 5
  SwiftObjectWorkers: 7

Comment 4 Christian Schwede (cschwede) 2017-09-21 15:35:51 UTC
Merged after release - moving to 13.

Comment 10 Tzach Shefi 2018-02-26 07:23:14 UTC
Still waiting on newer puddle
Last one I managed to deploy today, none sufficient yet > 2018-02-14.1

Comment 16 errata-xmlrpc 2018-06-27 13:29:16 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.