[jira] [Updated] (KAFKA-12806) KRaft: Confusing leadership status exposed in metrics for controller without quorum

["Gunnar Morling (Jira)" <ji...@apache.org>]

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

Gunnar Morling updated KAFKA-12806:
-----------------------------------
    Summary: KRaft: Confusing leadership status exposed in metrics for controller without quorum  (was: KRaft: Confusing leadership status exposed for controller without quorum)

> KRaft: Confusing leadership status exposed in metrics for controller without quorum
> -----------------------------------------------------------------------------------
>
>                 Key: KAFKA-12806
>                 URL: https://issues.apache.org/jira/browse/KAFKA-12806
>             Project: Kafka
>          Issue Type: Bug
>    Affects Versions: 2.8.0
>            Reporter: Gunnar Morling
>            Priority: Major
>
> I'm testing Kafka in the new KRaft mode added in 2.8. I have a cluster of three Kafka nodes (all combined nodes). After starting all components, I first stop the current controller of the Kafka cluster, then I stop the then controller of the Kafka cluster. At this point, only one Kafka node out of the original three and Connect is running. In the new KRaft-based metrics, "leader" is exposed as the role for that node, and its id is shown as the current leader. Also in the metadata shell, that node is shown as the quorum leader via /metadataQuorum/leader. This is pretty confusing, as one out of three nodes cannot have the quorum. I believe this is mostly an issue of displaying the status, as for instance creating a topic in this state times out.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)