[ https://issues.apache.org/jira/browse/KAFKA-15105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737186#comment-17737186 ]
Max Riedel commented on KAFKA-15105: ------------------------------------ I would like to work on this issue. I'm still trying to understand how the build infrastructure works. Can someone give me a hint, how to reproduce the behavior? > Flaky test > FetchFromFollowerIntegrationTest.testFetchFromLeaderWhilePreferredReadReplicaIsUnavailable > ----------------------------------------------------------------------------------------------------- > > Key: KAFKA-15105 > URL: https://issues.apache.org/jira/browse/KAFKA-15105 > Project: Kafka > Issue Type: Bug > Components: core > Affects Versions: 3.5.0 > Reporter: Josep Prat > Priority: Major > Labels: flaky-test > > Test > integration.kafka.server.FetchFromFollowerIntegrationTest.testFetchFromLeaderWhilePreferredReadReplicaIsUnavailable() > became flaky. An example can be found here: > [https://ci-builds.apache.org/job/Kafka/job/kafka-pr/job/PR-13865/2/testReport/junit/integration.kafka.server/FetchFromFollowerIntegrationTest/Build___JDK_11_and_Scala_2_13___testFetchFromLeaderWhilePreferredReadReplicaIsUnavailable__/] > The error might be caused because of a previous kafka cluster used for > another test wasn't cleaned up properly before this one run. > > h3. Error Message > {code:java} > org.apache.kafka.common.errors.TopicExistsException: Topic > '__consumer_offsets' already exists.{code} > h3. Stacktrace > {code:java} > org.apache.kafka.common.errors.TopicExistsException: Topic > '__consumer_offsets' already exists. {code} -- This message was sent by Atlassian Jira (v8.20.10#820010)