@chitrarthasur, Has the reply helped resolve your issue? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future.  ... View more

@chitrarthasur ,   The processor that you're using is not the ListenHTTP processor, but the HandleHttpRequest, correct? When you use HandleHttpRequest, you must always connect that processor to a HandleHttpResponse processor so that NiFi can send a response back to the client. With this you can ingest the content of the request, process it in NiFi and send a response according to the results of your processing.   If your only requirement is to ingest the content of the HTTP request, you should use a ListenHTTP instead.   Cheers, André   ... View more

Deleting that state directory should not be a normal maintenance function. What you initially described is a very odd case. The fact that your node went down 003 and if it was the primary node or the coordinator node, internally there would have been a election to nominate a new cluster member node to perform those functions.   In your case node 003 is a member of the cluster but it is not connected. Why it is not connected could be the cause of n reasons typically node is down or it was manually disconnected. When you see that message how many member nodes do you have? I expect the UI to show 2/3 because node 3 is not connected. The solution is to connect it by fixing the issue of why node is down or connect it through the UI     ... View more