[IGNITE-13018] Get rid of duplicated checking of failed node.

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Vladimir Steshin
• Reporter: Vladimir Steshin
• Created: 15/May/20 14:18
• Updated: 03/Jun/20 10:08
• Resolved: 27/May/20 11:01

Description

Failed node checking should be simplified to one step: ping node (send a message) from previous one in the ring and wait for response within IgniteConfiguration.failureDetectionTimeout. If node doesn't respond, we should consider it failed. Extra steps of connection checking may seriously delay failure detection, bring confusion and weird behavior.

Issue Links

• duplicates: IGNITE-13014 Remove double checking of node availability.