Skip to content
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

Merged
merged 1 commit into from
Jul 22, 2022

Conversation

mmaslankaprv
Copy link
Member

@mmaslankaprv mmaslankaprv commented Jul 18, 2022

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

@mmaslankaprv mmaslankaprv marked this pull request as ready for review July 18, 2022 07:49
@mmaslankaprv mmaslankaprv requested review from ztlpn and dlex July 18, 2022 08:38
@NyaliaLui NyaliaLui added the ci-repeat-5 repeat tests 5x concurrently to check for flakey tests; self-cancelling label Jul 19, 2022
@vbotbuildovich vbotbuildovich removed the ci-repeat-5 repeat tests 5x concurrently to check for flakey tests; self-cancelling label Jul 19, 2022
@NyaliaLui
Copy link
Contributor

NyaliaLui commented Jul 19, 2022

Added ci-repeat-5 since this PR fixes ci-failures

@dotnwat
Copy link
Member

dotnwat commented Jul 20, 2022

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>
@mmaslankaprv mmaslankaprv added the ci-repeat-5 repeat tests 5x concurrently to check for flakey tests; self-cancelling label Jul 22, 2022
@vbotbuildovich vbotbuildovich removed the ci-repeat-5 repeat tests 5x concurrently to check for flakey tests; self-cancelling label Jul 22, 2022
@dotnwat dotnwat merged commit 975b5e0 into redpanda-data:dev Jul 22, 2022
= 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);
Copy link
Contributor

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

kafka/groups: error in join_empty_group_static_member test test_kafka_server_fixture_rpunit failure
6 participants