Re: Queue incoherent state

Hi again, Unfortunately I didn't save the logs when the node restarted, but I don't remember anything that provided me a clue regarding the reason of the blocked queue. I just have a few logs during the week-end when the queues were in this strange state: 2017-05-14 09:01:29,635 INFO

Re: Queue incoherent state

Arnaud, Did you have any WARN or ERROR messages in the logs? I'm particular interested in anything that mentions the word "Swap" or "swap" (i.e., regardless of case). Is it possible that the FlowFile Repository could have run out of disk space? Thanks -Mark On May 16, 2017, at 3:34 AM, Arnaud

Re: Queue incoherent state

Thanks for following up with these details. I'm going to add these observations to the corresponding JIRA [1]. Thanks and sorry again for the inconvenience. Matt [1] https://issues.apache.org/jira/browse/NIFI-3897 On Tue, May 16, 2017 at 3:34 AM, Arnaud G wrote: > Hi

Re: Queue incoherent state

Hi Matt, Thanks for your reply! I finally solved the problem by deleting all the content in the flowfile directory, but here are my observations: 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

Re: Queue incoherent state

Sorry for the delayed response. Similar behavior has been reported by some other users [1]. Does the connection have any back pressure threshold configured? Can new flowfiles be enqueued? Do the expiration settings have any affect? Lastly, if you restart the cluster does it claim the connection

Queue incoherent state

Hi again! I currently have another issue with incoherent queue status. Following the upgrade to 1.2 of a cluster, I have a couple of queues that display through the GUI a high number of flowfiles. As the queue were no emptying despite tuning, I tried to list the content of the queue. This