You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "Chia-Ping Tsai (Jira)" <ji...@apache.org> on 2024/09/10 04:17:00 UTC

[jira] [Resolved] (KAFKA-17497) Add e2e for zk migration with old controller

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

Chia-Ping Tsai resolved KAFKA-17497.
------------------------------------
    Resolution: Fixed

trunk: https://github.com/apache/kafka/commit/2dc3ee05579ddcf70a072fecd8db68ab9d1bbdb2

3.9: https://github.com/apache/kafka/commit/4b6437e6a523f72ef9d1572a77933057dbafafdd

> Add e2e for zk migration with old controller
> --------------------------------------------
>
>                 Key: KAFKA-17497
>                 URL: https://issues.apache.org/jira/browse/KAFKA-17497
>             Project: Kafka
>          Issue Type: Test
>            Reporter: Chia-Ping Tsai
>            Assignee: TengYao Chi
>            Priority: Blocker
>             Fix For: 3.9.0
>
>
> This is follow-up of KAFKA-17011 that zk migration will encounter min=0 issue when the cluster consists of "new" broker and "old" controller.
> The e2e `zookeeper_migration_test` [0] is a good test for online migration, but it does not test hybrid version. Hence, we can leverage it to increase test coverage.
>  [0] https://github.com/apache/kafka/blob/trunk/tests/kafkatest/tests/core/zookeeper_migration_test.py#L91



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