[ https://issues.apache.org/jira/browse/NIFI-9093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Elbraish updated NIFI-9093: ----------------------------------- Component/s: (was: NiFi Stateless) Core Framework > GetSplunk Processor hangs > ------------------------- > > Key: NIFI-9093 > URL: https://issues.apache.org/jira/browse/NIFI-9093 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework > Affects Versions: 1.12.1 > Environment: NiFi 3 nodes cluster - 40 CPU core +28 GB of RAM per node > Reporter: Michael Elbraish > Priority: Major > > 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 -- This message was sent by Atlassian Jira (v8.3.4#803005)