[
https://issues.apache.org/jira/browse/IGNITE-7152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16842099#comment-16842099
]
Stanilovsky Evgeny commented on IGNITE-7152:
--------------------------------------------
This reproducer (described case) is not possible on current [master] code and
probably has been erroneously reported earlier, cause if it would be problems
on *readReceipt* side, similar problems would be on sending
*TcpDiscoveryHandshakeRequestmessage*, witch prevents from infinite loop.
> Failure detection timeout don't work on permanent send message errors causing
> infinite loop
> -------------------------------------------------------------------------------------------
>
> Key: IGNITE-7152
> URL: https://issues.apache.org/jira/browse/IGNITE-7152
> Project: Ignite
> Issue Type: Bug
> Components: general
> Affects Versions: 2.3
> Reporter: Alexandr Kuramshin
> Assignee: Stanilovsky Evgeny
> Priority: Critical
> Fix For: 2.8
>
> Attachments: testFailureDetectionOnReceiptError.patch
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
