[NIFI-9093] Add timeouts to avoid GetSplunk processor hanging

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.12.1
• Fix Version/s: 1.16.0, 1.15.1
• Component/s: Core Framework
• Labels: easy-fix newbie
• Environment: NiFi 3 nodes cluster - 40 CPU core +28 GB of RAM per node
• Flags: Important
• Assignee: Joe Witt
• Reporter: Michael Elbraish
• Created: 25/Aug/21 13:58
• Updated: 13/Dec/21 18:43
• Resolved: 07/Dec/21 15:21

Description

I configured GetSplunk to run on cron schedule every 2 min, sometimes when there's no data to retrieve from Splunk, the job thread hangs with no issues or outputs and keeps running, blocking the new scheduled jobs from starting until I stop--> terminate --> start processor.

 
1- Why this happened in the first place, that the threads of GetSplunk kept hanging
2- How to over come such situation in the future? we need to either be notified by some kind of log message or the threads should terminates on their own.
3- If a thread was hanging, then why subsequent threads didn't execute
 
I also believe that adding a timeout property to this processor is important

Issue Links

• links to: GitHub Pull Request #5578