[
https://issues.apache.org/jira/browse/KAFKA-7335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-7335:
-------------------------------
Fix Version/s: 2.4.0
> 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
> Assignee: David Jacot
> Priority: Major
> Fix For: 2.4.0
>
>
> 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.14#76016)
