[
https://issues.apache.org/jira/browse/KAFKA-16619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17841997#comment-17841997
]
David Arthur commented on KAFKA-16619:
--------------------------------------
Thanks for the report, [~fmethot]. I agree we can improve this log message to
avoid confusing the operator. The rationale for logging this at a WARN is that
this information is highly relevant to any cluster that is going through or has
gone through a migration. Users almost always have WARN enabled in their logger
settings.
For the case of a de-novo KRaft cluster, we can create a special message rather
than just logging the state enum.
> Unnecessary controller warning : "Loaded ZK migration state of NONE"
> --------------------------------------------------------------------
>
> Key: KAFKA-16619
> URL: https://issues.apache.org/jira/browse/KAFKA-16619
> Project: Kafka
> Issue Type: Improvement
> Components: controller
> Affects Versions: 3.6.2
> Reporter: F Méthot
> Priority: Trivial
>
> When we launch a fresh cluster of Kafka and Kraft Controller, no zookeeper
> involved.
> We get this warning in the controller log:
> [2024-04-15 03:44:33,881] WARN [QuorumController id=3] Performing controller
> activation. Loaded ZK migration state of NONE.
> (org.apache.kafka.controller.QuorumController)
>
> Our project has no business with Zookeeper, seeing this message prompted us
> to investigate and spend time looking up this warning to find an explanation.
> We have that setting
> {_}zookeeper.metadata.migration.enable{_}=false
> and we still get that warning.
> In future version, to avoid further confusion this message should not be
> showed when zookeeper is not involved at all .
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
