Purushotham, Generally if you run into a situation where you have a stuck thread you will need to provide a thread dump to understand what is going on. It’s easiest to do that by running “bin/nifi.sh dump dump1.txt” and then attaching the created dump1.txt to the email.
Thanks -Mark Sent from my iPhone On Jun 7, 2019, at 3:45 AM, Purushotham Pushpavanthar <[email protected]<mailto:[email protected]>> wrote: Hi, I've been ExecuteSQL to execute some DDL statements whenever there is an update to my S3. This was working fine for me except for one glitch. It stops processing any incoming flowfiles with running threads. Once the processor gets into this state, it never recovers. It's not possible to stop the processor without forcefully terminating it. It starts working fine once I restart it through forceful termination. I went through the mail thread in the link http://apache-nifi-users-list.2361937.n4.nabble.com/ExecuteSQL-question-how-do-I-stop-long-running-queries-td3039.html and tried adding Validation Query, but it didn't help. I'm sending very light weight DDL statements like ALTER TABLE ADD PARTITION. I don't this is causing much load on the Athena End. I've attached my ExecuteSQL and DBConnectionPool configuration. Kindly review it and help me resolve/let me know workaround. Regards Purushotham Pushpavanth <Screenshot 2019-06-07 at 12.58.33 PM.png> <Screenshot 2019-06-07 at 12.59.01 PM.png> <Screenshot 2019-06-07 at 12.58.41 PM.png>
