[
https://issues.apache.org/jira/browse/NIFI-3897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16012233#comment-16012233
]
Matt Gilman commented on NIFI-3897:
-----------------------------------
Observations from another mailing list message
{noformat}
1) The problem was coming from one of the cluster node, when this node was out
of the cluster, the queue were reporting 0 flowfile.
2) The first time I restarted this node, about 20'000 flowfile reappeared and
were treated, every time I subsequently restarted this node about 20-30k
flowfiles were again treated (I was only specifically monitoring one queue, but
it happened for multiple other queues)
3) After 3-4 reboots of this node the queue reported 90K elements and remained
in this state despite multiple other restart.
4) The flowfile directory on this node contained 200 MB of data
5) I tried to setup the flowfile expiration but it didn't do anything to the
queue status
6) I tried to change the backpressure threshold without any effect.
7) During the problem the queue was operating normally on the cluster, and
flowfiles were flowing through it without any issue.
{noformat}
> Empty queue displays a non-zero flow file count
> -----------------------------------------------
>
> Key: NIFI-3897
> URL: https://issues.apache.org/jira/browse/NIFI-3897
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.2.0
> Reporter: Joseph Gresock
> Priority: Minor
> Attachments: queue-has-no-flowfiles.png
>
>
> A particular queue is listed as having 80,000 flow files, but NiFi thinks
> there are none to list. I am inclined to believe that the queue is indeed
> empty, and that there is somehow a pointer to 80,000 flow files leftover on
> the queue.
> Unfortunately, the logs have rolled over so I can't see what error or warning
> messages may have happened at the time, and I can't reproduce it reliably.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
