[
https://issues.apache.org/jira/browse/KAFKA-21566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-21566.
---------------------------------
Fix Version/s: 4.4.1
4.3.3
Resolution: Fixed
> Break server assignor vote ties by assignor name
> ------------------------------------------------
>
> Key: KAFKA-21566
> URL: https://issues.apache.org/jira/browse/KAFKA-21566
> Project: Kafka
> Issue Type: Bug
> Components: group-coordinator
> Affects Versions: 4.4.0, 4.3.2
> Reporter: Dongnuo Lyu
> Assignee: Dongnuo Lyu
> Priority: Major
> Fix For: 4.4.1, 4.3.3
>
>
> A consumer group picks its server assignor by member vote. With a tied vote,
> the winner is whichever entry the vote map lists first. In
> {{{}hasPreferredServerAssignorChanged{}}}, the heartbeat path computes the
> winner twice to detect a change of preferred assignor, once from the stored
> TimelineHashMap and once from a HashMap copy. The two maps can list tied
> entries in different orders, so plain heartbeats looks like an assignor
> change.
> There is a related bug in 4.0 where the assignor name in
> ConsumerGroupDescribe can differ from the assignor actually in used, since
> preferredServerAssignor() and computePreferredServerAssignor() break ties in
> whatever order their map lists the entries.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)