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

ASF GitHub Bot commented on NIFI-2452:
--------------------------------------

Github user markap14 commented on a diff in the pull request:

    https://github.com/apache/nifi/pull/771#discussion_r73220319
  
    --- Diff: 
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/FlowController.java
 ---
    @@ -16,7 +16,38 @@
      */
     package org.apache.nifi.controller;
     
    -import com.sun.jersey.api.client.ClientHandlerException;
    --- End diff --
    
    @joewitt this change was due to a bug that I ran into when testing this PR. 
The bug was preventing me from moving forward, and was a rather trivial fix, so 
I just included it in the PR. I could have created a separate JIRA and PR but 
since it would have blocked this PR it seemed more prudent to just roll it in.


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

Reply via email to