That is not possible. The cluster was stripped down to 2 nodes and when ignitevisorcmd.sh is not connected I can stop and start cluster nodes freely. As soon as ignitevisorcmd.sh is connected to the grid on any of the 2 nodes at the time you stop one cluster node, that makes the stopped cluster node fail to start with "Node with BaselineTopology cannot join mixed cluster running in compatibility mode". I would be very surprised if devs could not reproduce it with:
1. Set up a 2-node cluster with the simplest config possible. Persistence may need to be enabled (I had it on) and consistentID hard-coded in the config (that's what I did but probably doesn't matter). 2. Make sure the cluster is active, 2 nodes are ONLINE. 3. Create an SQL table which will create an underlying cache - may also not be needed really but that is what I did. 4. Try stopping/started the cluster nodes (one at a time) with systemctl (or kill the processes manually if you prefer or have an old system with no systemd). This should work. 5. Now start ignitevisorcmd.sh. on either node, connect it and make sure it can see both cluster nodes with "top". 6. Try restarting any of the 2 cluster nodes while ignitevisorcmd.sh is connected (same as in 4.). You should get the lovely error I did. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
