You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we upgrade AWS RabbitMQ, all webserver containers (3 on PROD) might (does not happen always) break simultaneously leading to 404.
Expected Behavior
As long as AWS RabbitMQ has healthy Nodes, webserver containers should keep running
Steps To Reproduce
Upgrade RabbitMQ
Anything else?
We run Clustered (3 EC2 Nodes) AWS RabbitMQ. During upgrade 2 AWS RabbitMQ Nodes instances are available at all time (upgrade is applied to 1 Node at a time). Webserver containers should try to connect to different Nodes or reconnect to other Nodes if their connection went off.
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Which deploy/s?
No response
Current Behavior
When we upgrade AWS RabbitMQ, all webserver containers (3 on PROD) might (does not happen always) break simultaneously leading to 404.
Expected Behavior
As long as AWS RabbitMQ has healthy Nodes, webserver containers should keep running
Steps To Reproduce
Anything else?
We run Clustered (3 EC2 Nodes) AWS RabbitMQ. During upgrade 2 AWS RabbitMQ Nodes instances are available at all time (upgrade is applied to 1 Node at a time). Webserver containers should try to connect to different Nodes or reconnect to other Nodes if their connection went off.
The text was updated successfully, but these errors were encountered: