[
https://issues.apache.org/jira/browse/OAK-4242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15251822#comment-15251822
]
Tomek Rękawek commented on OAK-4242:
------------------------------------
[~jsedding], the issue occurred after a few iterations of the repeated
migration. The performance of the queries on the migrated repository was
deteriorated. The cause was that the index at /oak:index/counter was totally
out of sync, as a result of some large oak-upgrade incremental migrations. This
was pretty obvious on viewing the results of the NodeCounter JMX bean and was
sending the inaccurate costing of the indexes and thus causing the wrong index
to be chosen. The index was rebuilt and the issue went away.
> Counter index should be rebuilt after successful migration
> ----------------------------------------------------------
>
> Key: OAK-4242
> URL: https://issues.apache.org/jira/browse/OAK-4242
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: upgrade
> Reporter: Tomek Rękawek
> Priority: Minor
> Fix For: 1.6, 1.5.2
>
>
> The /oak:index/counter is used to choose the appropriate strategy and indexes
> for a query. It should be rebuilt after every [repeated migration|OAK-2619].
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
