-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Roll controller nodes on num.partitions
change
#10594
Roll controller nodes on num.partitions
change
#10594
Conversation
Signed-off-by: Jakub Scholz <www@scholzj.com>
num.partitions
change
The change looks good to me, but tagging @showuon who reviewed the list when it was initially added for awareness. |
/azp run regression |
Azure Pipelines successfully started running 1 pipeline(s). |
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.
Thanks for the fix!
I will re-look at the list again when available.
@showuon Not sure it is worth the time. Hopefully, this will finally work properly in Kafka 3.9 and we will be able to get rid of the list. |
I thought we still need it after kafka 4.0 (without ZK) because we need to know if the changed configs need to roll controller or not. Why could we get rid of the list? |
I thought that being able to talk to controllers should be enough for that. But maybe I'm wrong. @tinaselenge might know better. |
Type of change
Description
Currently, we do not roll the controller-only nodes when
num.partitions
option changes. But this option seems to be used by the controller nodes and not brokers. So any changes to it are ignored unless the controllers are rolled. This PR adds it to the list of controller relevant options, so that we roll the controllers when it is changed.This was raised up in https://cloud-native.slack.com/archives/CMH3Q3SNP/p1726561281223539
Checklist