@Sean Murphy Each Node in a NiFi cluster runs its own threads within its own processor working on its own set of FlowFiles. Nodes in a NiFi cluster have no knowledge of what FlowFiles are being worked on by other nodes. If you are seeing multiple copies of the same output, that suggest that each node in your cluster is processing the same files. I am not sure how your dataflow is designed to ingest the data it works on, but ideally you want to design it in such a way to prevent each node from ingesting the same data/files. Thanks, Matt ... View more

@Mothilal marimuthu Those processor were not introduced until Apache NiFi 1.0 / HDF 2.0. You screen shot shows you running NiFi 0.3 / HDF 1.1. ... View more

@Philippe Marseille The content size displayed in a the UI will not map exactly to disk utilization since Nifi stores multiple FlowFiles in a single claim in the content repo. A claim cannot be deleted until Every FlowFile in contains has reached a point of termination in your dataflow. so it is possible with 450,000 queued FlowFiles you are holding on to a large number of claims still. Try clearing out some of this backlog and see if disk usage drops. Setting backpressure thresholds on connections is good way to prevent your queues from getting so large. Another possibility is that you are running in to https://issues.apache.org/jira/browse/NIFI-2925 . This bug has been addressed for the next Apache NiFi release of 1.1 and HDF 2.1 Thanks, Matt ... View more