[IGNITE-10417] notifyDiscoveryListener() call can be lost.

• Type: Bug
• Status: Patch Available
• Priority: Critical
• Resolution: Unresolved
• Affects Version/s: 2.7
• Assignee: Pavel Voronkin
• Reporter: Pavel Voronkin
• Created: 27/Nov/18 09:16
• Updated: 25/Jan/21 16:43

Description

1) ServerImpl:5455 notifyDiscoveryListener can not be called in case of spiState != CONNECTED, for example DISCONNECTING which is valid state nevetheless inside notifyDiscoveryListener we check spiState == CONNECTED || spiState == DISCONNECTING, also we need to improve logging in notifyDiscoveryListener().

2)  Improve logging on duplicated custom discovery event.

3) Add assert if msg.creatorNodeId() doesn't exist in topology this is bad behaviour taht should lead to node fail.

 

 

 

 

 

Issue Links

• duplicates: IGNITE-9793 Deactivation, segmentation of one node, activation may lead to hang activation forever
• links to: PR