-
Notifications
You must be signed in to change notification settings - Fork 14.2k
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
KAFKA-18530 Remove ZooKeeperInternals #18641
Changes from 21 commits
b7bbdff
a022b0c
6cef55f
72fc80b
8065ee7
ff19654
821acd0
2d16565
fe8b6ca
b81ae52
4ca7f31
a6a52e0
44274d4
e9b1e5b
1927166
b52aaed
b4b727d
a201ae9
dd871e2
13d9b7f
ed6353b
d098405
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -46,12 +46,12 @@ import scala.collection._ | |
import scala.jdk.CollectionConverters._ | ||
|
||
/** | ||
* Dynamic broker configurations are stored in ZooKeeper and may be defined at two levels: | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. in kraft mode, the two levels are still existent. could you please revise it instead of removing it? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Heya @m1a2st! I have a follow-up ask, while the two levels are still present they will no longer be under the path specified in this file since the path is ZK-specific. As long as we don't use this comment to generate documentation I am okay with this being removed in a subsequent PR. However, if we use this file to generate documentation could you change this as part of this PR? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think those comments in DynamicBrokerConfig are not used to generate documentation, but it will be better to correct it - as least, the description about zk path must be removed. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Okay, then I will review once they have been changed 😊! There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. |
||
* Dynamic broker configurations may be defined at two levels: | ||
* <ul> | ||
* <li>Per-broker configs persisted at <tt>/configs/brokers/{brokerId}</tt>: These can be described/altered | ||
* using AdminClient using the resource name brokerId.</li> | ||
* <li>Cluster-wide defaults persisted at <tt>/configs/brokers/<default></tt>: These can be described/altered | ||
* using AdminClient using an empty resource name.</li> | ||
* <li>Per-broker configurations are persisted at the controller and can be described | ||
* or altered using AdminClient with the resource name brokerId.</li> | ||
* <li>Cluster-wide default configurations are persisted at the cluster level and can be | ||
* described or altered using AdminClient with an empty resource name.</li> | ||
* </ul> | ||
* The order of precedence for broker configs is: | ||
* <ol> | ||
|
@@ -367,7 +367,7 @@ class DynamicBrokerConfig(private val kafkaConfig: KafkaConfig) extends Logging | |
error(s"$errorMessage: $invalidPropNames") | ||
} | ||
} | ||
removeInvalidProps(nonDynamicConfigs(props), "Non-dynamic configs configured in ZooKeeper will be ignored") | ||
removeInvalidProps(nonDynamicConfigs(props), "Non-dynamic configs will be ignored") | ||
removeInvalidProps(securityConfigsWithoutListenerPrefix(props), | ||
"Security configs can be dynamically updated only using listener prefix, base configs will be ignored") | ||
if (!perBrokerConfig) | ||
|
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.
we don't need this conversion, right?