[
https://issues.redhat.com/browse/ISPN-12364?page=com.atlassian.jira.plugi...
]
Wolf-Dieter Fink updated ISPN-12364:
------------------------------------
Description:
If a node leave the lock held by this instance is unlocked with reliablilty AVAILABLE and
all other members can use the lock.
But with reliability CONSITENT the lock is still set and, as there is no longer an owner,
the only way is to force the unlock from application code, but there is no knowledge that
the lock does not have an alive owner
This is not the expected behaviour.
was:
If a node leave graceful by shutting down the CacheManager or stop the process (CTRL-C)
the lock held by this instance is unlocked and all other members can use the lock.
But if the process crash or is killed (UNIX kill -9) the lock is still set and, as there
is no longer an owner, the only way is to force the unlock.
This is not the expected behaviour.
If a node crashes leave the lock is not released in CONSISTENT
reliablility
---------------------------------------------------------------------------
Key: ISPN-12364
URL:
https://issues.redhat.com/browse/ISPN-12364
Project: Infinispan
Issue Type: Bug
Components: Clustered Locks
Affects Versions: 11.0.3.Final, 12.0.0.Dev04
Reporter: Wolf-Dieter Fink
Priority: Major
If a node leave the lock held by this instance is unlocked with reliablilty AVAILABLE and
all other members can use the lock.
But with reliability CONSITENT the lock is still set and, as there is no longer an owner,
the only way is to force the unlock from application code, but there is no knowledge that
the lock does not have an alive owner
This is not the expected behaviour.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)