[NIFI-731] If content repo is unable to destroy content as fast as it is generated, nifi performance becomes very erratic

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Fix Version/s: 0.2.0
• Component/s: Core Framework
• Assignee: Mark Payne
• Reporter: Mark Payne
• Created: 26/Jun/15 00:05
• Updated: 02/Jul/15 15:55
• Resolved: 02/Jul/15 15:55

Description

When the FlowFile Repository marks claims as destructable, it puts the notification on a queue that the content repo pulls from. If the content repo cannot keep up, the queue will fill, resulting in backpressure, that prevents the FlowFile repository from being updated. This, in turn, causes Processors to block, waiting on space to become available. This is by design.

However, the capacity of this queue is quite large, and the content repo drains the entire queue, then destroys all content claims that are on it. As a result, this act of destroying claims can be quite long, and Processors can block for quite a period of time, leading to very sporadic performance.

Instead, the content repo should pull from the queue and destroy the claims one at a time or in small batches, instead of draining the entire queue each time. This should result in much less sporadic behavior.

Issue Links

• is related to: NIFI-744 Allow FileSystemRepository to write to the same file for multiple (non-parallel) sessions
• relates to: NIFI-744 Allow FileSystemRepository to write to the same file for multiple (non-parallel) sessions