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/12/08 10:26:12 UTC

[jira] [Resolved] (OAK-2318) DocumentNodeStore.diffManyChildren() reads too many nodes

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

Marcel Reutegger resolved OAK-2318.
-----------------------------------
    Resolution: Fixed

Applied patch to trunk: http://svn.apache.org/r1643767

> DocumentNodeStore.diffManyChildren() reads too many nodes
> ---------------------------------------------------------
>
>                 Key: OAK-2318
>                 URL: https://issues.apache.org/jira/browse/OAK-2318
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: core, mongomk
>    Affects Versions: 1.0.8, 1.1.2
>            Reporter: Marcel Reutegger
>            Assignee: Marcel Reutegger
>            Priority: Minor
>             Fix For: 1.1.3
>
>         Attachments: OAK-2318.patch
>
>
> DocumentNodeStore.diffManyChildren() compares too many nodes when running in a non-clustered setup and there are many changes below a location with 'many' children.
> This is a regression introduced by OAK-2232. The fix changed the way how the minimum revision is calculated based on the two revisions to compare. The seen-at revision of the RevisionComparator is taken into account. However, in a single cluster node setup, the revision range for the current clusterId is never updated. This means the minimum revision is calculated too far back and causes queries with too many nodes than necessary.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)