[
https://issues.apache.org/jira/browse/KAFKA-14939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17872491#comment-17872491
]
Colin McCabe edited comment on KAFKA-14939 at 8/9/24 10:35 PM:
---------------------------------------------------------------
[~mumrah] I can't remember why we wanted to do this. It should be fine to just
expose the metric even if migration isn't possible?
I'll close this as WONTFIX. Anyway, if you disagree, feel free to reopen (and
race to get this done in 3.9, the final 3.x release) :)
was (Author: cmccabe):
[~mumrah] I can't remember why we wanted to do this. It should be fine to just
expose the metric even if migration isn't possible?
I'll close this as WONTFIX. Anyway, if you disagree, feel free to reopen (and
race to get this done in 3.9, the final 3.x release) (heh) :)
> Only expose ZkMigrationState metric if metadata.version supports it
> -------------------------------------------------------------------
>
> Key: KAFKA-14939
> URL: https://issues.apache.org/jira/browse/KAFKA-14939
> Project: Kafka
> Issue Type: Sub-task
> Affects Versions: 3.5.0
> Reporter: David Arthur
> Assignee: HaiyuanZhao
> Priority: Minor
>
> We should only expose the KafkaController.ZkMigrationState JMX metric if the
> cluster is running on a metadata.version that supports migrations.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
