hi Alex,Sorry for the confusing comment. My baseline topology does not have a client node. I was indeed referring to the current cluster topology in my previous comment.
These ignite cluster nodes are programmed to come up and immediately run ignite.cluster.active(true) but that is not coordinated to wait for both nodes to come up. Based on the output of control.sh I assume that I'm not bringing up the cluster correctly. Let me know what you think and how to fix. Thanks! Here is the output of control.sh: root [ /opt/ignite/apache-ignite-fabric-2.6.0-bin/bin ]# ./control.sh --baselineControl utility [ver. 2.6.0#20180710-sha1:669feacc]2018 Copyright(C) Apache Software FoundationUser: root--------------------------------------------------------------------------------Cluster state: activeCurrent topology version: 7Baseline nodes: ConsistentID=416b00e2-4344-4fc7-bb1e-7333977cfbf8, STATE=OFFLINE--------------------------------------------------------------------------------Number of baseline nodes: 1Other nodes: ConsistentID=51b15af0-613c-4bd3-a0bc-41c06a0fd654 ConsistentID=b8e5512d-13dd-46f5-be28-ea73314ac9aeNumber of other nodes: 2 -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
