[
https://issues.apache.org/jira/browse/NIFI-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joseph Witt updated NIFI-2452:
------------------------------
Description:
I occasionally see when I run Provenance queries against an active provenance
repository that the JVM will crash, writing out an hs_err_pid_XXX.log file.
This appears to be related to https://issues.apache.org/jira/browse/LUCENE-7183
which indicates that it's caused by using a closed IndexReader.
Adding to description from nice Github comments from mark:
Ensure that we keep track of how many references we have to each lucene
searcher and only close the underlying index reader if there are no references
to the searcher. Also updated to prefer newer provenance events over older
provenance events, and calculate FlowFile lineage based on an event id instead
of a FlowFile UUID, as it's much more efficient
was:I occasionally see when I run Provenance queries against an active
provenance repository that the JVM will crash, writing out an
hs_err_pid_XXX.log file. This appears to be related to
https://issues.apache.org/jira/browse/LUCENE-7183 which indicates that it's
caused by using a closed IndexReader.
> Provenance Repository's Index Readers can be prematurely closed
> ---------------------------------------------------------------
>
> Key: NIFI-2452
> URL: https://issues.apache.org/jira/browse/NIFI-2452
> Project: Apache NiFi
> Issue Type: Sub-task
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Joseph Witt
> Priority: Blocker
> Fix For: 1.0.0
>
>
> I occasionally see when I run Provenance queries against an active provenance
> repository that the JVM will crash, writing out an hs_err_pid_XXX.log file.
> This appears to be related to
> https://issues.apache.org/jira/browse/LUCENE-7183 which indicates that it's
> caused by using a closed IndexReader.
> Adding to description from nice Github comments from mark:
> Ensure that we keep track of how many references we have to each lucene
> searcher and only close the underlying index reader if there are no
> references to the searcher. Also updated to prefer newer provenance events
> over older provenance events, and calculate FlowFile lineage based on an
> event id instead of a FlowFile UUID, as it's much more efficient
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)