Figure out cause of error #3817
-
Good day! I've had some issue on the rabbitmq server. It did not broke cluster, it recovered, but it would be nice if you could provide some insight or ideas, what could possibly be the reason for this behavior. Preliminary data:
Running in docker-swarm, it is a cluster using quorum queues feature with consul for service discovery. There are multiple rabbitmq nodes sitting behind HAProxy. The errors that I've managed to recover:
Thank you! 🙏 |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
There have been many improvements to RabbitMQ and quorum queues since version 3.8.22. Please upgrade RabbitMQ and Erlang to the latest versions. If the issue re-appears after a network partition, provide the full logs from all nodes. For what it's worth, if your cluster's operation returned to normal after the above events, there is nothing to worry about. Those messages look typical of events that happen during a network partition. |
Beta Was this translation helpful? Give feedback.
There have been many improvements to RabbitMQ and quorum queues since version 3.8.22. Please upgrade RabbitMQ and Erlang to the latest versions. If the issue re-appears after a network partition, provide the full logs from all nodes.
For what it's worth, if your cluster's operation returned to normal after the above events, there is nothing to worry about. Those messages look typical of events that happen during a network partition.