[jira] [Commented] (NIFI-2925) FlowFiles that are swapped out are never released from Content Repository

[Dustin Rodrigues (JIRA)]

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

Dustin Rodrigues commented on NIFI-2925:


[~joewitt] What's your definition of large scale?

> FlowFiles that are swapped out are never released from Content Repository
> -
>
> Key: NIFI-2925
> URL: https://issues.apache.org/jira/browse/NIFI-2925
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Blocker
> Fix For: 1.1.0
>
>
> To reproduce this, I created a simple Flow: GenerateFlowFile (1 KB file size) 
> with success going to 2 different UpdateAttribute Processors (so that the 
> same Content Claim is held by 2 different FlowFiles). I let about 150,000 
> FlowFiles queue up (with backpressure turned off). I then start one of the 
> UpdateAttribute processors. This drained its queue. I could then look at my 
> content repo for any files not archived:
> {code}
> content_repository $ find . -type f | grep -v archive | wc -l
>  192
> {code}
> After a few minutes, the FlowFile repo is checkpointed, which will result in 
> things getting cleaned up if they can. The above command shows the same 
> result (expected, since the FlowFiles are still held. I then empty the queue. 
> After the FlowFile checkpoints again, I should see nothing in the content 
> repo outside of archive, but I see:
> {code}
> content_repository $ find . -type f | grep -v archive | wc -l
>  167
> {code}
> I see the same thing happening if I turn on expiration to remove the 
> FlowFiles instead of clicking Empty Queue, or if a processor runs and 
> completes the processing of the data.



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

[jira] [Commented] (NIFI-2925) FlowFiles that are swapped out are never released from Content Repository

[Joseph Witt (JIRA)]

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

Joseph Witt commented on NIFI-2925:
---

Provenance was reimplemented in the 1.x line many moons ago but not switched as 
the default until recently.  There are a very large number of large scale users 
I know of that leverage that quite successfully.

> FlowFiles that are swapped out are never released from Content Repository
> -
>
> Key: NIFI-2925
> URL: https://issues.apache.org/jira/browse/NIFI-2925
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Blocker
> Fix For: 1.1.0
>
>
> To reproduce this, I created a simple Flow: GenerateFlowFile (1 KB file size) 
> with success going to 2 different UpdateAttribute Processors (so that the 
> same Content Claim is held by 2 different FlowFiles). I let about 150,000 
> FlowFiles queue up (with backpressure turned off). I then start one of the 
> UpdateAttribute processors. This drained its queue. I could then look at my 
> content repo for any files not archived:
> {code}
> content_repository $ find . -type f | grep -v archive | wc -l
>  192
> {code}
> After a few minutes, the FlowFile repo is checkpointed, which will result in 
> things getting cleaned up if they can. The above command shows the same 
> result (expected, since the FlowFiles are still held. I then empty the queue. 
> After the FlowFile checkpoints again, I should see nothing in the content 
> repo outside of archive, but I see:
> {code}
> content_repository $ find . -type f | grep -v archive | wc -l
>  167
> {code}
> I see the same thing happening if I turn on expiration to remove the 
> FlowFiles instead of clicking Empty Queue, or if a processor runs and 
> completes the processing of the data.



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

[jira] [Commented] (NIFI-2925) FlowFiles that are swapped out are never released from Content Repository

[Andrew Glowacki (JIRA)]

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

Andrew Glowacki commented on NIFI-2925:
---

[~joewitt] - I do wish to upgrade, however I am reluctant since my organization 
has had issues with 1.x where critical features such as provenance do not work 
at scale.

> FlowFiles that are swapped out are never released from Content Repository
> -
>
> Key: NIFI-2925
> URL: https://issues.apache.org/jira/browse/NIFI-2925
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Blocker
> Fix For: 1.1.0
>
>
> To reproduce this, I created a simple Flow: GenerateFlowFile (1 KB file size) 
> with success going to 2 different UpdateAttribute Processors (so that the 
> same Content Claim is held by 2 different FlowFiles). I let about 150,000 
> FlowFiles queue up (with backpressure turned off). I then start one of the 
> UpdateAttribute processors. This drained its queue. I could then look at my 
> content repo for any files not archived:
> {code}
> content_repository $ find . -type f | grep -v archive | wc -l
>  192
> {code}
> After a few minutes, the FlowFile repo is checkpointed, which will result in 
> things getting cleaned up if they can. The above command shows the same 
> result (expected, since the FlowFiles are still held. I then empty the queue. 
> After the FlowFile checkpoints again, I should see nothing in the content 
> repo outside of archive, but I see:
> {code}
> content_repository $ find . -type f | grep -v archive | wc -l
>  167
> {code}
> I see the same thing happening if I turn on expiration to remove the 
> FlowFiles instead of clicking Empty Queue, or if a processor runs and 
> completes the processing of the data.



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

[jira] [Commented] (NIFI-2925) FlowFiles that are swapped out are never released from Content Repository

[Joseph Witt (JIRA)]

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

Joseph Witt commented on NIFI-2925:
---

[~andrewglowacki] the 0.7 line came out in July 2016 with 1.x coming out in Aug 
2016.  This means support for 0.7.x line should continue through Aug 2017 which 
it did.  However, there has been no work or focus on it since consistent with 
our stated support model [1].  It will be important to upgrade to the nifi 1.x 
line. There have been massive improvements and security related changes in the 
past two years.  The team put considerable effort into easing the migration 
effort including having newer code support older data structures and configs, 
and zookeeper state migration, etc..

[1] 
https://cwiki.apache.org/confluence/display/NIFI/Git+Branching+and+Release+Line+Management
 

> FlowFiles that are swapped out are never released from Content Repository
> -
>
> Key: NIFI-2925
> URL: https://issues.apache.org/jira/browse/NIFI-2925
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Blocker
> Fix For: 1.1.0
>
>
> To reproduce this, I created a simple Flow: GenerateFlowFile (1 KB file size) 
> with success going to 2 different UpdateAttribute Processors (so that the 
> same Content Claim is held by 2 different FlowFiles). I let about 150,000 
> FlowFiles queue up (with backpressure turned off). I then start one of the 
> UpdateAttribute processors. This drained its queue. I could then look at my 
> content repo for any files not archived:
> {code}
> content_repository $ find . -type f | grep -v archive | wc -l
>  192
> {code}
> After a few minutes, the FlowFile repo is checkpointed, which will result in 
> things getting cleaned up if they can. The above command shows the same 
> result (expected, since the FlowFiles are still held. I then empty the queue. 
> After the FlowFile checkpoints again, I should see nothing in the content 
> repo outside of archive, but I see:
> {code}
> content_repository $ find . -type f | grep -v archive | wc -l
>  167
> {code}
> I see the same thing happening if I turn on expiration to remove the 
> FlowFiles instead of clicking Empty Queue, or if a processor runs and 
> completes the processing of the data.



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

[jira] [Commented] (NIFI-2925) FlowFiles that are swapped out are never released from Content Repository

[Bryan Bende (JIRA)]

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

Bryan Bende commented on NIFI-2925:
---

[~andrewglowacki] this fix was committed to the 0.x branch, you can see the 
comment directly above yours that says "this is a 0.x version of Mark Payne's 
patch".

The commit for 0.x is here - 
[https://github.com/apache/nifi/commit/a9395bc67c2de4fa6ba82ca0573ad210ccc67434]

If there is still an issue I would recommend moving to the latest 1.9.0 
release, as the 0.x branch is officially no longer supported.

> FlowFiles that are swapped out are never released from Content Repository
> -
>
> Key: NIFI-2925
> URL: https://issues.apache.org/jira/browse/NIFI-2925
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Blocker
> Fix For: 1.1.0
>
>
> To reproduce this, I created a simple Flow: GenerateFlowFile (1 KB file size) 
> with success going to 2 different UpdateAttribute Processors (so that the 
> same Content Claim is held by 2 different FlowFiles). I let about 150,000 
> FlowFiles queue up (with backpressure turned off). I then start one of the 
> UpdateAttribute processors. This drained its queue. I could then look at my 
> content repo for any files not archived:
> {code}
> content_repository $ find . -type f | grep -v archive | wc -l
>  192
> {code}
> After a few minutes, the FlowFile repo is checkpointed, which will result in 
> things getting cleaned up if they can. The above command shows the same 
> result (expected, since the FlowFiles are still held. I then empty the queue. 
> After the FlowFile checkpoints again, I should see nothing in the content 
> repo outside of archive, but I see:
> {code}
> content_repository $ find . -type f | grep -v archive | wc -l
>  167
> {code}
> I see the same thing happening if I turn on expiration to remove the 
> FlowFiles instead of clicking Empty Queue, or if a processor runs and 
> completes the processing of the data.



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

[jira] [Commented] (NIFI-2925) FlowFiles that are swapped out are never released from Content Repository

[Andrew Glowacki (JIRA)]

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

Andrew Glowacki commented on NIFI-2925:
---

This is still an issue in 0.7.3. Why was this not ported to 0.x?

> FlowFiles that are swapped out are never released from Content Repository
> -
>
> Key: NIFI-2925
> URL: https://issues.apache.org/jira/browse/NIFI-2925
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Blocker
> Fix For: 1.1.0
>
>
> To reproduce this, I created a simple Flow: GenerateFlowFile (1 KB file size) 
> with success going to 2 different UpdateAttribute Processors (so that the 
> same Content Claim is held by 2 different FlowFiles). I let about 150,000 
> FlowFiles queue up (with backpressure turned off). I then start one of the 
> UpdateAttribute processors. This drained its queue. I could then look at my 
> content repo for any files not archived:
> {code}
> content_repository $ find . -type f | grep -v archive | wc -l
>  192
> {code}
> After a few minutes, the FlowFile repo is checkpointed, which will result in 
> things getting cleaned up if they can. The above command shows the same 
> result (expected, since the FlowFiles are still held. I then empty the queue. 
> After the FlowFile checkpoints again, I should see nothing in the content 
> repo outside of archive, but I see:
> {code}
> content_repository $ find . -type f | grep -v archive | wc -l
>  167
> {code}
> I see the same thing happening if I turn on expiration to remove the 
> FlowFiles instead of clicking Empty Queue, or if a processor runs and 
> completes the processing of the data.



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

[jira] [Commented] (NIFI-2925) FlowFiles that are swapped out are never released from Content Repository

[ASF subversion and git services (JIRA)]

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

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

Commit a9395bc67c2de4fa6ba82ca0573ad210ccc67434 in nifi's branch refs/heads/0.x 
from [~bbende]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=a9395bc ]

NIFI-2920 This is a 0.x version of Mark Payne's patch for NIFI-2925


> FlowFiles that are swapped out are never released from Content Repository
> -
>
> Key: NIFI-2925
> URL: https://issues.apache.org/jira/browse/NIFI-2925
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Blocker
> Fix For: 1.1.0
>
>
> To reproduce this, I created a simple Flow: GenerateFlowFile (1 KB file size) 
> with success going to 2 different UpdateAttribute Processors (so that the 
> same Content Claim is held by 2 different FlowFiles). I let about 150,000 
> FlowFiles queue up (with backpressure turned off). I then start one of the 
> UpdateAttribute processors. This drained its queue. I could then look at my 
> content repo for any files not archived:
> {code}
> content_repository $ find . -type f | grep -v archive | wc -l
>  192
> {code}
> After a few minutes, the FlowFile repo is checkpointed, which will result in 
> things getting cleaned up if they can. The above command shows the same 
> result (expected, since the FlowFiles are still held. I then empty the queue. 
> After the FlowFile checkpoints again, I should see nothing in the content 
> repo outside of archive, but I see:
> {code}
> content_repository $ find . -type f | grep -v archive | wc -l
>  167
> {code}
> I see the same thing happening if I turn on expiration to remove the 
> FlowFiles instead of clicking Empty Queue, or if a processor runs and 
> completes the processing of the data.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-2925) FlowFiles that are swapped out are never released from Content Repository

[ASF subversion and git services (JIRA)]

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

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

Commit e1f0ba5a43811561d2dce09914ca87db4a3e1738 in nifi's branch 
refs/heads/master from [~markap14]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=e1f0ba5 ]

NIFI-2925: When swapping in FlowFiles, do not assume that its Resource Claim is 
'in use' but instead look up the canonical representation of the resource claim

This closes #1150.

Signed-off-by: Bryan Bende 


> FlowFiles that are swapped out are never released from Content Repository
> -
>
> Key: NIFI-2925
> URL: https://issues.apache.org/jira/browse/NIFI-2925
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Blocker
> Fix For: 1.1.0
>
>
> To reproduce this, I created a simple Flow: GenerateFlowFile (1 KB file size) 
> with success going to 2 different UpdateAttribute Processors (so that the 
> same Content Claim is held by 2 different FlowFiles). I let about 150,000 
> FlowFiles queue up (with backpressure turned off). I then start one of the 
> UpdateAttribute processors. This drained its queue. I could then look at my 
> content repo for any files not archived:
> {code}
> content_repository $ find . -type f | grep -v archive | wc -l
>  192
> {code}
> After a few minutes, the FlowFile repo is checkpointed, which will result in 
> things getting cleaned up if they can. The above command shows the same 
> result (expected, since the FlowFiles are still held. I then empty the queue. 
> After the FlowFile checkpoints again, I should see nothing in the content 
> repo outside of archive, but I see:
> {code}
> content_repository $ find . -type f | grep -v archive | wc -l
>  167
> {code}
> I see the same thing happening if I turn on expiration to remove the 
> FlowFiles instead of clicking Empty Queue, or if a processor runs and 
> completes the processing of the data.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-2925) FlowFiles that are swapped out are never released from Content Repository

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2925:
--

Github user asfgit closed the pull request at:

https://github.com/apache/nifi/pull/1150


> FlowFiles that are swapped out are never released from Content Repository
> -
>
> Key: NIFI-2925
> URL: https://issues.apache.org/jira/browse/NIFI-2925
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Blocker
> Fix For: 1.1.0
>
>
> To reproduce this, I created a simple Flow: GenerateFlowFile (1 KB file size) 
> with success going to 2 different UpdateAttribute Processors (so that the 
> same Content Claim is held by 2 different FlowFiles). I let about 150,000 
> FlowFiles queue up (with backpressure turned off). I then start one of the 
> UpdateAttribute processors. This drained its queue. I could then look at my 
> content repo for any files not archived:
> {code}
> content_repository $ find . -type f | grep -v archive | wc -l
>  192
> {code}
> After a few minutes, the FlowFile repo is checkpointed, which will result in 
> things getting cleaned up if they can. The above command shows the same 
> result (expected, since the FlowFiles are still held. I then empty the queue. 
> After the FlowFile checkpoints again, I should see nothing in the content 
> repo outside of archive, but I see:
> {code}
> content_repository $ find . -type f | grep -v archive | wc -l
>  167
> {code}
> I see the same thing happening if I turn on expiration to remove the 
> FlowFiles instead of clicking Empty Queue, or if a processor runs and 
> completes the processing of the data.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-2925) FlowFiles that are swapped out are never released from Content Repository

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2925:
--

Github user bbende commented on the issue:

https://github.com/apache/nifi/pull/1150
  
Reviewing...


> FlowFiles that are swapped out are never released from Content Repository
> -
>
> Key: NIFI-2925
> URL: https://issues.apache.org/jira/browse/NIFI-2925
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Blocker
> Fix For: 1.1.0
>
>
> To reproduce this, I created a simple Flow: GenerateFlowFile (1 KB file size) 
> with success going to 2 different UpdateAttribute Processors (so that the 
> same Content Claim is held by 2 different FlowFiles). I let about 150,000 
> FlowFiles queue up (with backpressure turned off). I then start one of the 
> UpdateAttribute processors. This drained its queue. I could then look at my 
> content repo for any files not archived:
> {code}
> content_repository $ find . -type f | grep -v archive | wc -l
>  192
> {code}
> After a few minutes, the FlowFile repo is checkpointed, which will result in 
> things getting cleaned up if they can. The above command shows the same 
> result (expected, since the FlowFiles are still held. I then empty the queue. 
> After the FlowFile checkpoints again, I should see nothing in the content 
> repo outside of archive, but I see:
> {code}
> content_repository $ find . -type f | grep -v archive | wc -l
>  167
> {code}
> I see the same thing happening if I turn on expiration to remove the 
> FlowFiles instead of clicking Empty Queue, or if a processor runs and 
> completes the processing of the data.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-2925) FlowFiles that are swapped out are never released from Content Repository

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2925:
--

GitHub user markap14 opened a pull request:

https://github.com/apache/nifi/pull/1150

NIFI-2925: When swapping in FlowFiles, do not assume that its Resourc…

Thank you for submitting a contribution to Apache NiFi.

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

### For all changes:
- [ ] Is there a JIRA ticket associated with this PR? Is it referenced 
 in the commit message?

- [ ] Does your PR title start with NIFI- where  is the JIRA number 
you are trying to resolve? Pay particular attention to the hyphen "-" character.

- [ ] Has your PR been rebased against the latest commit within the target 
branch (typically master)?

- [ ] Is your initial contribution a single, squashed commit?

### For code changes:
- [ ] Have you ensured that the full suite of tests is executed via mvn 
-Pcontrib-check clean install at the root nifi folder?
- [ ] Have you written or updated unit tests to verify your changes?
- [ ] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)? 
- [ ] If applicable, have you updated the LICENSE file, including the main 
LICENSE file under nifi-assembly?
- [ ] If applicable, have you updated the NOTICE file, including the main 
NOTICE file found under nifi-assembly?
- [ ] If adding new Properties, have you added .displayName in addition to 
.name (programmatic access) for each of the new properties?

### For documentation related changes:
- [ ] Have you ensured that format looks appropriate for the output in 
which it is rendered?

### Note:
Please ensure that once the PR is submitted, you check travis-ci for build 
issues and submit an update to your PR as soon as possible.

…e Claim is 'in use' but instead look up the canonical representation of 
the resource claim

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/markap14/nifi NIFI-2925

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/nifi/pull/1150.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1150


commit 8646652c9263c3ff8ba4d51426375ca5f9b6f5eb
Author: Mark Payne 
Date:   2016-10-19T20:48:55Z

NIFI-2925: When swapping in FlowFiles, do not assume that its Resource 
Claim is 'in use' but instead look up the canonical representation of the 
resource claim




> FlowFiles that are swapped out are never released from Content Repository
> -
>
> Key: NIFI-2925
> URL: https://issues.apache.org/jira/browse/NIFI-2925
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Blocker
> Fix For: 1.1.0
>
>
> To reproduce this, I created a simple Flow: GenerateFlowFile (1 KB file size) 
> with success going to 2 different UpdateAttribute Processors (so that the 
> same Content Claim is held by 2 different FlowFiles). I let about 150,000 
> FlowFiles queue up (with backpressure turned off). I then start one of the 
> UpdateAttribute processors. This drained its queue. I could then look at my 
> content repo for any files not archived:
> {code}
> content_repository $ find . -type f | grep -v archive | wc -l
>  192
> {code}
> After a few minutes, the FlowFile repo is checkpointed, which will result in 
> things getting cleaned up if they can. The above command shows the same 
> result (expected, since the FlowFiles are still held. I then empty the queue. 
> After the FlowFile checkpoints again, I should see nothing in the content 
> repo outside of archive, but I see:
> {code}
> content_repository $ find . -type f | grep -v archive | wc -l
>  167
> {code}
> I see the same thing happening if I turn on expiration to remove the 
> FlowFiles instead of clicking Empty Queue, or if a processor runs and 
> completes the processing of the data.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)