@MaarufB  You must have a lot of logging enabled that you expect multiple 10MB app.log files per minute. Was NiFi ever rolling files? Check your NiFi app.log for any Out of Memory (OOM) exceptions.  Does not matter what class is throwing the OOM(s), once the NiFi process is having memory issues, it impacts everything within that service.  If this is the case, you'll need to make changes to your dataflow(s) or increase the NiFi heap memory. Secondly, check to make sure you have sufficient file handles for your NiFi process user. For example; - If your NiFi service is owned by the "nifi" user, make sure the open file limit is set to a very large value for this user (999999).    A restart of the NiFi service before the change to file handles will be applied. If you found that the provided solution(s) assisted you with your query, please take a moment to login and click Accept as Solution below each response that helped. Thank you, Matt ... View more

Did anyone have fix to this issue? I am encountering it also. I am using NiFi 1.16.1. The nifi-app.log is exceeding the 100MB maxFile in the setting.   ... View more

Sorry my bad, I forgot to reply here. Anyways I was able to fix the issue by clearing the cookies in the Postman and Put my Bearer token to the Authorization Header. Thanks for the help by the way. ... View more

Hello bro @SAMSAL , were you successfully control the nifi component using postman? If yes, would it be okay to share your countermeasure. Currently encountering the same issue that you had. Thanks in advance.   ... View more

@MaarufB Please make a new post with as much detail as you can around your question and use case.  This is an old topic and will not get a good response in the comments.  Feel free to @ tag me in the new post. ... View more

How did anyone solve this issue? I was currently trying to solve similar issue via nifi api (Postman) ... View more