[
https://issues.redhat.com/browse/ISPN-12364?page=com.atlassian.jira.plugi...
]
Wolf-Dieter Fink updated ISPN-12364:
------------------------------------
Steps to Reproduce:
* Start a 3 node cluster
* try a lock on each node
* stop one node
The behavior is expected to be the same with AVAILABLE and CONSISTENT reliability but it
is different.
With CONSISTENT the event is only fired for some locks
With AVAILABLE the event is fired for all locks and the lock for the missing node is
forced to release
was:Start a 3 node cluster and kill a node graceful (working) or by use "kill
-9" ungraceful to show the wrong behavior
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 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.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)