@ismail patel Flow files are queued of course because the processor is only running on the primary node. GetFile in a cluster is not the best way to get data into your flow. It would be better to use a ListFile and then a FetchFile processor. Configure each processor in that flow to run on primary node only or have two flow paths, one on primary node only and then a second flow that runs on all nodes. ... View more

@Richard Corfiel Question 1, there is currently no tool to do what you need. Question 2, The process you should follow to clear the repos -- stop NiFi, clean out the flowfile and content repos, then restart NiFi. You should not see any issues in the log file after that. What is the issue you are seeing with the MergeContent processor? What is the configuration of the MergeContent processor and how many/how large a file are you trying to create? ... View more

@Juthika Shenoy Have you manually tried to sftp to the remote system using the private key from the command line of the system running NiFi? Usually, the first time you connect to a system you are prompted to accept the key. ... View more

@siva karna You could the RouteOnAttribute processor. The SplitJson processor writes two attributes to each flow file that can be used to know when the last split flow file reaches the RouteOnAttribute file. fragment.count = The number of split FlowFiles generated from the parent FlowFile and fragment.index = A one-up number that indicates the ordering of the split FlowFiles that were created from a single parent FlowFile (this value starts at 0 for the first flow file) , so in your case, the last flow file would have fragment.index value of 5. So, you could use the expression language to determine when the last flow file arrived to the RouteOnAttribute processor. Here is an example of how you would use the fragment.count and the fragment.index attributes: Any flow file where the values result in a false will be routed out the unmatched relationship. The one flow file where the result will be true is routed out the nextprocessor relationship. ... View more

@Adda Fuentes I just saw the same error in a cluster I have for testing. I was able to make the error occur and the only way it would clear is if I restarted all of the nodes in my cluster at the same time. How you tried that with your cluster yet? ... View more

@Bharadwaj Bhimavarapu If you want to have the processor run every 5 seconds, then you would set that using property "Run Schedule" under the Schedule tab like this ... View more

@Adda Fuentes Are you able to ping the zookeeper systems from the NiFi node that is having the issue? I found an article where another user is seeing this issue. They said they cleared state in the state/zookeeper directory on all of the nodes, but don't remove the myid file, and restarted all of the nodes at the same time. I don't know if this is an option for you or not. Here is a link to the article I found Zookeeper error ... View more