Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
GitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
[cluster] SplitBrainMergeValidationOperation Ignoring join check from [NODEB]:5701, because this node is not master... #10587
Hi guys, How are you ?
I stopped/started the tomcat server nodeA, nodeB Become the "master" node. When NodeA was online again and join the hazelcast cluster, some messages was writen in catalina.out:
Even with this messages above, every thing seemed to work normal, but for this messages stop, I stopped NODEB for NODEA to become "Master" and started NODEB again, but I did this just this time today. After that I stopped/started many times each node in differente sequences and the error not appear any more. It's something intermittent that occurs rare times.
Do you have some guess about that ?
My env 64 bits: Linux RedHat 7.3, Tomcat 8.5, hazelcast-tomcat85-sessionmanager-1.1.jar, hazelcast-all-3.8.jar
Thank you very much!!!
Ok, as I understand, when NodeA is restarted, it successfully joins to the master NodeB but still you see that message repeatedly printed. Can you provide any log files so that we investigate the issue more efficiently. Especially the logs of NodeA's restart that lead to these log messages.