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

Posted to jira@kafka.apache.org by "Lucas Brutschy (Jira)" <ji...@apache.org> on 2025/06/20 09:07:00 UTC

[jira] [Updated] (KAFKA-19421) Deflake streams_broker_down_resilience_test

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

Lucas Brutschy updated KAFKA-19421:
-----------------------------------
    Component/s: streams

> Deflake streams_broker_down_resilience_test
> -------------------------------------------
>
>                 Key: KAFKA-19421
>                 URL: https://issues.apache.org/jira/browse/KAFKA-19421
>             Project: Kafka
>          Issue Type: Bug
>          Components: streams
>            Reporter: Lucas Brutschy
>            Assignee: Lucas Brutschy
>            Priority: Major
>
> `streams_broker_down_resilience_test` produce messages with `null` key to a topic with three partitions and expect each partition to be non-empty afterward. But I don't think this is a correct assumption, as a producer may try to be sticky and only produce to two partitions.
> This cause occasional flakiness in the test.
> The fix is to produce records with keys.



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