You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "David Arthur (Jira)" <ji...@apache.org> on 2024/08/31 20:11:00 UTC

[jira] [Updated] (KAFKA-17457) Raise minimum MetadataVersion for ZK migration to 3.6

     [ https://issues.apache.org/jira/browse/KAFKA-17457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Arthur updated KAFKA-17457:
---------------------------------
    Fix Version/s: 3.9.0
                   3.8.1
                       (was: 3.8.0)

> Raise minimum MetadataVersion for ZK migration to 3.6
> -----------------------------------------------------
>
>                 Key: KAFKA-17457
>                 URL: https://issues.apache.org/jira/browse/KAFKA-17457
>             Project: Kafka
>          Issue Type: Task
>          Components: controller, migration
>            Reporter: David Arthur
>            Priority: Blocker
>             Fix For: 3.6.3, 3.9.0, 3.7.2, 3.8.1
>
>
> In the 3.6.0 release notes, we announced that ZK migrations were production ready.
> > The 3.6.0 release marked the first production ready release for the migration of Kafka clusters from a ZooKeeper metadata system to a KRaft metadata system. Users wanting to perform this migration are advised to first upgrade to 3.6.2 or 3.7.1 to receive important bug fixes.
> Part of the reasoning behind this announcement was that the migration was feature complete at this point (migration transactions and migration of delegation tokens were included in 3.6). 
> If users are on a software version of 3.6 or higher, we should not let them perform the migration at an older MetadataVersion. Otherwise, the migration will be done without the use of metadata transactions, which is not safe.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)