jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Mueller (Jira)" <j...@apache.org>
Subject [jira] [Resolved] (OAK-9540) SegmentNotFoundException in IndexDefinition.hasMatchingNodeTypeReg
Date Wed, 25 Aug 2021 12:30:00 GMT

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

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

> 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)

Mime
View raw message