[
https://issues.apache.org/jira/browse/OAK-8046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17848192#comment-17848192
]
Thomas Mueller commented on OAK-8046:
-------------------------------------
[~royteeuwen] it means while the query is still running (and reading more
nodes), the index was updated concurrently. Indexes are updated every ~5
seconds.
Best is if the queries read less than 200 nodes, and relatively quickly (within
a second or so). If you have queries that read 100'000 or more nodes, it is
quite easy to get into this situation. With less than 200 nodes, it's typically
never a problem. (There's also the case where less than 200 nodes are read, but
very slowly... but that's unlikely).
> Result items are not always correctly counted against the configured read
> limit if a query uses a lucene index
> ---------------------------------------------------------------------------------------------------------------
>
> Key: OAK-8046
> URL: https://issues.apache.org/jira/browse/OAK-8046
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: lucene
> Affects Versions: 1.8.7
> Reporter: Georg Henzler
> Assignee: Vikas Saurabh
> Priority: Major
> Fix For: 1.12.0, 1.10.1, 1.8.12
>
> Attachments: OAK-8046-take2.patch, OAK-8046.patch
>
>
> There are cases where an index is re-opened during query execution. In that
> case, already returned entries are read again and skipped, so basically
> counted twice. This should be fixed to only count entries once (see also [1])
> The issue most likely exists since the read limit was introduced with OAK-6875
> [1]
> https://lists.apache.org/thread.html/dddf9834fee0bccb6e48f61ba2a01430e34fc0b464b12809f7dfe2eb@%3Coak-dev.jackrabbit.apache.org%3E
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
