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 2014/07/16 17:17:05 UTC

[jira] [Updated] (OAK-1972) Async property index update may fail on DocumentMK with more than 100 index changes

     [ https://issues.apache.org/jira/browse/OAK-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marcel Reutegger updated OAK-1972:
----------------------------------

    Fix Version/s: 1.0.3

> Async property index update may fail on DocumentMK with more than 100 index changes
> -----------------------------------------------------------------------------------
>
>                 Key: OAK-1972
>                 URL: https://issues.apache.org/jira/browse/OAK-1972
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: core, mongomk
>    Affects Versions: 1.0.1, 1.0.2
>            Reporter: Marcel Reutegger
>            Assignee: Marcel Reutegger
>             Fix For: 1.0.3
>
>
> The {{AsyncUpdateCallback}} gets notified whenever an editor updates the index via {{indexUpdate()}}. After every 100 changes the callback checks the lease time and extends the lease if necessary. In combination with OAK-1968 and more than 100 index changes, this will likely lead to an async-lease update in a separate commit from within the commit editor. Because of the way how OAK-1056 was fixed, this commit is mixed with the surrounding commit and may lead to a conflict or otherwise fail the commit.



--
This message was sent by Atlassian JIRA
(v6.2#6252)