[
https://issues.apache.org/jira/browse/KAFKA-12806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17897345#comment-17897345
]
Colin McCabe edited comment on KAFKA-12806 at 11/12/24 3:08 AM:
----------------------------------------------------------------
I think this was one of many KRaft metrics bugs we fixed in the 3.0 release.
was (Author: cmccabe):
I think this was one of many metrics bugs we fixed in the 3.0 release.
> 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
> Fix For: 3.0.0
>
>
> 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.20.10#820010)
