before I got the cluster to the active state I had deleted the /work folders on the 3 machines.
Then I deleted the /work folders once again, added a Windows machine (amended configs and firewall accordingly) to those 3 so to have a mixed cluster of 4 machines. I could not activate the new cluster. When control.sh --baseline tried to connect to the cluster it hung By the way - I wonder what is the right way to reset an Ignite instance to the initial state (the one I have when Ignite is just installed)? I used servise.sh set_firewall to add routes to the firewall, I added new ports to that file. So my iptable looks now like this Chain INPUT_direct (1 references) num target prot opt source destination 1 ACCEPT tcp -- anywhere anywhere multiport sports memcache:11220,47500:47509,47100:47109,58500:58520 2 ACCEPT udp -- anywhere anywhere multiport sports 47400:47409 3 ACCEPT tcp -- anywhere anywhere multiport dports memcache:11220,47500:47509,47100:47109,58500:58520 4 ACCEPT udp -- anywhere anywhere multiport dports 47400:47409 5 ACCEPT all -- anywhere anywhere PKTTYPE = multicast 6 ACCEPT tcp -- anywhere anywhere multiport sports memcache:11220,47500:47509,47100:47109,58500:58520,58100:58109 7 ACCEPT udp -- anywhere anywhere multiport sports 47400:47409,58400:58409 8 ACCEPT tcp -- anywhere anywhere multiport dports memcache:11220,47500:47509,47100:47109,58500:58520,58100:58109 9 ACCEPT udp -- anywhere anywhere multiport dports 47400:47409,58400:58409 10 ACCEPT tcp -- anywhere anywhere multiport sports gap,memcache:11220,47500:47509,47100:47109,58500:58520,58100:58109 11 ACCEPT tcp -- anywhere anywhere multiport dports gap,memcache:11220,47500:47509,47100:47109,58500:58520,58100:58109 12 ACCEPT tcp -- anywhere anywhere multiport sports gap:10801,memcache:11220,47500:47509,47100:47109,58500:58520,58100:58109 13 ACCEPT tcp -- anywhere anywhere multiport dports gap:10801,memcache:11220,47500:47509,47100:47109,58500:58520,58100:58109 regards, Evgeny -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
