Cannot form a cluster with consul Cluster Formation and Peer Discovery #15301
-
Describe the bugHey, I've set the configuration to use custom node names: but RMQ seems to still call the node in different ways than configured and not able to form a cluster (not even with a single instance): From the debug/log, it's also not clear where the actual issue is or even what is failing to connect (there are no error logs either)... Any help would be appreciated. Reproduction stepsSee describtion Expected behaviorForm a cluster Additional contextNo response |
Beta Was this translation helpful? Give feedback.
Answered by
michaelklishin
Jan 19, 2026
Replies: 1 comment
-
|
@kochen we cannot comment on "RMQ seems to still call the node in different ways", you have debug logs that demonstrate exactly the requests performed. does match the config snippet you have provided. You can also see the exact requests peer discovery performs against Consul nodes. There are no errors in the provided snippet and no other details that would help the core team or anyone else understand what you are doing. demonstrates what the peer discovery process has discovered: one node. As the Cluster Formation guie explains, peer discovery will only run when a node is a blank one, restarting a node with an existing node data directory will not invoke peer discovery.
Makes no sense to me either because a node that discovers no peers and has no existing database will start as a standalone node. So there always will be a single node. We will not guess what you expect to happen, and we will not troubleshoot networking and such for non-paying, non-contributing users. |
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
michaelklishin
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@kochen we cannot comment on "RMQ seems to still call the node in different ways", you have debug logs that demonstrate exactly the requests performed.