-
Notifications
You must be signed in to change notification settings - Fork 14.5k
KAFKA-17472: Speed Up DescribeConsumerGroupTest #17117
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
Merged
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
0829390
add GroupCoordinatorConfig in ConsumerGroupCommandTestUtils
m1a2st 17bf18d
add MAX_POLL_INTERVAL_MS_CONFIG in DescribeConsumerGroupTest
m1a2st 8b18308
add new config for broker
m1a2st 4268f6c
remove MAX_POLL_INTERVAL_MS_CONFIG in consumer
m1a2st File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
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.
Hi @m1a2st, one question, based on the document of
group.initial.rebalance.delay.ms
. (Link)I think setting
group.initial.rebalance.delay.ms
to zero might be better. Is there have any reason we use 1000 ms?I can see some tests are using 1000ms, but some others are using 0ms.
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.
Hi @chenyulin0719, You can see this discussion, we set the
group.initial.rebalance.delay.ms
from 3000 to 1000 to not only keep the initial rebalance delay but also speed up the test.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.
I see. Comparing to set
group.initial.rebalance.delay.ms
to 0 ms, adding some delay could speed up the metadata synchronization in Kraft mode. Let's a suprising finding to me.Thanks for sharing the discussion.
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.
That is good, but we want to have delay in testing. That can "reduce" the difference between test and production. Also, 1.5s is good enough in speedup.