[ 
https://issues.apache.org/jira/browse/NIFI-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15406034#comment-15406034
 ] 

ASF subversion and git services commented on NIFI-2452:
-------------------------------------------------------

Commit 16348b071d361697f517397b2da2ea32c5599c11 in nifi's branch 
refs/heads/master from [~markap14]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=16348b0 ]

NIFI-2452: This closes #771.  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


> 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
> In resolving the JIRA also cleaned up logic for handling heartbeat messages 
> where a few states weren't accounted for leading to an incorrect accounting 
> of heartbeats.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to