nifi-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (NIFI-2739) ConsumeKafka and ConsumeKafka_0_10 can block indefinitely if unable to communicate with Kafka broker
Date Wed, 07 Sep 2016 04:57:20 GMT

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

ASF GitHub Bot commented on NIFI-2739:
--------------------------------------

Github user joewitt commented on the issue:

    https://github.com/apache/nifi/pull/989
  
    +1 as-is but do consider reducing from 30 secs to 5 secs.  There is no known reason why
it should ever have to wait near 5 seconds even as currently implemented particularly in the
case of an unscheduling of the processor.  Each poll event immediately writes to the content
repository.
    
    Glad to hear wakeup does what is needed here at least for lifecycle calls such as OnUnscheduled.


> ConsumeKafka and ConsumeKafka_0_10 can block indefinitely if unable to communicate with
Kafka broker
> ----------------------------------------------------------------------------------------------------
>
>                 Key: NIFI-2739
>                 URL: https://issues.apache.org/jira/browse/NIFI-2739
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Extensions
>            Reporter: Mark Payne
>            Assignee: Mark Payne
>             Fix For: 1.1.0
>
>
> If I use ConsumeKafka and point to a broker that is in a bad state, I see ConsumeKafka
block indefinitely.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message