Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 63451200CF3 for ; Tue, 15 Aug 2017 08:12:00 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 5FBA9166491; Tue, 15 Aug 2017 06:12:00 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id CCEAD16648F for ; Tue, 15 Aug 2017 08:11:59 +0200 (CEST) Received: (qmail 2396 invoked by uid 500); 15 Aug 2017 06:11:58 -0000 Mailing-List: contact user-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@ignite.apache.org Delivered-To: mailing list user@ignite.apache.org Received: (qmail 2383 invoked by uid 99); 15 Aug 2017 06:11:57 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Aug 2017 06:11:57 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 486051A04F9 for ; Tue, 15 Aug 2017 06:11:57 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.972 X-Spam-Level: X-Spam-Status: No, score=0.972 tagged_above=-999 required=6.31 tests=[RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.972] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id mqNtA18Plol3 for ; Tue, 15 Aug 2017 06:11:56 +0000 (UTC) Received: from mwork.nabble.com (mwork.nabble.com [162.253.133.43]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 138175FB2C for ; Tue, 15 Aug 2017 06:11:56 +0000 (UTC) Received: from static.162.255.23.37.macminivault.com (unknown [162.255.23.37]) by mwork.nabble.com (Postfix) with ESMTP id C8FD65C456AD7 for ; Mon, 14 Aug 2017 23:11:55 -0700 (MST) Date: Mon, 14 Aug 2017 23:11:55 -0700 (MST) From: dkarachentsev To: user@ignite.apache.org Message-ID: <1502777515812-16193.post@n6.nabble.com> In-Reply-To: <2017081513143988297312@tophold.com> References: <2017081513143988297312@tophold.com> Subject: Re: In which scenario the ignite nodes will shutdown by itself MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit archived-at: Tue, 15 Aug 2017 06:12:00 -0000 Hi, Node may stop if it was segmented out of the cluster. Usually this happens because of long GC or network pauses, when node doesn't respond longer than failureDetectionTimeout. Please, attach Ignite (with -DIGNITE_QUIET=false JVM flag) and GC logs, this will help to understand more. Thanks! -Dmitry. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/In-which-scenario-the-ignite-nodes-will-shutdown-by-itself-tp16192p16193.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.