[
https://issues.apache.org/jira/browse/KAFKA-3879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15345485#comment-15345485
]
Jason Gustafson commented on KAFKA-3879:
----------------------------------------
[~singhashish] This is a duplicate of KAFKA-3822, right? Yeah, we knew about
it. I think we should either solve it by adding a {{max.block.ms}}
configuration option or an overloaded close() with a timeout.
> KafkaConsumer with auto commit enabled gets stuck when killed after broker is
> dead
> ----------------------------------------------------------------------------------
>
> Key: KAFKA-3879
> URL: https://issues.apache.org/jira/browse/KAFKA-3879
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.10.0.0
> Reporter: Ashish K Singh
> Assignee: Ashish K Singh
> Fix For: 0.10.0.1
>
>
> KafkaConsumer with auto commit enabled gets stuck when killed after broker is
> dead.
> * KafkaConsumer on close tries to close coordinator.
> * Coordinator, if auto commit is enabled, tries to commit offsets
> synchronously before closing.
> * While trying to synchronously commit offsets, coordinator checks if
> coordinator is alive by sending {{GroupCoordinatorRequest}}. As brokers are
> dead, this returns {{NoAvailableBrokersException}}, which is a retriable
> exception.
> * Coordinator ready check enters into an infinite loop as it keeps retrying
> to discover group coordinator.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
