Comment 2 for bug 2006145
Revision history for this message
| Maximilian Stinsky (mstinsky) wrote Re: BGP Speaker peer sessions down when rabbitmq offline | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
In newer versions of rabbitmq there is a high chance that rolling upgrades are working but there is still the possibility that some versions adds new feature flags that dont support rolling upgrades.
I understand the thought process about one agent maybe serving stale data if a single node is losing its connection to rabbitmq, but to lose all public connectivity to the cloud on a rabbitmq problem seems like too much impact.
In my opinion the agent should continue to announce its stale state and an operator needs to have alerting that the agent is down because it lost its connection to rabbitmq and then act accordingly to the situation.
When thinking about it dont other agent more or less do the same and just keep its local state like l3, ovs-agent and so on. They dont just remove router ip's, floating ip's, security groups or ovs-flows when they lose their connection to rabbitmq.