[jira] [Commented] (KAFKA-13140) KRaft brokers do not expose kafka.controller metrics, breaking backwards compatibility

["David Jacot (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KAFKA-13140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17443701#comment-17443701 ] 

David Jacot commented on KAFKA-13140:
-------------------------------------

Moving to the next release as we are past the 3.1 release code freeze.

> KRaft brokers do not expose kafka.controller metrics, breaking backwards compatibility
> --------------------------------------------------------------------------------------
>
>                 Key: KAFKA-13140
>                 URL: https://issues.apache.org/jira/browse/KAFKA-13140
>             Project: Kafka
>          Issue Type: Bug
>          Components: kraft
>    Affects Versions: 2.8.0, 3.0.0
>            Reporter: Ron Dagostino
>            Assignee: Ron Dagostino
>            Priority: Major
>             Fix For: 3.2.0
>
>
> The following controller metrics are exposed on every broker in a ZooKeeper-based (i.e. non-KRaft) cluster regardless of whether the broker is the active controller or not, but these metrics are not exposed on KRaft nodes that have process.roles=broker (i.e. KRaft nodes that do not implement the controller role).  For backwards compatibility, KRaft nodes that are just brokers should expose these metrics with values all equal to 0: just like ZooKeeper-based brokers do when they are not the active controller.
> kafka.controller:type=KafkaController,name=ActiveControllerCount
> kafka.controller:type=KafkaController,name=GlobalTopicCount
> kafka.controller:type=KafkaController,name=GlobalPartitionCount
> kafka.controller:type=KafkaController,name=OfflinePartitionsCount
> kafka.controller:type=KafkaController,name=PreferredReplicaImbalanceCount



--
This message was sent by Atlassian Jira
(v8.20.1#820001)