-
Notifications
You must be signed in to change notification settings - Fork 577
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
k/tests: wait for coordinator of correct group id #5496
Conversation
Added ci-repeat-5 since this PR fixes ci-failures |
Good call @NyaliaLui. I think the failure may have triggered again: https://buildkite.com/redpanda/redpanda/builds/12747#018217f3-7504-4609-854e-e27bcd0289d1/6-5439 |
When broker returns `not_coordinator` error client should retry. Signed-off-by: Michal Maslanka <michal@redpanda.com>
= client.dispatch(std::move(req), kafka::api_version(5)).get0(); | ||
BOOST_REQUIRE( | ||
resp.data.error_code == kafka::error_code::none | ||
|| resp.data.error_code == kafka::error_code::not_coordinator); |
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.
The case when error_code == none && member_id == unknown_member_id
was a test failure before, and now it will cause retries. Should it be an immediate failure instead?
After changing default number of partitions for
__consumer_offsets
topic we need to wait for particular group coordinator before requesting
consumer to join the group.
Fixes: #5495
Fixes: #5466