[
https://issues.apache.org/jira/browse/NIFI-5771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16670612#comment-16670612
]
ASF subversion and git services commented on NIFI-5771:
-------------------------------------------------------
Commit 4c10b47e602741adc52ad693a9bc56b9964cd7ef in nifi's branch
refs/heads/master from [~markap14]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=4c10b47 ]
NIFI-5771: Ensure that we only increment claimant count for content claim if we
have a FlowFile that references it
This closes #3118.
Signed-off-by: Bryan Bende <[email protected]>
> If 0-byte FlowFiles are load balanced, can result in content claim not being
> cleaned up
> ---------------------------------------------------------------------------------------
>
> Key: NIFI-5771
> URL: https://issues.apache.org/jira/browse/NIFI-5771
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Critical
> Fix For: 1.9.0
>
>
> To replicate, create two separate Flows:
> GenerateFlowFile (File Size 800 KB) -> UpdateAttribute [auto-terminate]
> GenerateFlowFile (FileSize 0 B) -> UpdateAttribute [auto-terminate]
> On the second one, that is generating 0-byte flowfiles, configure the
> Connection to Load Balance (Round Robin is easiest).
> Start both flows.
> After a minute or two, stop the GenerateFlowFile processors; let the
> flowfiles finish being processed by UpdateAttribute.
> Now, wait for the FlowFile Repository to checkpoint. At this point, the
> content claim should be cleaned up and delete/archive any content claims
> (with the exception of a few claims that are still 'writable'). However, some
> claims are still sticking around when they shouldn't.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
