[
https://issues.apache.org/jira/browse/NIFI-6846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Gilman updated NIFI-6846:
------------------------------
Fix Version/s: 1.11.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Content Repository may fail to cleanup after Processor throws Exception
> -----------------------------------------------------------------------
>
> Key: NIFI-6846
> URL: https://issues.apache.org/jira/browse/NIFI-6846
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
> Fix For: 1.11.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> If a Processor throws an Exception while writing to a FlowFile, the Content
> Claim that gets created for the FlowFile may not get cleaned up. To
> demonstrate this, create a ConvertRecord processor. For the Record Reader,
> use a CSV Reader. Feed it a CSV file where the content is malformed at some
> point in the middle of the CSV file. Loop the failure relationship back to
> the ConvertRecord processor.
> After the FlowFile has failed several times, the Processor can be stopped. At
> this point, you can determine how many resource claims exist in the Content
> Repository by running the following command:
> `find content_repository -type f | grep -v archive | wc -l`
> This number should be approximately equal to 1 + the number of failures.
> However, after the FlowFile Repository is checkpointed, running the command
> again should yield approximately 1, not 1 + the number of failures. But
> currently, I'm seeing 1 + the number of failures.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
