cmccabe opened a new pull request, #15306: URL: https://github.com/apache/kafka/pull/15306
This patch addresses a few minor observability and operational concerns for ZK to KRaft migrations. The "MetadataType" metric is added to both the brokers and controllers, as defined in KIP-866. The values are: 1 (ZooKeeper), 2 (KRaft), 3 (Dual-Write). The brokers will only ever report ZooKeeper or KRaft, while the controller can also report Dual-Write depending on the state of the ZK migration. The "MigratingZkBrokerCount" metric is added to the ZK controller, where the value will always be zero. This aligns this metric with the KRaft controller, which makes monitoring a bit simpler. During the ZK to KRaft migration, both of these metrics can be useful. Observing a non-zero MigratingZkBrokerCount means that the cluster is in a hybrid state with some ZK brokers and a KRaft controller. Also, including a definitive metric for "is this KRaft or ZK?" is useful when observing brokers come up as KRaft during the migration process. This patch also adds an internal config "zookeeper.metadata.migration.min.batch.size" to tune the batch size for the initial metadata migration. The batch size default is set to 200 (down from 1000). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: jira-unsubscr...@kafka.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
