You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Badai Aqrandista (JIRA)" <ji...@apache.org> on 2018/08/24 01:23:00 UTC
[jira] [Commented] (KAFKA-7335) Store clusterId locally to ensure
broker joins the right cluster
[ https://issues.apache.org/jira/browse/KAFKA-7335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16591030#comment-16591030 ]
Badai Aqrandista commented on KAFKA-7335:
-----------------------------------------
Can we have this manually configured as well in server.properties or like myid file in zookeeper? So user can specify explicitly that a broker is part of a certain cluster?
> Store clusterId locally to ensure broker joins the right cluster
> ----------------------------------------------------------------
>
> Key: KAFKA-7335
> URL: https://issues.apache.org/jira/browse/KAFKA-7335
> Project: Kafka
> Issue Type: Improvement
> Reporter: Jason Gustafson
> Priority: Major
>
> We have seen situations where a broker somehow got the wrong configuration and joined a different cluster than the one it was previously registered in. This can create various kinds of metadata inconsistencies in the cluster and can be difficult to debug. It was suggested in [KIP-78|https://cwiki.apache.org/confluence/display/KAFKA/KIP-78%3A+Cluster+Id] that we could store the clusterId locally after initial registration and verify upon startup that the locally stored value matches what is in zookeeper.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)