From issues-return-94919-archive-asf-public=cust-asf.ponee.io@ignite.apache.org Mon Apr 8 16:09:02 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id BC896180654 for ; Mon, 8 Apr 2019 18:09:01 +0200 (CEST) Received: (qmail 30062 invoked by uid 500); 8 Apr 2019 15:49:23 -0000 Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list issues@ignite.apache.org Received: (qmail 30047 invoked by uid 99); 8 Apr 2019 15:49:23 -0000 Received: from mailrelay1-us-west.apache.org (HELO mailrelay1-us-west.apache.org) (209.188.14.139) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Apr 2019 15:49:23 +0000 Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 6D12DE005D for ; Mon, 8 Apr 2019 16:09:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 2A92624595 for ; Mon, 8 Apr 2019 16:09:00 +0000 (UTC) Date: Mon, 8 Apr 2019 16:09:00 +0000 (UTC) From: "Alexey Goncharuk (JIRA)" To: issues@ignite.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (IGNITE-11621) Node is stuck in "No next node in topology" infinite loop in special case. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/IGNITE-11621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16812544#comment-16812544 ] Alexey Goncharuk commented on IGNITE-11621: ------------------------------------------- [~sergey-chugunov], can you add a short comment to the changed line to explain why this condition is important? Otherwise looks good. > 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)