neutron

Spawn dedicated rpc workers for state reports queue

Bug #1505217 reported by Eugene Nikanorov
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
neutron
Fix Released
Medium
Eugene Nikanorov

Bug Description

This change will address a case when rpc workers are loaded with heavy requests, like l3 router sync and have no capacity to
process state reports. In such case agents will blink, rescheduling will occur, which will load neutron-server even more and potentially disrupt connectivity.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to neutron (master)

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

Changed in neutron:
status: New → In Progress
Eugene Nikanorov (enikanorov)
tags: added: neutron-core
Ihar Hrachyshka (ihar-hrachyshka)
Changed in neutron:
importance: Undecided → Medium
tags: added: loadimpact
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to neutron (master)

Reviewed: https://review.openstack.org/233605
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=678b431ba4be8ccf6e505b3dd8fb8e9465b82f83
Submitter: Jenkins
Branch: master

commit 678b431ba4be8ccf6e505b3dd8fb8e9465b82f83
Author: Eugene Nikanorov <email address hidden>
Date: Mon Oct 12 16:21:02 2015 +0400

    Spawn dedicated rpc workers for state reports queue

    By default spawn one additional rpc worker to process
    state report queue.
    State report queue will also be processed by regular
    rpc workers, but in case these workers are busy with
    processing heavy requests, state reports queue will
    automatically be consumed by dedicated rpc workers.

    This change applies to ML2 plugin only.
    Other plugins should implement start_rpc_state_reports_listener
    to enable additional rpc workers.

    Change-Id: I5f8df6a478f7c82382049274b34b07109eeafbdb
    Closes-Bug: #1505217

Changed in neutron:
status: In Progress → Fix Committed
Revision history for this message
Thierry Carrez (ttx) wrote : Fix included in openstack/neutron 8.0.0.0b1

This issue was fixed in the openstack/neutron 8.0.0.0b1 development milestone.

Doug Hellmann (doug-hellmann)
Changed in neutron:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

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