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 "Davide Giannella (JIRA)" <ji...@apache.org> on 2016/03/02 15:56:18 UTC
[jira] [Updated] (OAK-3439) MissingLastRevSeeker potential race
condition acquiring the lock
[ https://issues.apache.org/jira/browse/OAK-3439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Davide Giannella updated OAK-3439:
----------------------------------
Fix Version/s: 1.4
> 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
> Affects Versions: 1.3.9, 1.0.23, 1.2.8
> Reporter: Julian Reschke
> Assignee: Julian Reschke
> Labels: candidate_oak_1_0
> Fix For: 1.4, 1.3.10, 1.2.11
>
> Attachments: OAK-3439.diff, OAK-3439.diff
>
>
> {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)