[IGNITE-7152] Failure detection timeout don't work on permanent send message errors causing infinite loop

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Not A Bug
• Affects Version/s: 2.3
• Fix Version/s: 2.8
• Component/s: general
• Assignee: Evgeny Stanilovsky
• Reporter: Alexandr Kuramshin
• Created: 08/Dec/17 11:44
• Updated: 25/Jul/19 06:31
• Resolved: 17/May/19 11:20

Description

Relative to RingMessageWorker.sendMessageAcrossRing implementation.

IgniteSpiOperationTimeoutHelper reinitialized every time the socket successfully connected.

If any of IOException, IgniteCheckedException occurs upon message send the socket will be closed and old IgniteSpiOperationTimeoutHelper will be used to reconnect.

But after successful reconnect the new one will be created and the cycle repeat. With a permanent send message error this causes an infinite loop.

The only send error which may cause to exit out of the loop and the next node failure is IgniteSpiOperationTimeoutException, SocketTimeoutException, SocketException.

Issue Links

• breaks: IGNITE-7134 Never-ending timeout in IgniteSpiOperationTimeoutHelper.nextTimeoutChunk()
• is related to: IGNITE-7160 Ignore messages from not alive and failed nodes
• relates to: IGNITE-11221 Refactor timeout logic in TcpDiscovery
• relates to: IGNITE-11567 runFailureDetectionOnReceiptError fail with SocketTimeoutException would be thrown.
• links to: GitHub Pull Request #6136