[
https://issues.apache.org/jira/browse/NIFI-2920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15592346#comment-15592346
]
Mark Payne commented on NIFI-2920:
----------------------------------
After looking into this some more, I believe that what I have replicated here
is actually a different bug that affects only version 1.0. The symptoms are
similar if not identical. However, the problem appears to not be the same, as I
can easily reproduce the problem in version 1.0 but cannot reproduce the
problem in the 0.x baseline. I tried in both 0.7.0 and 0.6.1. Given that you
have reported this as a bug in 0.6.1, I think they are different. I have
created a new ticket (NIFI-2925) to address the issue that affects 1.0 and will
submit a PR for that problem momentarily. I can see in the code that problem in
1.0 would not affect the 0.x branch. So I have marked the tickets as related
but not the same.
> Swapped FlowFiles are not removed from content repo when a queue is emptied.
> ----------------------------------------------------------------------------
>
> Key: NIFI-2920
> URL: https://issues.apache.org/jira/browse/NIFI-2920
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 0.6.1
> Environment: Linux
> Reporter: Matthew Clarke
> Priority: Critical
>
> If a queue contains enough FlowFiles to trigger swapping to occur and a user
> selects "empty queue" or sets file expiration, only the content claims
> associated to FlowFiles that were not swapped get removed from the content
> repository. All other content claims are left in the content repository and
> are not moved to archive and/or purged.
> A restart of NiFi will produce app log messages about these unknown files
> left in the content repo and will at that time move them to archive or purge
> them.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
