You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Dhiyaneshwaran Radhakrishnan (Jira)" <ji...@apache.org> on 2025/05/02 12:39:00 UTC

[jira] [Commented] (KAFKA-14056) Test reading of old messages formats in ZK-to-KRaft upgrade test

    [ https://issues.apache.org/jira/browse/KAFKA-14056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17948896#comment-17948896 ] 

Dhiyaneshwaran Radhakrishnan commented on KAFKA-14056:
------------------------------------------------------

Hi all,

I’ve completed testing the scenario for this ticket as described.

{*}Summary of what I validated:{*}{*}{*}
 * Started Kafka in *ZooKeeper mode* 
 * Created a topic and {*}produced messages using older message format{*}{*}{*}
 * Migrated to *KRaft mode*
 * Restarted Kafka in KRaft mode and successfully *read the pre-migration messages* from the same topic

Tested using {*}Kafka 3.9 built from source{*}, and this confirms that {*}reading older format messages post migration works as expected{*}.

> Test reading of old messages formats in ZK-to-KRaft upgrade test
> ----------------------------------------------------------------
>
>                 Key: KAFKA-14056
>                 URL: https://issues.apache.org/jira/browse/KAFKA-14056
>             Project: Kafka
>          Issue Type: Task
>          Components: kraft
>    Affects Versions: 3.9.0
>            Reporter: Ron Dagostino
>            Assignee: Dhiyaneshwaran Radhakrishnan
>            Priority: Blocker
>             Fix For: 3.9.2
>
>
> Whenever we support ZK-to-KRaft upgrade we must confirm that we can still read messages with an older message format.  We can no longer write such messages as of IBP 3.0 (which is the minimum supported with KRaft), but we must still support reading such messages with KRaft.  Therefore, the only way to test this would be to write the messages with a non-KRaft cluster, upgrade to KRaft, and then confirm we can read those messages.



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