[NIFI-2925] FlowFiles that are swapped out are never released from Content Repository

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 1.0.0
• Fix Version/s: 1.1.0
• Component/s: Core Framework
• Assignee: Mark Payne
• Reporter: Mark Payne
• Created: 20/Oct/16 16:51
• Updated: 23/Feb/19 14:22
• Resolved: 31/Oct/16 14:00

Description

To reproduce this, I created a simple Flow: GenerateFlowFile (1 KB file size) with success going to 2 different UpdateAttribute Processors (so that the same Content Claim is held by 2 different FlowFiles). I let about 150,000 FlowFiles queue up (with backpressure turned off). I then start one of the UpdateAttribute processors. This drained its queue. I could then look at my content repo for any files not archived:

content_repository $ find . -type f | grep -v archive | wc -l
     192

After a few minutes, the FlowFile repo is checkpointed, which will result in things getting cleaned up if they can. The above command shows the same result (expected, since the FlowFiles are still held. I then empty the queue. After the FlowFile checkpoints again, I should see nothing in the content repo outside of archive, but I see:

content_repository $ find . -type f | grep -v archive | wc -l
     167

I see the same thing happening if I turn on expiration to remove the FlowFiles instead of clicking Empty Queue, or if a processor runs and completes the processing of the data.

Issue Links

• is related to: NIFI-2920 Swapped FlowFiles are not removed from content repo when a queue is emptied.
• links to: GitHub Pull Request #1150