ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Evans Ye (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-4450) Explicit lock is not released when node that acquired it is killed
Date Wed, 15 Mar 2017 07:57:41 GMT

    [ 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

View raw message