[ https://issues.apache.org/jira/browse/IGNITE-11621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sergey Chugunov updated IGNITE-11621: ------------------------------------- Ignite Flags: (was: Docs Required) Fix Version/s: 2.8 > 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)