[
https://issues.apache.org/jira/browse/KAFKA-16294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dongnuo Lyu updated KAFKA-16294:
--------------------------------
Description:
The online upgrade is triggered when a consumer group heartbeat request is
received in a classic group. The downgrade is triggered when any old protocol
request is received in a consumer group. We only accept upgrade/downgrade if
the corresponding group migration config policy is enabled.
This is the first part of the implementation of online group protocol
migration, adding the kafka config group protocol migration. The config has
four valid values – both(both upgrade and downgrade are allowed), upgrade(only
upgrade is allowed), downgrade(only downgrade is allowed) and none(neither is
allowed.).
At present the default value is NONE. When we start enabling the migration, we
expect to set BOTH to default so that it's easier to roll back to the old
protocol as a quick fix for anything wrong in the new protocol; when using
consumer groups becomes default and the migration is near finished, we will set
the default policy to upgrade to prevent unwanted downgrade causing too
frequent migration.
was:
The offline upgrade is triggered when a consumer group heartbeat request is
received in a classic group. The downgrade is triggered when any old protocol
request is received in a consumer group. We only accept upgrade/downgrade if 1)
the group migration config is enabled 2) the group is empty.
This is the first part of the implementation of offline group protocol
migration, adding the kafka config group protocol migration. The config has
four valid values – both(both upgrade and downgrade are allowed), upgrade(only
upgrade is allowed), downgrade(only downgrade is allowed) and none(neither is
allowed.).
> Add group protocol migration enabling config
> --------------------------------------------
>
> Key: KAFKA-16294
> URL: https://issues.apache.org/jira/browse/KAFKA-16294
> Project: Kafka
> Issue Type: Sub-task
> Reporter: Dongnuo Lyu
> Assignee: Dongnuo Lyu
> Priority: Major
>
> The online upgrade is triggered when a consumer group heartbeat request is
> received in a classic group. The downgrade is triggered when any old protocol
> request is received in a consumer group. We only accept upgrade/downgrade if
> the corresponding group migration config policy is enabled.
> This is the first part of the implementation of online group protocol
> migration, adding the kafka config group protocol migration. The config has
> four valid values – both(both upgrade and downgrade are allowed),
> upgrade(only upgrade is allowed), downgrade(only downgrade is allowed) and
> none(neither is allowed.).
> At present the default value is NONE. When we start enabling the migration,
> we expect to set BOTH to default so that it's easier to roll back to the old
> protocol as a quick fix for anything wrong in the new protocol; when using
> consumer groups becomes default and the migration is near finished, we will
> set the default policy to upgrade to prevent unwanted downgrade causing too
> frequent migration.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
