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 E2761200D18 for ; Wed, 11 Oct 2017 12:04:38 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id E0ACC1609E4; Wed, 11 Oct 2017 10:04:38 +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 594D41609CA for ; Wed, 11 Oct 2017 12:04:38 +0200 (CEST) Received: (qmail 1045 invoked by uid 500); 11 Oct 2017 10:04:37 -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 1034 invoked by uid 99); 11 Oct 2017 10:04:37 -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, 11 Oct 2017 10:04:37 +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 9E6E9196541 for ; Wed, 11 Oct 2017 10:04:36 +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-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 Qeap7FExfVDQ for ; Wed, 11 Oct 2017 10:04:35 +0000 (UTC) Received: from n6.nabble.com (n6.nabble.com [162.255.23.37]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id D1B3F5FCA7 for ; Wed, 11 Oct 2017 10:04:34 +0000 (UTC) Received: from n6.nabble.com (localhost [127.0.0.1]) by n6.nabble.com (Postfix) with ESMTP id 27C2A22FDE70 for ; Wed, 11 Oct 2017 03:04:34 -0700 (MST) Date: Wed, 11 Oct 2017 03:04:34 -0700 (MST) From: afedotov To: user@ignite.apache.org Message-ID: <1507716274159-0.post@n6.nabble.com> In-Reply-To: <1507576123931-0.post@n6.nabble.com> References: <1507576123931-0.post@n6.nabble.com> Subject: Re: Lock on cache keys during node failures MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit archived-at: Wed, 11 Oct 2017 10:04:39 -0000 Hi Naresh, In case of a node failure, all the locks acquired by that node will be released. So, if there is a node waiting on any of such keys it should eventually acquire the lock. Kind regards, Alex -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/