Replies: 2 comments
-
Hi @jipeigong, I am going to convert this to a github discussion because it's not clear to me that this is a bug 😃 |
Beta Was this translation helpful? Give feedback.
-
Hi @jipeigong, are you using a classic queue without replication? If you have high availability requirements, you should look into using quorum queues which makes sure that the queue is accessible in at least 3 nodes and would have the desired behavior of "can publish and consume when one node is down" that you are looking for. With classic queues, queues are only available in the node that they are created in, so when cluster-0 is down, the queue would be down as well, which is what you've observed. Let me know if using quorum queues help with your use case. |
Beta Was this translation helpful? Give feedback.
-
Describe the bug
k8s rabbitmq cluster multiple nodes high availability exception
To Reproduce
Steps to reproduce the behavior:
yaml:
Expected behavior
The expected result is that springboot reconnects to other cluster and runs normally,
Version and environment information
Beta Was this translation helpful? Give feedback.
All reactions