-
Notifications
You must be signed in to change notification settings - Fork 14.3k
KAFKA-18206: EmbeddedKafkaCluster must set features #18189
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
b61db67
to
33ea277
Compare
33ea277
to
17a262f
Compare
17a262f
to
b1982e5
Compare
Should we split this into it's own PR? |
We have merged 18448 so we should be able to proceed here :) |
I'm not sure why, but it seems like a lot of tests have become more flaky than before in this PR. One failed test in CI (https://github.com/apache/kafka/actions/runs/12810813472) caught my attention: MirrorConnectorsIntegrationTransactionsTest #testOffsetTranslationBehindReplicationFlow. The error message is:
I expected this failed test should to be mitigated after merging PR #18448, so I'll spend some time investigating this. |
This #18189 (comment) seems due to TV_2 return incorrect error, and should be handled correctly in #18604. |
@brandboat I just merged my PR and will restart the tests here. You may need to rebase, but we can try as is for now. |
Bunch of ci failed in this PR since ClearElrRecord isn't corrected handled, but will be fixed after #18708 merged. |
The build is looking better! Maybe we just need to look in to the |
Yes, I'm currently investigating the root cause of this test failure. Thanks for the heads-up! |
after ec49a60, if ELR is enabled, a cluster-level min.insync.replicas will be set to 1, and this PR aims to update all feature version to the latest.
Finally got an AC 🎉 , perhaps we can move on? |
@@ -696,7 +696,8 @@ class KRaftClusterTest { | |||
new AlterConfigOp(new ConfigEntry("max.connections.per.ip", "60"), OpType.SET)))))) | |||
validateConfigs(admin, Map(new ConfigResource(Type.BROKER, "") -> Seq( | |||
("log.roll.ms", "1234567"), | |||
("max.connections.per.ip", "60"))), exhaustive = true) | |||
("max.connections.per.ip", "60"), | |||
("min.insync.replicas", "1"))), exhaustive = true) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why did we make this change?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
after ec49a60, if ELR is enabled, a cluster-level min.insync.replicas will be set to 1, and this PR will enable ELR by default in all integration tests that use TestKitNodes.java
I'm also curious why the tests are returning 1 if there are just flaky tests. Has this always been the case? |
Hi @jolshan, pardon me, did you mean EagerConsumerCoordinatorTest.testOutdatedCoordinatorAssignment? If so, yes it it a flaky test, and we already have a JIRA ticket for it: https://issues.apache.org/jira/browse/KAFKA-15900 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your persistence here @brandboat !
related to KAFKA-18206, set features in EmbeddedKafkaCluster in both streams and connect module, note that this PR also fix potential transaction with empty records in sendPrivileged method as transaction version 2 doesn't allow this kind of scenario. Reviewers: Justine Olshan <[email protected]>
Also pushed to 4.0. Thanks! |
related to KAFKA-18206, set features in EmbeddedKafkaCluster in both streams and connect module, note that this PR also fix potential transaction with empty records in sendPrivileged method as transaction version 2 doesn't allow this kind of scenario. Reviewers: Justine Olshan <[email protected]>
related to KAFKA-18206, set features in EmbeddedKafkaCluster in both streams and connect module, note that this PR also fix potential transaction with empty records in sendPrivileged method as transaction version 2 doesn't allow this kind of scenario. Reviewers: Justine Olshan <[email protected]>
related to KAFKA-18206, set features in EmbeddedKafkaCluster in both streams and connect module, note that this PR also fix potential transaction with empty records in sendPrivileged method as transaction version 2 doesn't allow this kind of scenario.
Committer Checklist (excluded from commit message)