kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ewen Cheslack-Postava (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-3834) Consumer should not block in poll on coordinator discovery
Date Mon, 20 Jun 2016 06:07:05 GMT

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

Ewen Cheslack-Postava commented on KAFKA-3834:
----------------------------------------------

Is returning an empty record set even what we want to do? Why not just throw an exception
that indicates the underlying error? (Which has the benefit of making applications aware of
the real issue and hopefully alleviating you of having to answer questions about why they
are getting errors)?

> 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
>
> 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
(v6.3.4#6332)

Mime
View raw message