[
https://issues.apache.org/jira/browse/KAFKA-9275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dengziming reassigned KAFKA-9275:
---------------------------------
Assignee: dengziming
> Print assignment and IP address in the log message when consumer
> leaves/removed from the group
> ----------------------------------------------------------------------------------------------
>
> Key: KAFKA-9275
> URL: https://issues.apache.org/jira/browse/KAFKA-9275
> Project: Kafka
> Issue Type: Improvement
> Reporter: Badai Aqrandista
> Assignee: dengziming
> Priority: Minor
>
> In order to simplify identification of which member is causing rebalance, can
> we add the IP address and the list of topic-partitions assigned to the member
> that leaves/removed from the group?
> And especially in the "reason" string for rebalance:
> https://github.com/apache/kafka/blob/2.4/core/src/main/scala/kafka/coordinator/group/GroupCoordinator.scala#L964
> https://github.com/apache/kafka/blob/2.4/core/src/main/scala/kafka/coordinator/group/GroupCoordinator.scala#L972
> https://github.com/apache/kafka/blob/2.4/core/src/main/scala/kafka/coordinator/group/GroupCoordinator.scala#L1144
> https://github.com/apache/kafka/blob/2.4/core/src/main/scala/kafka/coordinator/group/GroupCoordinator.scala#L493
> This will allow a much faster investigation when a consumer group is stuck in
> rebalancing state.
> Even better if we can send this reason to all other members that are affected
> by the rebalance. Currently, it takes forever to know what caused a rebalance
> when a consumer group continuously goes into rebalancing state due to one
> member keeps exceeding max.poll.intervals.ms.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
