notification agent sets up redundant consumers
Bug #1397424 reported by
gordon chung
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ceilometer |
Fix Released
|
Medium
|
gordon chung | ||
| Juno |
Fix Released
|
Medium
|
gordon chung | ||
Bug Description
when setting up listeners, the notification agent calls get_targets to retreive a list of queues to create a consumer for. unfortunately, we call get_targets per meter even though the exchange and queue itself is the same for related meters (ie. all the identity meters listen to keystone exchange, notification topic).
because of this we're creating a lot of duplicate consumers which from end user pov, makes no difference but if looking at stats ie. 'rabbitmqctl list_consumers.' there are a lot of extra consumers which don't really need to be there.
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to ceilometer (master) | #1 |
| description: | updated |
| description: | updated |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to ceilometer (master) | #2 |
| Changed in ceilometer: | |
| status: | In Progress → Fix Committed |
| Changed in ceilometer: | |
| status: | Fix Committed → Fix Released |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to ceilometer (stable/juno) | #3 |
| Changed in ceilometer: | |
| milestone: | kilo-1 → 2015.1.0 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to ceilometer (stable/juno) | #4 |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/