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 "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2015/06/10 13:43:55 UTC
[jira] [Updated] (OAK-2762) Configurable maxLockTryTimeMS
[ https://issues.apache.org/jira/browse/OAK-2762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcel Reutegger updated OAK-2762:
----------------------------------
Fix Version/s: 1.0.15
Merged to 1.0 branch: http://svn.apache.org/r1684644
> Configurable maxLockTryTimeMS
> -----------------------------
>
> Key: OAK-2762
> URL: https://issues.apache.org/jira/browse/OAK-2762
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: core, mongomk
> Reporter: Marcel Reutegger
> Assignee: Marcel Reutegger
> Priority: Minor
> Fix For: 1.2.1, 1.3.0, 1.0.15
>
>
> OAK-2127 introduced a maxLockTryTimeMS to allow a writer to proceed with a merge even if the merge lock is currently acquired by another thread. The value is currently hardcoded.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)