← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1631384] [NEW] New option for num_threads for state change server

 

Public bug reported:

https://review.openstack.org/379578
Dear bug triager. This bug was created since a commit was marked with DOCIMPACT.
Your project "openstack/neutron" is set up so that we directly report the documentation bugs against it. If this needs changing, the docimpact-group option needs to be added for the project. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to.

commit 5c1516e1fb07bb3e026a3569396567c3907b31c6
Author: venkata anil <anilvenkata@xxxxxxxxxx>
Date:   Tue May 17 16:30:13 2016 +0000

    New option for num_threads for state change server
    
    Currently max number of client connections(i.e greenlets spawned at
    a time) opened at any time by the WSGI server is set to 100 with
    wsgi_default_pool_size[1].
    
    This configuration may be fine for neutron api server. But with
    wsgi_default_pool_size(=100) requests, state change server
    is creating heavy cpu load on agent.
    So this server(which run on agents) need lesser value i.e
    can be configured to half the number of cpu on agent
    
    We use "ha_keepalived_state_change_server_threads" config option
    to configure number of threads in state change server instead of
    wsgi_default_pool_size.
    
    [1] https://review.openstack.org/#/c/278007/
    
    DocImpact: Add new config option -
    ha_keepalived_state_change_server_threads, to configure number
    of threads in state change server.
    
    Closes-Bug: #1581580
    Change-Id: I822ea3844792a7731fd24419b7e90e5aef141993
    (cherry picked from commit 70ea188f5d87c45fb60ace8b8405274e5f6dd489)

** Affects: neutron
     Importance: Undecided
         Status: New


** Tags: doc neutron

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1631384

Title:
      New option for num_threads for state change server

Status in neutron:
  New

Bug description:
  https://review.openstack.org/379578
  Dear bug triager. This bug was created since a commit was marked with DOCIMPACT.
  Your project "openstack/neutron" is set up so that we directly report the documentation bugs against it. If this needs changing, the docimpact-group option needs to be added for the project. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to.

  commit 5c1516e1fb07bb3e026a3569396567c3907b31c6
  Author: venkata anil <anilvenkata@xxxxxxxxxx>
  Date:   Tue May 17 16:30:13 2016 +0000

      New option for num_threads for state change server
      
      Currently max number of client connections(i.e greenlets spawned at
      a time) opened at any time by the WSGI server is set to 100 with
      wsgi_default_pool_size[1].
      
      This configuration may be fine for neutron api server. But with
      wsgi_default_pool_size(=100) requests, state change server
      is creating heavy cpu load on agent.
      So this server(which run on agents) need lesser value i.e
      can be configured to half the number of cpu on agent
      
      We use "ha_keepalived_state_change_server_threads" config option
      to configure number of threads in state change server instead of
      wsgi_default_pool_size.
      
      [1] https://review.openstack.org/#/c/278007/
      
      DocImpact: Add new config option -
      ha_keepalived_state_change_server_threads, to configure number
      of threads in state change server.
      
      Closes-Bug: #1581580
      Change-Id: I822ea3844792a7731fd24419b7e90e5aef141993
      (cherry picked from commit 70ea188f5d87c45fb60ace8b8405274e5f6dd489)

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1631384/+subscriptions


Follow ups