[KAFKA-7335] Store clusterId locally to ensure broker joins the right cluster

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.4.0
• Assignee: David Jacot
• Reporter: Jason Gustafson
• Created: 23/Aug/18 22:14
• Updated: 25/Aug/19 20:59
• Resolved: 14/Aug/19 16:57

Description

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 that we could store the clusterId locally after initial registration and verify upon startup that the locally stored value matches what is in zookeeper.

Issue Links

• links to: GitHub Pull Request #7189