e84a10882a
when launching multiple agents at same time, there is a chance that agents will miss the registry of another agent. this is possible because there is a lot of overhead involved when starting up agents, specifically with initialising managers. this change makes it so the agent only joins the group AFTER it has done all setup that does not require coordination. after it joins, we start listening right away for other changes to group membership additionally, this adds a lock to pipeline queue setup so only one event at any time can trigger a reconfiguration. Change-Id: I8100160a3aa83a190c4110e6e8be9b26aef8fd1c Closes-Bug: #1533787
10 lines
436 B
YAML
10 lines
436 B
YAML
---
|
|
critical:
|
|
- >
|
|
[`bug 1533787 <https://bugs.launchpad.net/ceilometer/+bug/1533787>`_]
|
|
Fix an issue where agents are not properly getting registered to group
|
|
when multiple notification agents are deployed. This can result in
|
|
bad transformation as the agents are not coordinated. It is still
|
|
recommended to set heartbeat_timeout_threshold = 0 in
|
|
[oslo_messaging_rabbit] section when deploying multiple agents.
|