[
https://issues.apache.org/jira/browse/KAFKA-18536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18117864#comment-18117864
]
Akhilesh Chaganti commented on KAFKA-18536:
-------------------------------------------
I looked at this test failure. I think it's because the replica fetchers start
before the quotas are applied on start up. We can do a fix for the ordering,
but in practice it shouldn't have drastic effort on the fetch bandwidth. So, I
created a patch to fix the test such that the quotas are known to the broker
before replicas are assigned for fetching. -
https://github.com/apache/kafka/pull/23548
> Flaky ReplicationQuotasTest.shouldBootstrapTwoBrokersWithFollowerThrottle
> -------------------------------------------------------------------------
>
> Key: KAFKA-18536
> URL: https://issues.apache.org/jira/browse/KAFKA-18536
> Project: Kafka
> Issue Type: Bug
> Reporter: PoAn Yang
> Assignee: Akhilesh Chaganti
> Priority: Major
>
> This case failed 19 times in last month and most of failure is like following:
>
> {noformat}
> org.opentest4j.AssertionFailedError: Expected 8927 > 9000.0 ==> expected:
> <true> but was: <false>
> at
> org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
> at
> org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)
> at org.junit.jupiter.api.AssertTrue.failNotTrue(AssertTrue.java:63)
> at org.junit.jupiter.api.AssertTrue.assertTrue(AssertTrue.java:36)
> at org.junit.jupiter.api.Assertions.assertTrue(Assertions.java:214)
> at
> kafka.server.ReplicationQuotasTest.shouldMatchQuotaReplicatingThroughAnAsymmetricTopology(ReplicationQuotasTest.scala:183)
> at
> kafka.server.ReplicationQuotasTest.shouldBootstrapTwoBrokersWithFollowerThrottle(ReplicationQuotasTest.scala:79){noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
