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 41607200C60 for ; Mon, 24 Apr 2017 09:58:08 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 3FE03160BB2; Mon, 24 Apr 2017 07:58:08 +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 875FC160B99 for ; Mon, 24 Apr 2017 09:58:07 +0200 (CEST) Received: (qmail 91938 invoked by uid 500); 24 Apr 2017 07:58:01 -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 91928 invoked by uid 99); 24 Apr 2017 07:58:01 -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; Mon, 24 Apr 2017 07:58:01 +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 4293C180BA9 for ; Mon, 24 Apr 2017 07:58:01 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.673 X-Spam-Level: ** X-Spam-Status: No, score=2.673 tagged_above=-999 required=6.31 tests=[DKIM_ADSP_CUSTOM_MED=0.001, KAM_NUMSUBJECT=0.5, NML_ADSP_CUSTOM_MED=1.2, 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 (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id JtLX4XiVns2J for ; Mon, 24 Apr 2017 07:57:59 +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 327A85F342 for ; Mon, 24 Apr 2017 07:57:59 +0000 (UTC) Received: from static.162.255.23.37.macminivault.com (unknown [162.255.23.37]) by mwork.nabble.com (Postfix) with ESMTP id D64953C4F53D8 for ; Mon, 24 Apr 2017 00:57:58 -0700 (MST) Date: Mon, 24 Apr 2017 00:57:58 -0700 (MST) From: vdpyatkov To: user@ignite.apache.org Message-ID: <1493020678873-12174.post@n6.nabble.com> In-Reply-To: <1492789517267-12161.post@n6.nabble.com> References: <1492278948063-11989.post@n6.nabble.com> <1492436518101-11997.post@n6.nabble.com> <1492789517267-12161.post@n6.nabble.com> Subject: Re: Exceptions while running Closure with task count > 1000 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit archived-at: Mon, 24 Apr 2017 07:58:08 -0000 I have reproduce you issue. Seem that is java heap issue. If the test is producing in one physical machine the issue does not reproduce, because costs of network communications are small. But when you are dedicate nodes by others computers, overheads are growing and heap space becomes insufficient. In result long GC pause or OOM exception and breakdown topology. If you wan to avoid this issue you should add enough memory for jvm and additional tuning you application. Look in his article[1]. [1]: https://apacheignite.readme.io/docs/jvm-and-system-tuning#section-jvm-tuning-for-clusters-with-on_heap-caches -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Exceptions-while-running-Closure-with-task-count-1000-tp11989p12174.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.