[
https://issues.apache.org/jira/browse/OAK-5587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15855917#comment-15855917
]
Thomas Mueller commented on OAK-5587:
-------------------------------------
> I've a bit of concern about the length of test though
The loop only runs rarely (about one of 10 test runs), and in most cases it
only creates 5000 nodes or so. But you are right, it's unfortunate that so many
nodes are needed. I will change the resolution of the counter index to 100, so
that the probability of this loop is much lower.
> 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.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)
