[IGNITE-882] Node can join twice with the same ID

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: sprint-7
• Component/s: general
• Assignee: Dmitriy Setrakyan
• Reporter: Semen Boikov
• Created: 08/May/15 12:10
• Updated: 23/Jul/15 08:10
• Resolved: 07/Jul/15 11:14

Description

Observed in the test 'GridCacheColocatedFailoverSelfTest.testOptimisticRepeatableReadTxConstantTopologyChange':

Node joined:

[15:53:24,163][INFO ][disco-event-worker-#121%dht.GridCacheColocatedFailoverSelfTest0%][GridDiscoveryManager] Added new node to topology: TcpDiscoveryNode [id=10cf7906-50af-4f46-9c31-baf419539001, addrs=[127.0.0.1], sockAddrs=[/127.0.0.1:47525], discPort=47525, order=400, intOrder=202, loc=false, ver=1.0.3#19700101-sha1:00000000, isClient=false]

Node failed:

[15:53:24,171][WARN ][disco-event-worker-#121%dht.GridCacheColocatedFailoverSelfTest0%][GridDiscoveryManager] Node FAILED: TcpDiscoveryNode [id=10cf7906-50af-4f46-9c31-baf419539001, addrs=[127.0.0.1], sockAddrs=[/127.0.0.1:47525], discPort=47525, order=400, intOrder=202, loc=false, ver=1.0.3#19700101-sha1:00000000, isClient=false]

This see this message from the thread starting new node:

[15:53:29,047][WARN ][topology-change-thread-1][TcpDiscoverySpi] Node has not been connected to topology and will repeat join process. Check remote nodes logs for possible error messages. Note that large topology may require significant time to start. Increase 'TcpDiscoverySpi.networkTimeout' configuration property if getting this message on the starting nodes [networkTimeout=5000]

Node joined again with the same ID:

[15:53:29,212][INFO ][disco-event-worker-#121%dht.GridCacheColocatedFailoverSelfTest0%][GridDiscoveryManager] Added new node to topology: TcpDiscoveryNode [id=10cf7906-50af-4f46-9c31-baf419539001, addrs=[127.0.0.1], sockAddrs=[/127.0.0.1:47525], discPort=47525, order=404, intOrder=205, loc=false, ver=1.0.3#19700101-sha1:00000000, isClient=false]

Then test hangs (in the log I see that future mapped on the node '10cf7906-50af-4f46-9c31-baf419539001' did not finish).

The same issue observed in tests extending GridCacheAbstractNodeRestartSelfTest.

Issue Links

• is duplicated by: IGNITE-874 [Test] GridCachePartitionedNodeRestartTest cause build hanging