You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "PoAn Yang (Jira)" <ji...@apache.org> on 2025/04/14 15:29:00 UTC

[jira] [Commented] (KAFKA-19142) TestKitNodes doesn't bootstrap KIP-853 correctly

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

PoAn Yang commented on KAFKA-19142:
-----------------------------------

Hi [~jsancio], may I take this? I think we also has another similar case from this situation.

https://issues.apache.org/jira/browse/KAFKA-18937

> TestKitNodes doesn't bootstrap KIP-853 correctly
> ------------------------------------------------
>
>                 Key: KAFKA-19142
>                 URL: https://issues.apache.org/jira/browse/KAFKA-19142
>             Project: Kafka
>          Issue Type: Sub-task
>          Components: kraft, unit tests
>            Reporter: José Armando García Sancio
>            Priority: Critical
>
> In some tests in KRaftClusterTest the kraft version is configured using the TestKitNodes#setFeatureLevel method. That doesn't properly bootstrap a KIP-853 cluster since it records the kraft version using FeatureLevelRecord instead of KRaftVersion control record.
> Any time the kraft.version is 1, it must be guaranteed that the voter set is also persisted in the partition.
> Take a look at `RaftClientTestContext#testDescribeKRaftVersion` for an example on how to configure a cluster with kraft version 1.



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