nifi-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Payne (JIRA)" <>
Subject [jira] [Commented] (NIFI-1527) Resource Claim counts not incremented on restart for FlowFiles that are swapped out
Date Mon, 22 Feb 2016 16:52:18 GMT


Mark Payne commented on NIFI-1527:

Joe - yes, the 2 KB should be applied to master (and support). The 39 KB patch i think had
some minor tweaks to the Javadocs that i unintentionally pushed without uploading the patch.
However, the logic is all correct in both cases, and master & support branches are up
to date with the appropriate Javadocs. You should be able to apply the 2 KB patch without
issue. Please let me know if not.


> Resource Claim counts not incremented on restart for FlowFiles that are swapped out
> -----------------------------------------------------------------------------------
>                 Key: NIFI-1527
>                 URL:
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>            Reporter: Mark Payne
>            Assignee: Mark Payne
>            Priority: Blocker
>             Fix For: 0.6.0, 0.5.1
>         Attachments: 0001-NIFI-1527-Ensure-that-we-increment-Claimant-Counts-f.patch,
0001-NIFI-1527-Ensure-that-we-increment-Claimant-Counts-f.patch, 0001-NIFI-1527-Ensure-that-we-increment-Claimant-Counts-f.patch,
> When NiFi starts, it tallies the count of how many FlowFiles reference each Resource
Claim and then removes or archives any file in the Content Repository for which there is no
> However, the claim counts are not incremented for data that is swapped out. As a result,
the content repository could delete or archive data on restart that it should not. This could
potentially result in data loss, if NiFi is restarted while both of the following conditions
are met:
> * All FlowFiles that reference a Resource Claim are swapped out
> * Content Repository's archive is disabled, or the archival threshold is already exceeded
from data outside of the Content Repository

This message was sent by Atlassian JIRA

View raw message