You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Jason Gustafson (JIRA)" <ji...@apache.org> on 2018/03/02 01:24:00 UTC
[jira] [Commented] (KAFKA-6348) Kafka consumer can't restore from
coordinator failure
[ https://issues.apache.org/jira/browse/KAFKA-6348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16382966#comment-16382966 ]
Jason Gustafson commented on KAFKA-6348:
----------------------------------------
Each groupId is mapped to one of the __consumer_offsets partitions. The group coordinator is whichever broker happens to be leading that partition. So if you see an issue with the coordinator which is resolved by changing the groupId, that likely suggests some problem with whichever __consumer_offsets partitions the old groupId was mapped to. You should check that all partitions are healthy and that there are no errors in the broker logs.
> Kafka consumer can't restore from coordinator failure
> -----------------------------------------------------
>
> Key: KAFKA-6348
> URL: https://issues.apache.org/jira/browse/KAFKA-6348
> Project: Kafka
> Issue Type: Bug
> Components: consumer, core
> Affects Versions: 0.10.1.1
> Reporter: Renjie Liu
> Priority: Major
>
> Kafka consumer blocks and keep reporting coordinator is dead. I tried to restart the process and it still can't work. Then we shutdown the broker and restart consumer, but it still keep reporting coordinator is dead. This situation continues until we change our group id and it works.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)