From user-return-17155-archive-asf-public=cust-asf.ponee.io@ignite.apache.org Wed Jan 10 14:46:29 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id 1246618072F for ; Wed, 10 Jan 2018 14:46:29 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 02C2D160C2E; Wed, 10 Jan 2018 13:46:29 +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 6B4FA160C23 for ; Wed, 10 Jan 2018 14:46:28 +0100 (CET) Received: (qmail 15231 invoked by uid 500); 10 Jan 2018 13:46:27 -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 15221 invoked by uid 99); 10 Jan 2018 13:46:27 -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; Wed, 10 Jan 2018 13:46:27 +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 E643A180145 for ; Wed, 10 Jan 2018 13:46:26 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.172 X-Spam-Level: ** X-Spam-Status: No, score=2.172 tagged_above=-999 required=6.31 tests=[DKIM_ADSP_CUSTOM_MED=0.001, NML_ADSP_CUSTOM_MED=1.2, SPF_HELO_PASS=-0.001, 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 47iJUwj4ABW9 for ; Wed, 10 Jan 2018 13:46:24 +0000 (UTC) Received: from n6.nabble.com (n6.nabble.com [162.255.23.37]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 95CCF5F3D0 for ; Wed, 10 Jan 2018 13:46:24 +0000 (UTC) Received: from n6.nabble.com (localhost [127.0.0.1]) by n6.nabble.com (Postfix) with ESMTP id 163C13F4700F for ; Wed, 10 Jan 2018 06:46:23 -0700 (MST) Date: Wed, 10 Jan 2018 06:46:23 -0700 (MST) From: Alexey Popov To: user@ignite.apache.org Message-ID: <1515591983088-0.post@n6.nabble.com> In-Reply-To: <1515546232872-0.post@n6.nabble.com> References: <1515546232872-0.post@n6.nabble.com> Subject: Re: IgniteOutOfMemoryException when using putAll instead of put MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi, You are right, cache.putAll() can't evict the entries from the batch it is working on, and you can get Ignite OOME. This is expected behavior because putAll get locks for all provided entry keys. That is critical: 1) for transactional caches and 2) any caches backed up by 3-rd party persistence store. There was an intention to optimize this behavior for atomic caches without cache store [1] but it seems it will not be implemented. So, you could rely on this behavior. [1] https://issues.apache.org/jira/browse/IGNITE-514. Thank you, Alexey -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/