@dz902 as this is an older post, you would have a better chance of receiving a resolution by starting a new thread. This will also be an opportunity to provide details specific to your environment that could aid others in assisting you with a more accurate answer to your question. You can link this thread as a reference in your new post. ... View more

@MattWho  Thank you for your input. It works and It was invaluable.    ... View more

This should be addressed by: https://issues.apache.org/jira/browse/NIFI-5065 ... View more

In any way its better to backup logs ... View more

Hi @Matt Clarke Thanks for taking the time to answer my question and confirm that the size of the queued content doesn't include any archived content. I've taken a closer look at the status history of the connection (queue) over the past 24 hours and I can see that the nature of the data flowing in varies depending on the time of day. It seems that earlier in the day a large number of small flow files pass into the queue, but they can be processed rapidly. As the day goes on we start to see flow files of a much larger size. I think this is the explanation as to why the number of flow files decreases but the size of the data increases. This is something I hadn't expected until I looked at the status history closely. Thanks again for helping me get to the bottom of this! Richard ... View more

Hi Matt, Does Clearing flowfile & content repositories clears up state of the processors too? ... View more

We have a similar problem. A MergeContent processor giving out 'is not the most recent version of thisFlowFile within this session' and 'is not known in this session' errors. Also we have the 'phantom' queue that you describe. A large queue that the processor does not process. But when we restart NiFi the queue drops the zero. ... View more