You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Lianet Magrans (Jira)" <ji...@apache.org> on 2026/03/12 16:17:00 UTC
[jira] [Resolved] (KAFKA-20296) Flaky testAsyncConsumerPerPartitionLeadMetricsCleanUpWithSubscribe
[ https://issues.apache.org/jira/browse/KAFKA-20296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lianet Magrans resolved KAFKA-20296.
------------------------------------
Resolution: Fixed
> Flaky testAsyncConsumerPerPartitionLeadMetricsCleanUpWithSubscribe
> ------------------------------------------------------------------
>
> Key: KAFKA-20296
> URL: https://issues.apache.org/jira/browse/KAFKA-20296
> Project: Kafka
> Issue Type: Test
> Components: clients, consumer
> Reporter: Lianet Magrans
> Assignee: Lianet Magrans
> Priority: Minor
> Labels: flaky-test
>
> Has been flaky on trunk, failing when it continues to find a metric that is supposed to the removed when preparing fetch requests
> [https://develocity.apache.org/scans/tests?search.rootProjectNames=kafka&search.startTimeMax=1773254924044&search.startTimeMin=1767243600000&search.tags=trunk&search.timeZoneId=America%2FToronto&tests.container=org.apache.kafka.clients.consumer.PlaintextConsumerTest&tests.sortField=FLAKY&tests.test=testAsyncConsumerPerPartitionLeadMetricsCleanUpWithSubscribe()%5B1%5D]
> The metric is only removed when sending new fetch requests (on prepareFetchRequests), so wonder if the case if that the test is just waiting for a rebalance (callbacks triggered) before checking the metric is removed. But that awaitRebalance does not guarantee that we sent a new fetch request
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)