[
https://issues.apache.org/jira/browse/OAK-9540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17404401#comment-17404401
]
Thomas Mueller commented on OAK-9540:
-------------------------------------
Merged in trunk.
Also in the 1.22 branch in
https://github.com/apache/jackrabbit-oak/commit/37a6d47b27cd7393812fa34c23b5dc68170daef3
> SegmentNotFoundException in IndexDefinition.hasMatchingNodeTypeReg
> ------------------------------------------------------------------
>
> Key: OAK-9540
> URL: https://issues.apache.org/jira/browse/OAK-9540
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: indexing, query
> Reporter: Thomas Mueller
> Assignee: Thomas Mueller
> Priority: Major
> Fix For: 1.42.0, 1.22.9
>
>
> We sometimes see a SegmentNotFoundException when calling
> IndexDefinition.hasMatchingNodeTypeReg. This can happen after segment store
> GC was run, but before the index definitions are refreshed. In theory, it
> should never happen, as the index definitions are refreshed after compaction
> via LuceneIndexProviderService.registerGCMonitor. But it looks like this
> method is not called in all cases, or it is called too late / too early.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
