Hi, You might be experiencing the following scenario: 1. Node tried to connect to the cluster
2. Node is is added to the cluster 3. During the join process the node is timed out due to network issues (the default timeout is set via ackTimeout) 4. The node is dropped from the cluster 5. The node tries to re-connect to the cluster with the same nodeId. Node fails with “Node with the same ID..“ In order to keep each node's identity distinct, Ignite disallows nodes w/same id to join. In this case, because of timeouts, the ids are stored in the cluster and subsequent joins w/the same id fail. You need to increase failureDetectionTimeout if you are using it, otherwise increase ackTimeout. see: https://apacheignite.readme.io/docs/tcpip-discovery#failure-detection-timeout and: https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/spi/discovery/tcp/TcpDiscoverySpi.html#setAckTimeout-long- If this doesn't work, clean the work dir of all nodes, and restart, then send the logs and the structure of the work dir -- what it said in work/node id/db for each node. Thanks, Alex -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
