sanghyeok An created KAFKA-20909:
------------------------------------
Summary: Consider bumping the consumer group epoch when a member's
rack ID changes
Key: KAFKA-20909
URL: https://issues.apache.org/jira/browse/KAFKA-20909
Project: Kafka
Issue Type: Improvement
Reporter: sanghyeok An
Assignee: sanghyeok An
In KIP-848 consumer groups, a member's changed rack ID is persisted, but it
does not currently bump the group epoch. Therefore, the target assignment is
not recomputed until another event triggers a rebalance.
This is relevant to static members as well. A member rejoining with the same
group.instance.id retains its logical identity, but its previous assignment may
no longer be appropriate if its rack has changed.
Rack ID is also included in the member metadata passed to the assignor. A
custom or future rack-aware assignor may produce a different assignment based
on it.
Consider treating an effective rack ID change as an assignment-relevant
metadata change and bumping the group epoch. An omitted or unchanged rack ID
should not trigger a bump.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
