[
https://issues.apache.org/jira/browse/KAFKA-20272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-20272.
---------------------------------
Fix Version/s: 4.3.0
Resolution: Fixed
> Rebalance classic members only on new assignment
> ------------------------------------------------
>
> Key: KAFKA-20272
> URL: https://issues.apache.org/jira/browse/KAFKA-20272
> Project: Kafka
> Issue Type: Sub-task
> Components: group-coordinator
> Reporter: Sean Quah
> Assignee: Sean Quah
> Priority: Major
> Fix For: 4.3.0
>
>
> When classic members are part of a mixed group in the group coordinator, we
> tell them to rebalance when their member epoch lags behind the group epoch.
> They should instead rebalance when their member epoch lags behind the target
> assignment epoch, since there is no point in rebalancing when no new target
> assignment is available yet.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
