[ 
https://issues.apache.org/jira/browse/NIFI-3897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joseph Gresock updated NIFI-3897:
---------------------------------
    Description: 
A particular queue is listed as having 80,000 flow files, but NiFi thinks there 
are none to list.  I was originally 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.

Update: I happened to reboot my cluster, and suddenly the 80,000 flow files 
went through the flow.  This makes the problem considerably worse, since it 
appears the flow files were "invisible" until the reboot.

  was:
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.

Update: I happened to reboot my cluster, and suddenly the 80,000 flow files 
went through the flow.  This makes the problem considerably worse, since it 
appears the flow files were "invisible" until the reboot.


> Queue with flow files thinks it is empty
> ----------------------------------------
>
>                 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
>         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 was originally 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.
> Update: I happened to reboot my cluster, and suddenly the 80,000 flow files 
> went through the flow.  This makes the problem considerably worse, since it 
> appears the flow files were "invisible" until the reboot.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to