-
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
[KRaft] KafkaRoller
is strugling to transition controller-only nodes to mixed nodes
#9434
Labels
Comments
4 tasks
Discussed in the community call on 14.12.: Should be looked into and improved. There seem to be several options how to find out the current role of the node rather than the desired role from the NodeRef objects:
|
scholzj
added a commit
to scholzj/strimzi-kafka-operator
that referenced
this issue
Feb 14, 2024
…loses strimzi#9434 Signed-off-by: Jakub Scholz <[email protected]>
scholzj
added a commit
to scholzj/strimzi-kafka-operator
that referenced
this issue
Feb 14, 2024
…loses strimzi#9434 Signed-off-by: Jakub Scholz <[email protected]>
6 tasks
scholzj
added a commit
to scholzj/strimzi-kafka-operator
that referenced
this issue
Feb 14, 2024
…loses strimzi#9434 Signed-off-by: Jakub Scholz <[email protected]>
scholzj
added a commit
to scholzj/strimzi-kafka-operator
that referenced
this issue
Feb 14, 2024
…loses strimzi#9434 Signed-off-by: Jakub Scholz <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When having a controller-only node pool and trying to add a broker role to it, the operator /
KafkaRoller
seem to strugle to roll the nodes to change the configuration. It seems they try to treat the nodes as mixed nodes already, but fail to connect to them on the port 9091 as they are still controllers only.It looks like the eventually roll them after the timeout expires. But it is not clear if they properly ensure the quorum availability during this. If nothing else, we have to check that this does not break the quorum -> but if possible, we should try to improve the process.
The text was updated successfully, but these errors were encountered: