You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Muralidhar Basani (Jira)" <ji...@apache.org> on 2026/05/06 18:44:00 UTC
[jira] [Commented] (KAFKA-20530) Log cluster.id at startup phase
[ https://issues.apache.org/jira/browse/KAFKA-20530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18078766#comment-18078766 ]
Muralidhar Basani commented on KAFKA-20530:
-------------------------------------------
[~nicolas.guyomar] yea, kafka does not expose cluster.id as a standalone metric
> Log cluster.id at startup phase
> -------------------------------
>
> Key: KAFKA-20530
> URL: https://issues.apache.org/jira/browse/KAFKA-20530
> Project: Kafka
> Issue Type: Improvement
> Reporter: Nicolas Guyomar
> Priority: Minor
>
> Hi team,
> In the scenario where a cluster would no longer start because of such "RaftManager Unexpected error INCONSISTENT_CLUSTER_ID in FETCH response" during bootstrap error, would it be possible that the local meta.properties content (or just cluster.id) be logged at INFO level during the startup phase, so that we can troubleshoot using logs, without having to dump the file content ?
> Thank you
--
This message was sent by Atlassian Jira
(v8.20.10#820010)