[IGNITE-9493] Communication error resolver shouldn't be invoked if connection with client breaks unexpectedly

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.5
• Fix Version/s: 2.8
• Component/s: cache, zookeeper
• Ignite Flags: Docs Required
• Assignee: Evgeny Stanilovsky
• Reporter: Pavel Kovalenko
• Created: 07/Sep/18 12:48
• Updated: 21/Oct/20 20:29
• Resolved: 25/Dec/18 09:07

Description

Currently, we initiate communication error resolving process even if a connection between server and client breaks unexpectedly.

This is unnecessary action because client nodes are not important for cluster stability. We should ignore communication errors for client and daemon nodes.

Issue Links

• breaks: IGNITE-10988 Zookeeper test case testCommunicationFailureResolve_KillRandom frequently fails in GridAbstractTest.waitForTopology
• links to: GitHub Pull Request #5720
• links to: GitHub Pull Request #5720
• links to: TC