Re: [PR] [WIP] KAFKA-16383: fix flaky IdentityReplicationIntegrationTest .testReplicateFromLatest [kafka]

2024-04-02 Thread via GitHub


johnnychhsu commented on PR #15556:
URL: https://github.com/apache/kafka/pull/15556#issuecomment-2032431618

   @vamossagar12 thanks for sharing!
   and from the build the IdentityReplicationIntegrationTest 
.testReplicateFromLatest passed with the fix, I think this could be the root 
cause, @chia7712 @vamossagar12 wdyt?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: jira-unsubscr...@kafka.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] [WIP] KAFKA-16383: fix flaky IdentityReplicationIntegrationTest .testReplicateFromLatest [kafka]

2024-04-02 Thread via GitHub


vamossagar12 commented on PR #15556:
URL: https://github.com/apache/kafka/pull/15556#issuecomment-2031549949

   @johnnychhsu ,for completeness sake, the issue with private constructor 
related noise in the logs is being fixed in this PR: 
https://github.com/apache/kafka/pull/15642


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: jira-unsubscr...@kafka.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] [WIP] KAFKA-16383: fix flaky IdentityReplicationIntegrationTest .testReplicateFromLatest [kafka]

2024-04-01 Thread via GitHub


johnnychhsu commented on code in PR #15556:
URL: https://github.com/apache/kafka/pull/15556#discussion_r1546456617


##
connect/mirror/src/test/java/org/apache/kafka/connect/mirror/integration/MirrorConnectorsIntegrationBaseTest.java:
##
@@ -900,7 +900,7 @@ public void testReplicateFromLatest() throws Exception {
 
 String backupTopic = remoteTopicName(topic, PRIMARY_CLUSTER_ALIAS);
 // wait for at least the expected number of records to be replicated 
to the backup cluster

Review Comment:
   from this comment, I think what it wants to do is, verify that there are 
enough records in primary first, then consume all from backup to check that 
there are enough records in backup



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: jira-unsubscr...@kafka.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org