[jira] [Commented] (NIFI-9093) Add timeouts to avoid GetSplunk processor hanging

["ASF subversion and git services (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFI-9093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17458624#comment-17458624 ] 

ASF subversion and git services commented on NIFI-9093:
-------------------------------------------------------

Commit c7c5b6765ab0613904e1efaa5a26eab982f9cb5f in nifi's branch refs/heads/support/nifi-1.15 from ahmed shaaban
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=c7c5b67 ]

NIFI-9093 GetSplunk Processor hangs
NIFI-9093 changed the required flag to false on ConnectTimeout and ReadTimeout properties


> Add timeouts to avoid GetSplunk processor hanging
> -------------------------------------------------
>
>                 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
>            Assignee: Joe Witt
>            Priority: Major
>              Labels: easy-fix, newbie
>             Fix For: 1.16.0, 1.15.1
>
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> 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.20.1#820001)