A question about classic peer discovery combined with IPv6 #13911
-
Describe the bugI have upgraded RabbitMQ from 3.13.7 to 4.1.0 and found rabbit_peer_discovery_classic_config does not works properly now.
When I have disabled node discovery then RabbitMQ started without error messages We use IPv6-only network. we have configured
Reproduction stepsNeed to configure two-node cluster with enabled Expected behaviortwo RabbitMQ nodes will be joined into cluster without error messages in the logs Additional contextNo response |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
When I started one node, I could see an unexpected DNS request
Looks like RabbitMQ does not use FQDNS.
|
Beta Was this translation helpful? Give feedback.
-
@sergey-safarov you haven't provided any details, any configuration files, nor logs for us to work with. An There were no classic peer discovery changes (besides the new K8S plugin), so "peer discovery is broken" only for you. You haven't provided any details for us to work with, you are not a paying user nor your are a contributor => you will have to figure things out on your own. In addition, you did not seem to have read a dedicated documentation guide on using IPv6 for for inter-node communication. |
Beta Was this translation helpful? Give feedback.
@sergey-safarov you haven't provided any details, any configuration files, nor logs for us to work with. An
ERL_INTERC
file with oneThere were no classic peer discovery changes (besides the new K8S plugin), so "peer discovery is broken" only for you.
You haven't provided any details for us to work with, you are not a paying user nor your are a contributor => you will have to figure things out on your own.
In addition, you did not seem to have read a dedicated documentation guide on using IPv6 for for inter-node communication.