[
https://issues.apache.org/jira/browse/KAFKA-3834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15710240#comment-15710240
]
Sönke Liebau commented on KAFKA-3834:
-------------------------------------
Does anybody know whether this is being discussed somewhere else that I perhaps
couldn't find? In other words, are there any news on this? :)
I'm currently running into this behavior when using commitSync - in this case,
when the broker dies, the writing thread will simply block indefinitely and not
do anything, until the broker comes back, which as stated above is fine if it
is a transient failure, but I think a timeout makes sense here. Same issue,
when starting a consumer with a mistyped ip address, that will never error out
- granted, you'll notice that you are not sending any messages at some point,
but I think this could be improved.
> 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)
