maoling created ZOOKEEPER-3535:
----------------------------------
Summary: add a new property:initial-cluster-token to identify a
ensemble
Key: ZOOKEEPER-3535
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3535
Project: ZooKeeper
Issue Type: New Feature
Components: documentation, server
Reporter: maoling
Assignee: maoling
Fix For: 3.6.0
Every new zk cluster generates a new cluster ID based on the initial cluster
configuration and a user-provided unique initial-cluster-token value. By having
unique cluster ID’s, zk is protected from cross-cluster interaction which could
corrupt the cluster.
Usually this warning happens after tearing down an old cluster, then reusing
some of the peer addresses for the new cluster. If any zk process from the old
cluster is still running it will try to contact the new cluster. The new
cluster will recognize a cluster ID mismatch, then ignore the request and emit
this warning. This warning is often cleared by ensuring peer addresses among
distinct clusters are disjoint.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
