I would further interested check nifi-user.log to see the forbidden events when you see  403 error  ... View more

403 : Client is not authorized to make this request.  This means you are Authenticated and since you have a valid token but you are not authorized to do this action. to double-check if your user is Authorized, check if you can do the same action directly from NiFi UI ?   Thank you  ... View more

If you have  to load the new template from the filesystem/local to the NiFi cluster, the following API call should be made with POST method  nifi-api/process-groups/{pg-id}/templates/upload Thank you     ... View more

When a specific node is down, all the new ingestion will be handled by the remaining nodes.  But the data queued on the down node will be there on that node until the node comes back. If this is HW failure such as disk failure and the node can't be brought back, stuck data will be lost.  Since NiFi is not a storage system but more of an In/out pipeline, we expect the data that is pushed to NiFi not to be the only copy. systems that are pushing data to NiFi should have some room to keep the data intact for some buffer days/hrs until it is processed. NiFi does not provide any sort of backup/restore or real-time replication. To avoid such data loss it is expected to have the data at source for some time until data is processed by NiFi for further downstream processing.  Hope this helps. Thank you      ... View more

Thanks, The Error message tells me that "access unknown certificate of token not found"  This means NiFi as a service expects client cert to be present if there are No client certs then a token must be present which would be obtained after entering the user name password. But in LB connection it is possible that the token has been obtained from one nifi node but LB is redirecting the next request to a different NiFi node and it will not work  Have you configured the stick session at the Load Balancing Proxy? Refer to why it is needed in NiFi  https://community.cloudera.com/t5/Support-Questions/Nifi-authentication-fails-when-a-HTTPS-load-balancer-is-used/td-p/343785 https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#proxy_configuration https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#session_affinity     ... View more

How you are trying to log in? using certificate? or Username&Passsword ? Is NiFi running on the container?     ... View more

Looking at the thread, Ans is No, that's not the way NiFi Processor is meant to handle relationships, The Client Processor has to initialize /start properly with the given configuration then only it can try to write and then based on the write results flow files can be routed to failure or success, Here Processor can't even start properly.    ... View more

The reported behavior with Lock wait timeout in Mysql/MariaDB is not in control of NiFi PutSQL, You have to check your DB Table for possible issues.  Thank you  ... View more

You can evaluate the following for better approach  1. Batch use case with ListSFTP/FetchSFTP 2 . ExecuteStateless processor   Thank you    ... View more