Return-Path: X-Original-To: apmail-ignite-issues-archive@minotaur.apache.org Delivered-To: apmail-ignite-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BB21017DCA for ; Wed, 2 Dec 2015 09:42:18 +0000 (UTC) Received: (qmail 76153 invoked by uid 500); 2 Dec 2015 09:42:11 -0000 Delivered-To: apmail-ignite-issues-archive@ignite.apache.org Received: (qmail 76021 invoked by uid 500); 2 Dec 2015 09:42:11 -0000 Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list issues@ignite.apache.org Received: (qmail 75898 invoked by uid 99); 2 Dec 2015 09:42:11 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Dec 2015 09:42:11 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 4ACA72C14F0 for ; Wed, 2 Dec 2015 09:42:11 +0000 (UTC) Date: Wed, 2 Dec 2015 09:42:11 +0000 (UTC) From: "Andrey Gura (JIRA)" To: issues@ignite.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (IGNITE-2008) Abandoned locks are not released when nodes leave the grid MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/IGNITE-2008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15035552#comment-15035552 ] Andrey Gura commented on IGNITE-2008: ------------------------------------- Noam, I reproduced it on current development branch (ignite-1.5). > Abandoned locks are not released when nodes leave the grid > ---------------------------------------------------------- > > Key: IGNITE-2008 > URL: https://issues.apache.org/jira/browse/IGNITE-2008 > Project: Ignite > Issue Type: Bug > Affects Versions: ignite-1.4 > Environment: Ubuntu 12.04, Ignite 1.4, Java 1.8.0_40-b26 (HotSpot 64-Bit) > Reporter: Noam Liran > Fix For: 1.6 > > > Hi, > We're starting to use Ignite in one of our environments and we've encountered some strange behaviour in one of our test cases. > # Start two nodes at the same time. > # Each nodes should initialize a cache with the following parameters: > ## Cache mode: REPLICATED / PARTITIONED > ## Atomicity mode: TRANSACTIONAL > # Both nodes run the following code: > {code} > System.out.println("Sleeping before.."); > Thread.sleep(5000); > List locks = new ArrayList<>(); > System.out.println("Acquiring..."); > for (int lockId = 0; lockId < 4; lockId++) { > String lockName = "LOCK_" + lockId; > Lock lock = cache.lock(lockName); > locks.add(lock); > lock.lock(); > } > System.out.println("Acquired!"); > Thread.sleep(20000); > System.out.println("Done"); > {code} > # Node 1 acquires all the relevant locks and waits a while. > # Node 2 tries to acquire the locks and is blocked. > # Node 1 eventually quits while holding the locks. > # Node 2 never gains control of the locks even though they're abandoned. > When we try the same with a looped tryLock everything seems to work. > Our Ignite configuration is pretty straightforward: > # Regular TCP discovery > # No checkpointing SPI > # No collision SPI > # Always failover SPI > # CONTINUOUS deployment mode -- This message was sent by Atlassian JIRA (v6.3.4#6332)