Number of q-plugin and q-l3-plugin consumer is not equal
Bug #1503276 reported by
Ksenia Svechnikova
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mirantis OpenStack |
Triaged
|
Wishlist
|
Oleg Bondarev | ||
8.0.x |
Won't Fix
|
Wishlist
|
Oleg Bondarev | ||
9.x |
Won't Fix
|
Wishlist
|
Inessa Vasilevskaya |
Bug Description
Steps to reproduce:
MOS 7.0 (#301)
1. Deploy MOS (3+1) with Neutron with DVR enabled.
2. Check number of consumers rabbitmqctl list_queues consumers name | grep plugin$
Actual results:
root@node-1:~# rabbitmqctl list_queues consumers name | grep plugin$
3 q-metering-plugin
15 q-reports-plugin
36 q-plugin
39 q-l3-plugin
There are 36 for q-plugin and 39 for q-l3-plugin
Changed in mos: | |
status: | New → Confirmed |
milestone: | none → 8.0 |
Changed in mos: | |
status: | Confirmed → Triaged |
tags: | added: area-neutron neutron |
To post a comment you must log in.
The root cause is in the difference of how rpc listeners are started.
core plugin (ml2) doesn't start rpc listeners in __init__ method, unlike l3_router plugin.
So for l3 queues we have rpc_workers+1 listener (+1 goes from parent process).
For cases when rpc_workers > 0, q-plugin is only consumed from rpc_workers, but not from the parent process.
This doesn't indicate any malfunction and we don't need to fix it.