`listener_workers` not working

Bug #1522737 reported by Liyingjun
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Searchlight
Fix Released
High
Liyingjun

Bug Description

after setting listener_workers=2 in searchlight.conf, there is still only one searchlight-listener worker running

Liyingjun (liyingjun)
Changed in searchlight:
assignee: nobody → Liyingjun (liyingjun)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to searchlight (master)

Fix proposed to branch: master
Review: https://review.openstack.org/253973

Changed in searchlight:
status: New → In Progress
Changed in searchlight:
importance: Undecided → High
Changed in searchlight:
milestone: none → mitaka-2
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to searchlight (master)

Reviewed: https://review.openstack.org/253973
Committed: https://git.openstack.org/cgit/openstack/searchlight/commit/?id=d35dc3676a64d106f3eeacdf628449b869482785
Submitter: Jenkins
Branch: master

commit d35dc3676a64d106f3eeacdf628449b869482785
Author: liyingjun <email address hidden>
Date: Sun Nov 29 23:54:21 2015 +0800

    Set listener workers according to config

    Currently, the get_workers method always return 1, so config
    listener_workers will never work as expected. This patch adds
    the ability to specify number of workers for listener service.
    The default is equal to the number of CPUs available.
    Also, register searchlight.service.OPTS to group 'listener' in
    searchlight.listener.
    Remove not used options 'host' and 'http_timeout'.

    Change-Id: Ifc39d5eaab1a7b0239631aa1b2b6e0af3a07f0c9
    Closes-bug: #1522737
    Closes-bug: #1523639

Changed in searchlight:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.