You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Julian Reschke (JIRA)" <ji...@apache.org> on 2015/09/22 15:27:04 UTC
[jira] [Created] (OAK-3439) MissingLastRevSeeker potential race
condition acquiring the lock
Julian Reschke created OAK-3439:
-----------------------------------
Summary: MissingLastRevSeeker potential race condition acquiring the lock
Key: OAK-3439
URL: https://issues.apache.org/jira/browse/OAK-3439
Project: Jackrabbit Oak
Issue Type: Task
Components: core, rdbmk
Reporter: Julian Reschke
{code}
// This approach has a race condition where two different cluster
// nodes
// can acquire the lock simultaneously.
UpdateOp update = new UpdateOp(Integer.toString(clusterId), true);
update.set(ClusterNodeInfo.REV_RECOVERY_LOCK, RecoverLockState.ACQUIRED.name());
store.createOrUpdate(Collection.CLUSTER_NODES, update);
return true;
{code}
It would be good if could harden this, however it seems that the conditions in UpdateOp only work on revision properties. [~mreutegg] WDYT?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)