Hi I'm afraid I wiped Ignite off my servers already as this behaviour was a blocker to me. I only needed a key value store able to replicate across several datacenters across the globe (my use case involves very few writes) and I'm now evaluating another product already.
I strongly suggest you try to reproduce it with the exact steps I listed in this thread if you didn't try it already. It's dead simple to me - there are 2 nodes running, both in the baseline, you connect ignitevisorcmd.sh then shut down one node. Nothing else starts nor stops in the meantime, you just try to start up the shut down node again. In my tests it was 100% clear that ignitevisorcmd.sh being connected was the culprit of the 2.5 cluster being confused. It did not happen in 2.4. Good luck :-) -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
