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

Thomas Mueller updated OAK-9540:
--------------------------------
    Description: 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.  (was: 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.)

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

Reply via email to