[NIFI-6846] Content Repository may fail to cleanup after Processor throws Exception

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.11.0
• Component/s: Core Framework
• Assignee: Mark Payne
• Reporter: Mark Payne
• Created: 05/Nov/19 18:19
• Updated: 06/Nov/19 14:54
• Resolved: 06/Nov/19 14:54

Description

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.

Issue Links

• links to: GitHub Pull Request #3872