[
https://issues.apache.org/jira/browse/KAFKA-17321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17875004#comment-17875004
]
Chia-Ping Tsai commented on KAFKA-17321:
----------------------------------------
[~uncleyi] 1.1.1 is EOL. Could you please test the latest kafka?
> Kafka 1.1.1 consumer cannot get any topic-partition
> ---------------------------------------------------
>
> Key: KAFKA-17321
> URL: https://issues.apache.org/jira/browse/KAFKA-17321
> Project: Kafka
> Issue Type: Bug
> Components: consumer
> Affects Versions: 1.1.1
> Environment: Kafka 1.1.1 with Scala 2.11
> Reporter: YI ZHAOPU
> Priority: Critical
> Labels: consumer, group-coordinator
>
> We are using Kafka 1.1.1, in one day that our consumers (using subscribe
> mode) restarted themselves, but during the rebalance, consumers could assign
> topic-partitions until generation 229, after generation 229, the logs shown
> that the consumer could not get any topic-partition, event if we tried to
> restart consumer in order to trigger rebalance again, but it had no effect,
> logs shown that there were still no partition(Setting newly assigned
> partitions []).
> But both Kafka coordinator and consumer did not show any exception logs and
> error, it just rebalance the group as normal.
> The solution was we restarted the Group Coordinator, which trigger the broker
> high availability switch, let the leader of the __consumer_offsets switch to
> another broker and switch back, once the coordinator switched, that problem
> was solve immediately.
> Is there anyone meet similar problem before? Can anybody explain this thing?
> Very Thanks.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
