You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "Ryan Dielhenn (Jira)" <ji...@apache.org> on 2021/09/02 00:01:22 UTC

[jira] [Updated] (KAFKA-13245) KIP 771: Change behavior of how controller metrics are exposed when using KRaft.

     [ https://issues.apache.org/jira/browse/KAFKA-13245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ryan Dielhenn updated KAFKA-13245:
----------------------------------
    Description: 
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

  was:Zookeeper 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.


> 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.3.4#803005)