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 C8F5B200AE4 for ; Fri, 24 Jun 2016 15:56:12 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id C77EC160A58; Fri, 24 Jun 2016 13:56:12 +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 E7CA6160A2E for ; Fri, 24 Jun 2016 15:56:11 +0200 (CEST) Received: (qmail 52299 invoked by uid 500); 24 Jun 2016 13:56:11 -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 52287 invoked by uid 99); 24 Jun 2016 13:56:10 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 24 Jun 2016 13:56:10 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 8308C180651 for ; Fri, 24 Jun 2016 13:56:10 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.279 X-Spam-Level: * X-Spam-Status: No, score=1.279 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gridgain-com.20150623.gappssmtp.com Received: from mx2-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id EXZyxrhKH28d for ; Fri, 24 Jun 2016 13:56:08 +0000 (UTC) Received: from mail-lf0-f51.google.com (mail-lf0-f51.google.com [209.85.215.51]) by mx2-lw-eu.apache.org (ASF Mail Server at mx2-lw-eu.apache.org) with ESMTPS id F05E85F4E8 for ; Fri, 24 Jun 2016 13:56:07 +0000 (UTC) Received: by mail-lf0-f51.google.com with SMTP id q132so116498812lfe.3 for ; Fri, 24 Jun 2016 06:56:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gridgain-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:references:to:in-reply-to; bh=jbW3OkQ1ecjFSQHZFjU1FT5mNEniVavjx6ItaqRAnDY=; b=V/idaFYjs/pZ9QTAZsj2t52tpGpEJ8I9Vz41QpbrQf2xm5akpf/dHFh4AyVT0+JXOe 1b/t74V3h+8XVrDNmsvx/gvZx497W8T3v5fzSp1KrDNgZta73z0WZ04WNIY/hXGbIWa8 zhrZg9MB7mhSL/3zN7ziChWT5GSqv2yl9Jy3ce3puOmc+tVW5nInPNapprbWFp8UYQ1F KfkzC81OsO0jQScqRT05qlnlKBNHvZ1E79SbR8Ft5PQUOF23IxSl+dVr4CKmC/1p+lDB fLtbqRiE6h4psY+dB/LYz3BiK4MGDCOsXnZkxzNWZo8LHOLtZ9ynseqyblStCig1FEAU qHBA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:message-id:mime-version:subject:date :references:to:in-reply-to; bh=jbW3OkQ1ecjFSQHZFjU1FT5mNEniVavjx6ItaqRAnDY=; b=RShI8J00TaBcfb5+C/4NGvgnM99EJx3FonTYfTV0h9oVBclJHuamn14yiJZvzr2jxQ wK4MJZGyx5yMZmu/rGxOiNOLbUiymIuvlVatUUE8dptEsFq1KkSjDmsUl4h0zOa9slxc ePxWzIpTMzYbAKVHtQ1y6K1v0gkV76ijtOzl4MwYC4jovVkfaf4x6qsyWd2Qjp1zlfqP oqS59xqN84h9z8Sn8igiUjeKoMjTTISOetjCG5XRBB/7DPws4K7m7K8e88NrNcsq34rv wvXOqWAfpNU5k8z5be8lg7T/aB6RGeDQhz5Mah3F3aBnVCKQgo2UkMyGkr21qmJe4exU MsJA== X-Gm-Message-State: ALyK8tIxCcBUPfQWtgPEihvm0x+4N1c5kBF/lUGIsjv/Vnin0DbtkvcfT3inyHqPdt5ErbXd X-Received: by 10.25.4.4 with SMTP id 4mr1162346lfe.208.1466776567360; Fri, 24 Jun 2016 06:56:07 -0700 (PDT) Received: from [10.107.125.19] ([217.26.0.100]) by smtp.gmail.com with ESMTPSA id m125sm920741lfg.49.2016.06.24.06.56.06 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 24 Jun 2016 06:56:06 -0700 (PDT) From: Denis Magda Content-Type: multipart/alternative; boundary="Apple-Mail=_0DA69D5E-A76F-4194-8F55-42CCBA9CF2BA" Message-Id: Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: System.exit() not exiting cleanly (locked on IgnitionEx$IgniteNamedInstance) Date: Fri, 24 Jun 2016 16:56:06 +0300 References: <1466651475171-5814.post@n6.nabble.com> <1466765090153-5870.post@n6.nabble.com> <1466771407407-5876.post@n6.nabble.com> To: user@ignite.apache.org In-Reply-To: <1466771407407-5876.post@n6.nabble.com> X-Mailer: Apple Mail (2.3124) archived-at: Fri, 24 Jun 2016 13:56:13 -0000 --Apple-Mail=_0DA69D5E-A76F-4194-8F55-42CCBA9CF2BA Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Please provide full thread dumps from all the nodes at the time it = happens again. In particular I=E2=80=99m interested in what is going with the thread = named "ipc-shmem-gc=E2=80=9D. In addition to the thread dumps attache = the logs from all the nodes for investigation. As a workaround you can disable shmem as it was suggested before. = Finally I would recommend upgrading to the latest Ignite 1.6.0 version. =E2=80=94 Denis > On Jun 24, 2016, at 3:30 PM, bintisepaha = wrote: >=20 > JDK 1.7, 16 node cluster, each JVM 10 GB heap and 4 GB off heap. 4 = nodes run > on 4 linux boxes, each box has 64 GB memory. the heap is = under-utilized when > this happens. so doubt GC will cause it. > multiple clients connect to it. clients cannot exit properly either = with > System.exit() or Ignition.stop(). >=20 > We did not have the issue on our end until this week, but then = something > could have changed with ports in our environment. We cannot reproduce > ourselves in UAT it only happens for us in Production. >=20 >=20 >=20 >=20 >=20 > -- > View this message in context: = http://apache-ignite-users.70518.x6.nabble.com/System-exit-not-exiting-cle= anly-locked-on-IgnitionEx-IgniteNamedInstance-tp5814p5876.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. --Apple-Mail=_0DA69D5E-A76F-4194-8F55-42CCBA9CF2BA Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Please provide full thread dumps from all = the nodes at the time it happens again.
In particular = I=E2=80=99m interested in what is going with the thread named = "ipc-shmem-gc=E2=80=9D. In addition to the thread dumps attache the logs = from all the nodes for investigation.

As a workaround you can disable shmem = as it was suggested before. Finally I would recommend upgrading to the = latest Ignite 1.6.0 version.

=E2=80=94
Denis

On Jun 24, 2016, at 3:30 PM, = bintisepaha <binti.sepaha@tudor.com> wrote:

JDK = 1.7, 16 node cluster, each JVM 10 GB heap and 4 GB off heap. 4 nodes = run
on 4 linux boxes, each box has 64 GB memory. the heap = is under-utilized when
this happens. so doubt GC will = cause it.
multiple clients connect to it. clients cannot = exit properly either with
System.exit() or = Ignition.stop().

We did not have the issue = on our end until this week, but then something
could have = changed with ports in our environment. We cannot reproduce
ourselves in UAT it only happens for us in Production.




--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/System-exit-not-= exiting-cleanly-locked-on-IgnitionEx-IgniteNamedInstance-tp5814p5876.html<= /a>
Sent from the Apache Ignite Users mailing list archive = at
Nabble.com.

= --Apple-Mail=_0DA69D5E-A76F-4194-8F55-42CCBA9CF2BA--