fix(inkless): retry describeTopics in InklessManagedReplicasClusterTest for metadata propagation - #625
Merged
Conversation
…st for metadata propagation In multi-broker clusters, metadata propagation from the controller to follower brokers is async. describeTopics may hit a broker that hasn't received the update yet, causing UnknownTopicOrPartitionException. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
jeqo
force-pushed
the
jeqo/fix-flaky-managed-replicas-test
branch
from
June 1, 2026 15:40
d74994f to
eeef9bd
Compare
Contributor
There was a problem hiding this comment.
Pull request overview
This PR reduces test flakiness in InklessManagedReplicasClusterTest by retrying Admin#describeTopics to tolerate asynchronous metadata propagation in multi-broker clusters (where a follower broker may temporarily return UnknownTopicOrPartitionException right after topic creation).
Changes:
- Added a small retry helper to wait until
describeTopicssucceeds after topic creation. - Updated two tests to use the new helper instead of a single
describeTopicscall.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
jeqo
marked this pull request as ready for review
June 1, 2026 16:06
viktorsomogyi
approved these changes
Jun 2, 2026
giuseppelillo
pushed a commit
that referenced
this pull request
Jun 4, 2026
…st for metadata propagation (#625) In multi-broker clusters, metadata propagation from the controller to follower brokers is async. describeTopics may hit a broker that hasn't received the update yet, causing UnknownTopicOrPartitionException. Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
gqmelo
pushed a commit
that referenced
this pull request
Jun 4, 2026
…st for metadata propagation (#625) In multi-broker clusters, metadata propagation from the controller to follower brokers is async. describeTopics may hit a broker that hasn't received the update yet, causing UnknownTopicOrPartitionException. Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In multi-broker clusters, metadata propagation from the controller to follower brokers is async. describeTopics may hit a broker that hasn't received the update yet, causing UnknownTopicOrPartitionException.