[jira] [Commented] (IGNITE-11621) Node is stuck in "No next node in topology" infinite loop in special case.

["Ignite TC Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-11621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16808620#comment-16808620 ] 

Ignite TC Bot commented on IGNITE-11621:
----------------------------------------

{panel:title=--> Run :: All: Possible Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Thin client: Node.js{color} [[tests 0 Exit Code |https://ci.ignite.apache.org/viewLog.html?buildId=3490320]]

{panel}
[TeamCity *--> Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=3487889&buildTypeId=IgniteTests24Java8_RunAll]

> Node is stuck in "No next node in topology" infinite loop in special case.
> --------------------------------------------------------------------------
>
>                 Key: IGNITE-11621
>                 URL: https://issues.apache.org/jira/browse/IGNITE-11621
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Sergey Chugunov
>            Assignee: Sergey Chugunov
>            Priority: Critical
>             Fix For: 2.8
>
>         Attachments: NoNextNodeInTopologyReproducer.java
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> In special case (reproducer is attached) node may stuck in the loop when the following sequence of events happens:
> * Nodes A and B are already in cluster.
> * Node C starts joining the cluster.
> * On node C NodeAdded message new node D is started.
> * Before NodeAddFinished for node C reaches it socket to node C fails and node is considered failed by the cluster.
> * When NodeFailed message for node C reaches node B both A and B fails.
> * After that node D gets stuck in infinite "No next node in topology" loop processing NodeFailed messages for A, B and C indefinitely.
> The main logic in attached reproducer lives in node1SpecialSpi - it is a TcpDiscoverySpi node B starts with.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)