[
https://issues.apache.org/jira/browse/KAFKA-9509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17140203#comment-17140203
]
Matthias J. Sax commented on KAFKA-9509:
----------------------------------------
[https://builds.apache.org/job/kafka-pr-jdk11-scala2.13/7061/testReport/junit/org.apache.kafka.connect.mirror/MirrorConnectorsIntegrationTest/testReplication/]
{quote}ava.lang.AssertionError: Connector MirrorCheckpointConnector tasks did
not start in time on cluster:
org.apache.kafka.connect.util.clusters.EmbeddedConnectCluster@5376246b at
org.apache.kafka.connect.util.clusters.EmbeddedConnectClusterAssertions.assertConnectorAndAtLeastNumTasksAreRunning(EmbeddedConnectClusterAssertions.java:120)
at
org.apache.kafka.connect.mirror.MirrorConnectorsIntegrationTest.waitUntilMirrorMakerIsRunning(MirrorConnectorsIntegrationTest.java:191)
at
org.apache.kafka.connect.mirror.MirrorConnectorsIntegrationTest.setup(MirrorConnectorsIntegrationTest.java:184){quote}
> 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: Luke Chen
> 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)
