You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Sophie Blee-Goldman (Jira)" <ji...@apache.org> on 2020/06/17 17:58:00 UTC

[jira] [Reopened] (KAFKA-9509) Fix flaky test MirrorConnectorsIntegrationTest.testReplication

     [ https://issues.apache.org/jira/browse/KAFKA-9509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sophie Blee-Goldman reopened KAFKA-9509:
----------------------------------------

Saw this fail again on a PR build:
h3. Stacktrace

java.lang.RuntimeException: Could not find enough records. found 0, expected 100 at org.apache.kafka.connect.util.clusters.EmbeddedKafkaCluster.consume(EmbeddedKafkaCluster.java:435) at org.apache.kafka.connect.mirror.MirrorConnectorsIntegrationTest.testReplication(MirrorConnectorsIntegrationTest.java:222)

 

[https://builds.apache.org/job/kafka-pr-jdk14-scala2.13/1130/testReport/junit/org.apache.kafka.connect.mirror/MirrorConnectorsIntegrationTest/testReplication/]

> Fix flaky test MirrorConnectorsIntegrationTest.testReplication
> --------------------------------------------------------------
>
>                 Key: KAFKA-9509
>                 URL: https://issues.apache.org/jira/browse/KAFKA-9509
>             Project: Kafka
>          Issue Type: Test
>          Components: mirrormaker
>    Affects Versions: 2.4.0
>            Reporter: Sanjana Kaundinya
>            Assignee: Sanjana Kaundinya
>            Priority: Major
>             Fix For: 2.5.0
>
>
> The test org.apache.kafka.connect.mirror.MirrorConnectorsIntegrationTest.testReplication is a flaky test for MirrorMaker 2.0. Its flakiness lies in the timing of when the connectors and tasks are started up. The fix for this would make it such that when the connectors are started up, to wait until the REST endpoint returns a positive number of tasks to be confident that we can start testing.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)