Enabling refresh_pipeline_cfg leads to restart of event listener even when sample_pipeline is refreshed
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ceilometer |
Opinion
|
Medium
|
Rohit Jaiswal | ||
Bug Description
When dynamic pipeline is enabled in config and the pipeline file (sample_pipeline) is updated, the notification listeners are restarted when the pipeline is refreshed.
As many listeners are created as the number of messaging_urls, For a single messaging_url, 1 listener is created that handles both sample and event endpoint targets.
https:/
On a refresh of the sample pipeline, the listener is restarted to refresh its pipeline configuration, but this interrupts the event consumption which is not required since the sample_pipeline has been refreshed, not the event_pipeline.
There should be a separation of the listeners based on which pipeline configuration they use, so that only the required ones be restarted, if needed.
| Changed in ceilometer: | |
| assignee: | nobody → Rohit Jaiswal (rohit-jaiswal-3) |
| description: | updated |
| description: | updated |
| Changed in ceilometer: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| OpenStack Infra (hudson-openstack) wrote Fix proposed to ceilometer (master) | #1 |
| Changed in ceilometer: | |
| status: | Triaged → In Progress |
| Changed in ceilometer: | |
| status: | In Progress → Opinion |
| OpenStack Infra (hudson-openstack) wrote Change abandoned on ceilometer (master) | #2 |
Fix proposed to branch: master
Review: https:/