-
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
Allow KafkaRoller talk to controller directly #10016
Conversation
c256f5a
to
93053e7
Compare
1bf6fab
to
0f6d51f
Compare
0f6d51f
to
eefbd4c
Compare
...perator/src/main/java/io/strimzi/operator/cluster/model/KafkaBrokerConfigurationBuilder.java
Outdated
Show resolved
Hide resolved
52d9241
to
bb928d6
Compare
bb928d6
to
6e03523
Compare
/azp run regression |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run zookeeper-regression |
Azure Pipelines successfully started running 1 pipeline(s). |
I will check the regression test failures. |
@scholzj can you please kick off the regression tests again? The failed system tests seem to pass for me when running locally. |
@tinaselenge could you please rebase to avoid running |
6e03523
to
99cc9e2
Compare
thanks @Frawless . I rebased now. |
/azp run regression |
/azp run zookeeper-regression |
Azure Pipelines successfully started running 1 pipeline(s). |
1 similar comment
Azure Pipelines successfully started running 1 pipeline(s). |
I started the regressions. But the Unit test failure seems related to your PR. |
/azp run zookeeper-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. I left some questions / nits.
operator-common/src/main/java/io/strimzi/operator/common/Annotations.java
Outdated
Show resolved
Hide resolved
operator-common/src/test/java/io/strimzi/operator/common/DefaultAdminClientProviderTest.java
Show resolved
Hide resolved
cluster-operator/src/main/java/io/strimzi/operator/cluster/operator/resource/KafkaRoller.java
Show resolved
Hide resolved
cluster-operator/src/main/java/io/strimzi/operator/cluster/operator/resource/KafkaRoller.java
Outdated
Show resolved
Hide resolved
/azp run regression |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run zookeeper-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.
I'm trying to run the STs on this with Kafka 3.8.1. But assuming they pass, this looks good to me. Thanks @tinaselenge.
Thank you @scholzj! |
operator-common/src/main/java/io/strimzi/operator/common/AdminClientProvider.java
Show resolved
Hide resolved
operator-common/src/test/java/io/strimzi/operator/common/DefaultAdminClientProviderTest.java
Outdated
Show resolved
Hide resolved
Update AdminClientProvider to create an admin client for controllers with BOOTSTRAP_CONTROLLERS_CONFIG set. Allow KafkaRoller create admin client against controllers nodes, if they are running 3.9.0 or later. Remove ceShouldBeFatal option as it's never set to true. Signed-off-by: Gantigmaa Selenge <[email protected]>
Signed-off-by: Gantigmaa Selenge <[email protected]>
Signed-off-by: Gantigmaa Selenge <[email protected]>
Signed-off-by: Gantigmaa Selenge <[email protected]>
Signed-off-by: Gantigmaa Selenge <[email protected]>
Signed-off-by: Gantigmaa Selenge <[email protected]>
d249582
to
dc4024a
Compare
Thanks for the PR @tinaselenge |
Signed-off-by: Gantigmaa Selenge <[email protected]>
This reverts commit 1f1a16d. This commit caused Warning messages indicating that describeQuorum request was sent to a non active controller therefore failed rolling a controller-only node. We discovered that non active controller does not forward the request to the active controller like broker does, but returns NOT_LEADER_OR_FOLLOWER error. This issue gets resolved by itself eventually after retrying the request several times, because the describeQuorum gets sent to the active controller at some point. However, it could cause some delay in rolling controller-only nodes, due to the number of retrying. Reverting this commit from 0.45.0 release branch, and the issue will be fixed properly in the main branch to target the next release.
This reverts commit 1f1a16d. This commit caused Warning messages indicating that describeQuorum request was sent to a non active controller therefore failed rolling a controller-only node. We discovered that non active controller does not forward the request to the active controller like broker does, but returns NOT_LEADER_OR_FOLLOWER error. This issue gets resolved by itself eventually after retrying the request several times, because the describeQuorum gets sent to the active controller at some point. However, it could cause some delay in rolling controller-only nodes, due to the number of retrying. Reverting this commit from 0.45.0 release branch, and the issue will be fixed properly in the main branch to target the next release. Signed-off-by: Gantigmaa Selenge <[email protected]>
…0.45.x release (#10944) Signed-off-by: Gantigmaa Selenge <[email protected]>
Type of change
Select the type of your PR
Description
There will be a follow up PR to dynamically apply configurations for controllers (with version 3.9.0 or later) using the admin client instead of how we currently restart controllers when any config changes.
Closes #9692
Checklist
Please go through this checklist and make sure all applicable tasks have been done