]
Brian Stansberry closed JBCLUSTER-268.
--------------------------------------
Resolution: Done
Distributed locking API should indicate whether taking lock from
another node was necessary
-------------------------------------------------------------------------------------------
Key: JBCLUSTER-268
URL:
https://jira.jboss.org/browse/JBCLUSTER-268
Project: JBoss Clustering
Issue Type: Task
Security Level: Public(Everyone can see)
Components: HA-Server-API
Reporter: Brian Stansberry
Fix For: HA-Server-API 2.0.0.Beta1
Callers asking for a lock should be able to distinguish these cases:
1) Lock can't be obtained
2) Lock obtained, and node already held it.
3) Lock obtained, but the node had to make a group RPC to get it
Purpose of this is to use condition 3) as a way to detect failover.
Related to this, the API should also support creation of a new lock category such that
the node immediately owns the lock with no group RPC.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: