[jira] [Commented] (KAFKA-13589) fix flaky `PlaintextAdminIntegrationTest.testReplicaCanFetchFromLogStartOffsetAfterDeleteRecords` test

["Luke Chen (Jira)" <ji...@apache.org>]

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

Luke Chen commented on KAFKA-13589:
-----------------------------------

The flaky test is because we want to verify the LEO is exactly the number we expected. But because we default deliver semantics is "at least once", which means, the LEO might be greater or equal to the expected number. This issue can be fixed after KAFKA-13598 is merged. That is, default producer will be idempotence producer by default. 

> fix flaky `PlaintextAdminIntegrationTest.testReplicaCanFetchFromLogStartOffsetAfterDeleteRecords` test
> ------------------------------------------------------------------------------------------------------
>
>                 Key: KAFKA-13589
>                 URL: https://issues.apache.org/jira/browse/KAFKA-13589
>             Project: Kafka
>          Issue Type: Test
>            Reporter: Luke Chen
>            Assignee: Luke Chen
>            Priority: Major
>
> org.opentest4j.AssertionFailedError: Expected follower to catch up to log end offset 200 at org.junit.jupiter.api.AssertionUtils.fail(AssertionUtils.java:39) at org.junit.jupiter.api.Assertions.fail(Assertions.java:117) at kafka.api.PlaintextAdminIntegrationTest.waitForFollowerLog$1(PlaintextAdminIntegrationTest.scala:730) at kafka.api.PlaintextAdminIntegrationTest.testReplicaCanFetchFromLogStartOffsetAfterDeleteRecords(PlaintextAdminIntegrationTest.scala:760)



--
This message was sent by Atlassian Jira
(v8.20.1#820001)