KAFKA-16390 add group.coordinator.rebalance.protocols=classic,consumer to broker configs when system tests need the new coordinator#16715
Conversation
…d set correct value for it
|
@frankvicky could you please attach the test result? I will verify this patch on my local later |
| @@ -782,7 +782,8 @@ def prop_file(self, node): | |||
|
|
|||
| if self.use_new_coordinator: | |||
| override_configs[config_property.NEW_GROUP_COORDINATOR_ENABLE] = 'true' | |||
There was a problem hiding this comment.
maybe we can remove this config? group.coordinator.rebalance.protocols=classic,consumer has covered that.
There was a problem hiding this comment.
I would keep it for now. It is nice to have the ability to set it explicitly in tests.
There was a problem hiding this comment.
I would keep it for now. It is nice to have the ability to set it explicitly in tests.
that is fine to me. BTW, will we remove group.coordinator.new.enable in the future?
There was a problem hiding this comment.
my point was: why we need the scenario that server uses the new coordinator but "consumer protocol" is disallowed?
There was a problem hiding this comment.
Yes. We will remove group.coordinator.new.enable in the near future. No, we don't have this case at the moment. I think that we have such cases, especially in integration environments where we want to test the new coordinator without the "consumer protocol".
|
Hi @chia7712 |
| if self.use_new_coordinator: | ||
| override_configs[config_property.NEW_GROUP_COORDINATOR_ENABLE] = 'true' | ||
|
|
||
| override_configs[config_property.GROUP_COORDINATOR_REBALANCE_PROTOCOLS_CONFIG] = 'classic,consumer' |
There was a problem hiding this comment.
just to double check, here we're adding both as a default, but still respecting any specific value that a test may have right? (I guess the following logic on ln 788 ensures that?)
There was a problem hiding this comment.
Yes, you're right, the logic respects specific test values while adding necessary defaults.
kirktrue
left a comment
There was a problem hiding this comment.
Thanks for the PR, @frankvicky!
This seems like a partial revert of the changes from #16482. If @dajac is happy with it, then I am as well 😄
Thanks!
yep, this PR reverts a part of #16482. For another, it seems adding the new coordinator configs to |
I'm sold. 😺 |
|
@frankvicky any updates? I feel this PR need to be backport to 3.9 to make e2e stable. @cmccabe FYI |
|
Hi @chia7712 |
|
Can we update the title and/or description. There are many more tests that are failing (and hopefully should be fixed) by this change. More specifically any test with |
chia7712
left a comment
There was a problem hiding this comment.
LGTM. run consume_bench_test.py on my local. it works.
group.coordinator.rebalance.protocols=classic,consumer to broker configs when E2E needs the new coordinator
group.coordinator.rebalance.protocols=classic,consumer to broker configs when E2E needs the new coordinatorgroup.coordinator.rebalance.protocols=classic,consumer to broker configs when system tests need the new coordinator
|
I will also cherrypick to 3.9 |
…mer` to broker configs when system tests need the new coordinator (#16715) Fix an issue that cause system test failing when using AsyncKafkaConsumer. A configuration option, group.coordinator.rebalance.protocols, was introduced to specify the rebalance protocols used by the group coordinator. By default, the rebalance protocol is set to classic. When the new group coordinator is enabled, the rebalance protocols are set to classic,consumer. Reviewers: Chia-Ping Tsai <chia7712@gmail.com>, David Jacot <djacot@confluent.io>, Lianet Magrans <lianetmr@gmail.com>, Kirk True <kirk@kirktrue.pro>, Justine Olshan <jolshan@confluent.io>
hi @lianetm, do you mean "consume_bench_test.py" still has some failed tests on your local? I run the test only once 😅 so maybe there are others flaky ... |
Jira Link
Fix an issue that cause system test failing when using
AsyncKafkaConsumer.A configuration option,
group.coordinator.rebalance.protocols, was introduced to specify the rebalance protocols used by the group coordinator. By default, the rebalance protocol is set toclassic. When the new group coordinator is enabled, the rebalance protocols are set toclassic,consumer.Committer Checklist (excluded from commit message)