From issues-return-69637-archive-asf-public=cust-asf.ponee.io@ignite.apache.org Fri Jul 13 10:49:03 2018 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 [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 452D5180626 for ; Fri, 13 Jul 2018 10:49:03 +0200 (CEST) Received: (qmail 30293 invoked by uid 500); 13 Jul 2018 08:49:02 -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 30284 invoked by uid 99); 13 Jul 2018 08:49:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Jul 2018 08:49:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id B09DECE600 for ; Fri, 13 Jul 2018 08:49:01 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.501 X-Spam-Level: X-Spam-Status: No, score=-109.501 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id HG4H-fUI_sJx for ; Fri, 13 Jul 2018 08:49:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id AE61A5F22E for ; Fri, 13 Jul 2018 08:49:00 +0000 (UTC) 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 507D9E015A for ; Fri, 13 Jul 2018 08:49: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 0E1F423F96 for ; Fri, 13 Jul 2018 08:49:00 +0000 (UTC) Date: Fri, 13 Jul 2018 08:49:00 +0000 (UTC) From: "Dmitry Karachentsev (JIRA)" To: issues@ignite.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (IGNITE-8985) Node segmented itself after connRecoveryTimeout MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/IGNITE-8985?page=3Dcom.atlassia= n.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D165= 42723#comment-16542723 ]=20 Dmitry Karachentsev commented on IGNITE-8985: --------------------------------------------- Here are few things that caused this behavior. 1. One node was killed. 2. Previous for it was unable to connect and tried to go to next of the kil= led. 3. As we have 60 secs of failure detection timeout, then connection check f= requency will be 60 / 3 =3D 20 secs. So it means that previous node will be= treated as failed if there was no message during 20 secs. In the other han= d, recovery timeout is 10 secs. 4. Another case is that each node has two loopback addresses, when one of t= hem 172.17.0.1:47500 is not determined as localhost and was checked. In oth= er words node checked connection to itself. To fix it should be applied loopback check from IGNITE-8683 ticket and add = IGNITE-8944 to mark node as failed faster. > Node segmented itself after connRecoveryTimeout > ----------------------------------------------- > > Key: IGNITE-8985 > URL: https://issues.apache.org/jira/browse/IGNITE-8985 > Project: Ignite > Issue Type: Bug > Reporter: Mikhail Cherkasov > Assignee: Dmitry Karachentsev > Priority: Major > Attachments: Archive.zip > > > I can see the following message in logs: > [2018-07-10 16:27:13,111][WARN ][tcp-disco-msg-worker-#2] Unable to conne= ct to next nodes in a ring, it seems local node is experiencing connectivit= y issues. Segmenting local node to avoid case when one node fails a big par= t of cluster. To disable that behavior set TcpDiscoverySpi.setConnectionRec= overyTimeout() to 0. [connRecoveryTimeout=3D10000, effectiveConnRecoveryTim= eout=3D10000] > [2018-07-10 16:27:13,112][WARN ][disco-event-worker-#61] Local node SEGME= NTED: TcpDiscoveryNode [id=3De1a19d8e-2253-458c-9757-e3372de3bef9, addrs=3D= [127.0.0.1, 172.17.0.1, 172.25.1.17], sockAddrs=3D[/172.17.0.1:47500, lab17= .gridgain.local/172.25.1.17:47500, /127.0.0.1:47500], discPort=3D47500, ord= er=3D2, intOrder=3D2, lastExchangeTime=3D1531229233103, loc=3Dtrue, ver=3D2= .4.7#20180710-sha1:a48ae923, isClient=3Dfalse] > I have failure detection time out 60_000 and during the test I had GC <25= secs, so I don't expect that node should be segmented. > =C2=A0 > Logs are attached. > =C2=A0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)