You can use InvokeHTTP processor wich provide options to handle Header    Thank you ... View more

You can refer to this article and tune the logback.xml file to delete and rollover based log files based on you space constraints https://community.cloudera.com/t5/Community-Articles/Understanding-how-the-logback-xml-configuration-in-NiFi/ta-p/248662   If you found this response assisted with your issue, please take a moment to login and click on "Accept as Solution" below this post. Thank you, Chandan ... View more

Before starting processor ListenHHTP , please check and make sure port 8888 is not used by any other process at host where nifi service is running. You can use netstat command to check and confirm.    If you found this response assisted with your issue, please take a moment to login and click on "Accept as Solution" below this post. Thank you, Chandan  ... View more

Trying to understand the relationship between upload template action and the error you have seen in logs, so the error is related to a sync issue between NiFi Flow and NiFi Regsitry Version control and is not related to uploading template in NiFi UI    Are you this error only appear when you try uploading templates in NiFi UI ?  Just to discard the error here can you please check in NiFi UI search for component with id b2b33551-8e13-1429-bd99-94bc96edf954 and see if get any component listed in search results and verify the status of that component with version control.   Now the 2nd point, is when you see unable to upload message box Is this nifi service is secure? then you can check in nifi-user.log for any events with your username after template uplod action Check if any timeout related message reported in nifi-app.log after template upload action? how big template is ?  Can you please try with very small template ?   The above action items can help isolate the issue further.    Thank You        ... View more

This line "The problem occurs when InvokeHttp tries to resend data and it consumes so many threads that ListenSyslog starts dropping incoming data"  My understanding is that InvokeHttp will try run with max number of threads based upon what is configured concurrent task settings, beyond that it will not use any more threads at the same ListenSyslog is also running with it own concurrent task setting and max threads it can use and which can be further tune to hold more request based on settings Max Size of Message Queue and Max Size of Socket Buffer and Max Number of TCP Connections.   To hold your initial anaylsys between InvokeHTTP and ListenSyslog you can provide more details around your flow design when the issue occurs like screen shots of flow, configs setting for ListenSyslg and InvokeHTTP would help more to understand.   Thank You ... View more

Running Stored procedures from NiFi sql based processors  is not possible however you can use following suggestion suggested at https://community.cloudera.com/t5/Support-Questions/Execute-Stored-Procedure-of-MSSQL-in-Nifi/m-p/213365   Thank You. ... View more

State can be deleted from view state option on TailFile  processor , the when processor is stopped but it will clear the entire state for tailfile processor, in subsequent run , tailfile file may end up reading the same file again in case file is present. I do not think any harm in keeping the state for files even if files are deleted from the source, Do you have any specific requirements here? or any issues? ... View more