Lucas Brutschy created KAFKA-20172:
--------------------------------------
Summary: Support online migration between classic and streams
rebalance protocols
Key: KAFKA-20172
URL: https://issues.apache.org/jira/browse/KAFKA-20172
Project: Kafka
Issue Type: Task
Components: streams, group-coordinator
Reporter: Lucas Brutschy
The streams rebalance protocol \(KIP\-1071\) currently only supports offline
migration between the classic and streams protocols. Users must shut down all
application instances, wait for the session timeout to expire, update the
configuration, and then restart. This requires a maintenance window and causes
downtime for the streams application.
As specified in KIP\-1071, online migration should allow converting classic
consumer groups to streams groups during rolling client upgrades. When the
first streams client using the new protocol joins the group, the group should
be converted from a classic group to a streams group. Classic clients should
receive REBALANCE\_IN\_PROGRESS errors triggering JoinGroup/SyncGroup calls
while new protocol clients use StreamsGroupHeartbeat. The broker should
internally translate between protocols during the migration period. The group
should revert to classic when the last new\-protocol member leaves. This
enables zero\-downtime migration between protocols.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
