[ https://issues.apache.org/jira/browse/IGNITE-13590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pavel Vinokurov updated IGNITE-13590: ------------------------------------- Description: A new server node sends the join request and doesn't receive TcpDiscoveryNodeAddedMessage due to network issues. The node retries the join request and fails with: {code:java} Caused by: class org.apache.ignite.spi.IgniteSpiException: Node with the same ID was found in node IDs history or existing node in topology has the same ID (fix configuration and restart local node) {code} Instead of stopping it could retry joining the cluster after failureDetectionTimeout. was: A new server node sends the join request and doesn't receive TcpDiscoveryNodeAddedMessage due to network issues. The node retries the join request and fails with: {code:java} Caused by: class org.apache.ignite.spi.IgniteSpiException: Node with the same ID was found in node IDs history or existing node in topology has the same ID (fix configuration and restart local node) {code} Instead of fail down it could retry joining the cluster after failureDetectionTimeout. > Node fails with "Node with the same ID was found in node IDs history" after > missing TcpDiscoveryNodeAddedMessage > ---------------------------------------------------------------------------------------------------------------- > > Key: IGNITE-13590 > URL: https://issues.apache.org/jira/browse/IGNITE-13590 > Project: Ignite > Issue Type: Bug > Components: networking > Affects Versions: 2.8.1 > Reporter: Pavel Vinokurov > Priority: Major > Attachments: TcpDiscoveryMissingNodeAddedMessageTest.class > > > A new server node sends the join request and doesn't receive > TcpDiscoveryNodeAddedMessage due to network issues. > The node retries the join request and fails with: > {code:java} > Caused by: class org.apache.ignite.spi.IgniteSpiException: Node with the same > ID was found in node IDs history or existing node in topology has the same ID > (fix configuration and restart local node) > {code} > Instead of stopping it could retry joining the cluster after > failureDetectionTimeout. -- This message was sent by Atlassian Jira (v8.3.4#803005)