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 CA6F82004A0 for ; Wed, 16 Aug 2017 15:51:36 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 919DF1612CF; Wed, 16 Aug 2017 13:51:32 +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 0AB55160FD8 for ; Wed, 16 Aug 2017 15:51:31 +0200 (CEST) Received: (qmail 68568 invoked by uid 500); 16 Aug 2017 13:51:30 -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 68558 invoked by uid 99); 16 Aug 2017 13:51:30 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Aug 2017 13:51:30 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id CFF46C0042 for ; Wed, 16 Aug 2017 13:51:29 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-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-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id dvGgLocaPiAp for ; Wed, 16 Aug 2017 13:51:29 +0000 (UTC) Received: from mwork.nabble.com (mwork.nabble.com [162.253.133.43]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id C5B855F3D0 for ; Wed, 16 Aug 2017 13:51:28 +0000 (UTC) Received: from static.162.255.23.37.macminivault.com (unknown [162.255.23.37]) by mwork.nabble.com (Postfix) with ESMTP id 4393C5CAC7B70 for ; Wed, 16 Aug 2017 06:51:28 -0700 (MST) Date: Wed, 16 Aug 2017 06:51:28 -0700 (MST) From: dkarachentsev To: user@ignite.apache.org Message-ID: <1502891488274-16227.post@n6.nabble.com> In-Reply-To: <1502875525328-16223.post@n6.nabble.com> References: <2017081513143988297312@tophold.com> <1502875525328-16223.post@n6.nabble.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: Wed, 16 Aug 2017 13:51:37 -0000 Hi Aaron, Do you have long GC pauses? As Bob said, large queries or transactions could move a lot of data to on-heap. F.e. regular SELECT will get all dataset into heap on server node and will respond to client with pages. But first of all try to find a reason of node segmentation first, it could be due to GC or system pauses, lost network, etc. 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-tp16192p16227.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.