Uploaded image for project: 'Kafka'
  1. Kafka
  2. KAFKA-7335

Store clusterId locally to ensure broker joins the right cluster

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.4.0
    • Component/s: None
    • Labels:
      None

      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.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                dajac David Jacot
                Reporter:
                hachikuji Jason Gustafson
              • Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: