Replies: 3 comments 1 reply
-
I am afraid “deploy an OpenStack cluster” is not a reproduction step we can accept. There are hundreds of potential variables involved. Start with collecting node logs for clues. Make sure you understand what happens when nodes are restarted and what that means for various health checks your system may be using for readiness probes. RabbitMQ 3.9 is out of support and classic mirrored queues have been deprecated for a couple of years now. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
This is the log of the three nodes,thank you very much for your help. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Describe the bug
I recently deployed the Yoga version of OpenStack, and I found that when I shut down a rabbitmq node, launch a new instance would be stuck at the build step, and the migration of the virtual machine would fail. I tried use the command "docker exec -it rabbitmq rabbitmqctl set_policy ha-all "^" '{"ha-mode":"all"}'" to adjust the rabbitmq cluster to mirror mode, but it didn't work. How can I adjust the rabbitmq cluster so that the cluster can still be used normally when I shut down a rabbitmq node? Looking forward to your reply.
Reproduction steps
...
Expected behavior
Shutting down a rabbitmq node does not affect the creation and migration of virtual machines
Additional context
No response
Beta Was this translation helpful? Give feedback.
All reactions