Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
Date: Wed, 15 Mar 2017 07:57:41 +0000 (UTC)
From: "Evans Ye (JIRA)" <jira@apache.org>
To: issues@ignite.apache.org
Message-ID: <JIRA.13028814.1481929167000.23621.1489564661627@Atlassian.JIRA>
In-Reply-To: <JIRA.13028814.1481929167000@Atlassian.JIRA>
References: <JIRA.13028814.1481929167000@Atlassian.JIRA> <JIRA.13028814.1481929167763@jira-lw-us.apache.org>
Subject: [jira] [Commented] (IGNITE-4450) Explicit lock is not released when
 node that acquired it is killed
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 15 Mar 2017 07:57:46 -0000


    [ https://issues.apache.org/jira/browse/IGNITE-4450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15925698#comment-15925698 ] 

Evans Ye commented on IGNITE-4450:
----------------------------------

Hi team,
This is fixed and committed to the code base, however I can't find patch file or PR attached on this JIRA.
It would be better to have the code attached here so that user/developer can reference and learn how the bug gets fixed.
BTW, thanks for the fix.

> Explicit lock is not released when node that acquired it is killed
> ------------------------------------------------------------------
>
>                 Key: IGNITE-4450
>                 URL: https://issues.apache.org/jira/browse/IGNITE-4450
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache
>    Affects Versions: 1.8
>            Reporter: Valentin Kulichenko
>            Assignee: Semen Boikov
>            Priority: Critical
>             Fix For: 1.9
>
>         Attachments: ExplicitLockTest.java
>
>
> Test is attached. The scenario is the following:
> # Start first node and create a transactional cache.
> # Start second node and acquire a lock.
> # Kill second node after several seconds without doing unlock.
> # Try to start third node. It can't join because the lock is still held for some reason. The result if hanged cluster.


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)