Unable to initialize/recover vhost after autoheal #4612
Unanswered
Patrick-Remy
asked this question in
Questions
Replies: 1 comment 5 replies
-
There is a cascade of failures, including a failed feature flag state write. |
Beta Was this translation helpful? Give feedback.
5 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
In the last week we encountered two times, that rabbitmq's vhost keeps down after an autoheal. After the first time, we fully reinitialized a new rabbitmq cluster from scratch, and updated from 3.9.13 to latest bugfix version 3.9.15. But it happened again. As the crashing node was the holder of the queues, it broke the full cluster. We will test queue-mirroring to at least don't have the downtime.
Only a manual restart of the rabbitmq instance that had the vhost down helped to recover.
Do you have some idea what caused this?
RabbitMQ Dockerfile
Logs of www6-rabbitmq
Stack trace references
rabbitmq-server/deps/rabbit/src/rabbit_priority_queue.erl
Lines 111 to 117 in 14807cf
Beta Was this translation helpful? Give feedback.
All reactions