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 still has flowfiles enqueued? Matt [1] https://issues.apache.org/jira/browse/NIFI-3897 On Fri, May 12, 2017 at 5:47 AM, Arnaud G <[email protected]> wrote: > 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 action returns that the queue contains no flowfile, > which is not the expected as the GUI displays another value. > > If I try to empty the queue, I receive a message: 0 FlowFiles (0 bytes) > out of 210'000 (92.71MB) were removed from the queue. > > And of course I cannot delete the queue as this action reports me that the > queue is not empty. > > So somehow it seems that the queue are empty but that the current display > of the queue don't reflect it (it is very likely that some data were lost > during the upgrade procedure as we had to reboot a few node to change the > heap property) > > What will be the best method to restore a proper state and be able to edit > the flow file again? > > Thank you! > > Arnaud > > >
