Hi Bryan,
Thanks for your response.
As it turned out, it was a different issue and involved the java utility
that ExecuteStreamCommand was kicking off. The java utility creates a tmp
directory that happened to clash with another java program running on the
one node where I was having these proble
Hello,
I think the behavior you saw with the queue going to 0 is expected
behavior... when you are looking at the UI it is showing the aggregated
view of all the nodes in the cluster, so if one node has flow files in the
queue and that nodes goes down while you are in the UI in another node,
that
