Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Excessive logging of 3.6 and 3.7 cluster multicast discovery join failure #8867
I have an existing Hazelcast 3.6 cluster running. Then I start up a cluster with a different group name using Hazelcast 3.7 on the same network. They are both using the same multicast IP and port.
Other than logging output, I think there is no actual effect, but it certainly caused concern in our DEV environment when starting up the new 3.7 cluster. We can work around it by changing the multicast IP or port for now, as having our logs flooded with those stack traces is not a reasonable option for us and I'm not sure it is smart for us to silence logs from
Note that I tested and this is not an issue if both clusters are Hazelcast 3.6. If the info so far is not enough, I can put together a repository on GitHub to reproduce the issue.