[jira] [Commented] (NIFI-6150) Content Repo not getting cleaned up

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFI-6150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16807168#comment-16807168 ] 

ASF subversion and git services commented on NIFI-6150:
-------------------------------------------------------

Commit c1b478b893f4211d5843e64e81060a32aeaaf20d in nifi's branch refs/heads/NIFI-6169-RC1 from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=c1b478b ]

NIFI-6150: Moved logic of decrementing content claims from ProcessSession.commit to the FlowFile Repository. Also updated load-balancing protocol and queue drop logic to no longer decrement content claims since the flowfile repo will handle the logic. This allows us ts to ensure that the claimant counts are decremented only if the repo is successfully updated and still before checking if the claim is still in use or not.

This closes #3391.

Signed-off-by: Bryan Bende <bb...@apache.org>


> Content Repo not getting cleaned up
> -----------------------------------
>
>                 Key: NIFI-6150
>                 URL: https://issues.apache.org/jira/browse/NIFI-6150
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>    Affects Versions: 1.9.1
>            Reporter: Mark Payne
>            Assignee: Mark Payne
>            Priority: Blocker
>             Fix For: 1.10.0, 1.9.2
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> In version 1.9.1, we made a fix for NIFI-6110 that prevented a Content Claim's count from being decremented if the FlowFile Repository fails to update. This was done to avoid a potential data loss bug. However, it had an adverse effect of causing Content Claims to never be cleaned up in some cases, which can lead to the Content Repository filling up and running out of disk space.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)