[jira] [Commented] (KAFKA-18771) Flaky test KRaftClusterTest .testDescribeQuorumRequestToControllers

["PoAn Yang (Jira)" <ji...@apache.org>]

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

PoAn Yang commented on KAFKA-18771:
-----------------------------------

Hi [~showuon], the test case was introduced by your PR https://github.com/apache/kafka/commit/612e1299e46ee72bcf763257e0d99dd9a2c48bf6. I can fix it by replacing shutdown raft client with shutdown the controller. Do you know why we want to shutdown raft client directly? If it's not required, I can file a PR to fix the case. Thanks.


{noformat}
diff --git a/core/src/test/scala/integration/kafka/server/KRaftClusterTest.scala b/core/src/test/scala/integration/kafka/server/KRaftClusterTest.scala
index f380794629..87d4c6be76 100644
--- a/core/src/test/scala/integration/kafka/server/KRaftClusterTest.scala
+++ b/core/src/test/scala/integration/kafka/server/KRaftClusterTest.scala
@@ -950,7 +950,7 @@ class KRaftClusterTest {
           s"Leader ID ${quorumInfo.leaderId} was not a controller ID.")

         // Try to bring down the raft client in the active controller node to force the leader election.
-        cluster.controllers().get(quorumInfo.leaderId).sharedServer.raftManager.client.shutdown(1000)
+        cluster.controllers().get(quorumInfo.leaderId).shutdown()
         // Send another describe metadata quorum request, it'll get NOT_LEADER_OR_FOLLOWER error first and then re-retrieve the metadata update
         // and send to the correct active controller.
         val quorumInfo2 = admin.describeMetadataQuorum(new DescribeMetadataQuorumOptions)
{noformat}


> Flaky test KRaftClusterTest .testDescribeQuorumRequestToControllers
> -------------------------------------------------------------------
>
>                 Key: KAFKA-18771
>                 URL: https://issues.apache.org/jira/browse/KAFKA-18771
>             Project: Kafka
>          Issue Type: Test
>          Components: core, kraft, unit tests
>            Reporter: Matthias J. Sax
>            Priority: Critical
>              Labels: flaky-test
>
> Seeing this test failing very frequently on PR builds as flaky (so a re-run usually passes). But it very high noise ratio and we should look into it.



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