[
https://issues.apache.org/jira/browse/NIFI-1527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15156172#comment-15156172
]
Mark Payne commented on NIFI-1527:
----------------------------------
Joe - hmm, that does seem odd... I will try to replicate problem and see if i
can figure out why it's behaving this way - or if it's a bug that we need to
address.
> Resource Claim counts not incremented on restart for FlowFiles that are
> swapped out
> -----------------------------------------------------------------------------------
>
> Key: NIFI-1527
> URL: https://issues.apache.org/jira/browse/NIFI-1527
> 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
>
>
> 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 claim.
> 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
(v6.3.4#6332)
