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 "Thomas Mueller (JIRA)" <ji...@apache.org> on 2017/02/07 15:41:41 UTC

[jira] [Resolved] (OAK-5587) Node counter index estimates must not be used before first async index cycle

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

Thomas Mueller resolved OAK-5587.
---------------------------------
    Resolution: Fixed

> Node counter index estimates must not be used before first async index cycle
> ----------------------------------------------------------------------------
>
>                 Key: OAK-5587
>                 URL: https://issues.apache.org/jira/browse/OAK-5587
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>            Reporter: Thomas Mueller
>            Assignee: Thomas Mueller
>             Fix For: 1.8, 1.6.1
>
>
> Oak traversing index returns a very low estimate when first async index cycle hasn't completed yet, so that the wrong index can be used on first startup.
> NodeCounter#getCombinedCost() should treat non-existing /oak:index/counter/:index same as /oak:index/counter not existing.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)