You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2019/08/09 23:51: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=16904255#comment-16904255 ]
ASF GitHub Bot commented on KAFKA-7335:
---------------------------------------
dajac commented on pull request #7189: KAFKA-7335: Store clusterId locally to ensure broker joins the right cluster
URL: https://github.com/apache/kafka/pull/7189
`clusterId` is stored in the `meta.properties`. During startup, the broker checks that it joins the correct cluster and fails fast otherwise.
The `meta.properties' is versioned. I have decided to not bump the version because 1) the clusterId is null anyway if not present in the file; and 2) bumping it means that rolling back to a previous version won't work.
Unit tests have been extended to cover the change.
### Committer Checklist (excluded from commit message)
- [ ] Verify design and implementation
- [ ] Verify test coverage and CI build status
- [ ] Verify documentation (including upgrade notes)
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
> 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
>
> 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)