kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Abhishek Agarwal (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-3834) Consumer should not block in poll on coordinator discovery
Date Sun, 16 Jul 2017 09:48:00 GMT

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

Abhishek Agarwal commented on KAFKA-3834:
-----------------------------------------

[~hachikuji] If the ips are misconfigured or the broker is not available, then group_coordinator_request
will never be sent to that node. Isn't it? Won't the lookupCoordinator() call itself fail,
before the client blocks itself in awaitMetadataUpdate()

> 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.4.14#64029)

Mime
View raw message