[
https://issues.apache.org/jira/browse/IGNITE-8810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16517038#comment-16517038
]
Jon Tricker commented on IGNITE-8810:
-------------------------------------
Created the attached CacheUnlockTest.java testing the same problem with cache
locks.
If the ‘remote’ node is explicitly closed this releases the lock as expected.
This is different to the re-entrant lock case.
However if the remote node goes out of scope, or crashes, without an explicit
close(), it remains locked. See comments in code for more details.
However this is all running on one machine (process?). Maybe things are
different if the failing node is really a remote machine connected over the
network.
> Create failoverSafe for ReentrantLock
> -------------------------------------
>
> Key: IGNITE-8810
> URL: https://issues.apache.org/jira/browse/IGNITE-8810
> Project: Ignite
> Issue Type: Improvement
> Reporter: Evgenii Zhuravlev
> Priority: Major
> Attachments: CacheUnlockTest.java, UnlockTest.java
>
>
> Currently, it has the flag "failoverSafe", but it doesn't have any
> implementation for it
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
