[
https://issues.apache.org/jira/browse/KAFKA-13245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colin McCabe resolved KAFKA-13245.
----------------------------------
Resolution: Won't Fix
We decided to have standby KRaft controllers expose their metrics normally,
rather than setting everything to 0 because they were standby. Closing as
"Won't Fix".
> KIP 771: Change behavior of how controller metrics are exposed when using
> KRaft.
> --------------------------------------------------------------------------------
>
> Key: KAFKA-13245
> URL: https://issues.apache.org/jira/browse/KAFKA-13245
> Project: Kafka
> Issue Type: Improvement
> Reporter: Ryan Dielhenn
> Assignee: Ryan Dielhenn
> Priority: Major
>
> Pre-Kraft brokers expose 0 for controller metrics in the case of controller
> failover. KRaft brokers should not since they will never be elected as
> controller and since this would introduce a non-negligible performance
> impact. If a KRaft node is a "controller" process but is not the active
> controller it will expose 0 for all controller metrics since the process is
> eligible to become the active controller. This is consistent with behavior
> for controller-eligible nodes in a Kafka cluster using Zookeeper.
>
> https://cwiki.apache.org/confluence/display/KAFKA/KIP+771%3A+KRaft+brokers+should+not+expose+controller+metrics
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
