[
https://issues.apache.org/jira/browse/OAK-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14063594#comment-14063594
]
Marcel Reutegger commented on OAK-1972:
---------------------------------------
Turns out the described nested commit is not the root cause for the index
update failure I saw.
What actually happens is, that the frequent async-lease update triggered a
document split and reading on an older revision on the split document returns
an outdated property.
> 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
>
> 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)
