[jira] [Commented] (KAFKA-3834) Consumer should not block in poll on coordinator discovery

["Ruslan Dautkhanov (Jira)" <ji...@apache.org>]

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

Ruslan Dautkhanov commented on KAFKA-3834:
------------------------------------------

That's great this issue is fixed on the discovery side. We had a production stream and after connectivity got lost for all Kafka brokers, it went to the same hanging state.. Is there is a way to make an existing / running stream on Kafka client / consumer fail same way - if source Kafka cluster isn't available for an extended period of time? Thanks!

> Consumer should not block in poll on coordinator discovery
> ----------------------------------------------------------
>
>                 Key: KAFKA-3834
>                 URL: https://issues.apache.org/jira/browse/KAFKA-3834
>             Project: Kafka
>          Issue Type: Improvement
>          Components: consumer
>            Reporter: Jason Gustafson
>            Assignee: Jason Gustafson
>            Priority: Major
>             Fix For: 2.0.0
>
>
> Currently we block indefinitely in poll() when discovering the coordinator for the group. Instead, we can return an empty record set when the passed timeout expires. The downside is that it may obscure the underlying problem (which is usually misconfiguration), but users typically have to look at the logs to figure out the problem anyway. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)