From issues-return-897-archive-asf-public=cust-asf.ponee.io@zookeeper.apache.org Fri Sep 6 02:28:02 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id 763E9180674 for ; Fri, 6 Sep 2019 04:28:02 +0200 (CEST) Received: (qmail 46900 invoked by uid 500); 6 Sep 2019 12:22:13 -0000 Mailing-List: contact issues-help@zookeeper.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@zookeeper.apache.org Delivered-To: mailing list issues@zookeeper.apache.org Received: (qmail 46880 invoked by uid 99); 6 Sep 2019 12:22:13 -0000 Received: from mailrelay1-us-west.apache.org (HELO mailrelay1-us-west.apache.org) (209.188.14.139) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Sep 2019 12:22:13 +0000 Received: from jira-he-de.apache.org (static.172.67.40.188.clients.your-server.de [188.40.67.172]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id CF794E312C for ; Fri, 6 Sep 2019 02:28:00 +0000 (UTC) Received: from jira-he-de.apache.org (localhost.localdomain [127.0.0.1]) by jira-he-de.apache.org (ASF Mail Server at jira-he-de.apache.org) with ESMTP id 21FB2780697 for ; Fri, 6 Sep 2019 02:28:00 +0000 (UTC) Date: Fri, 6 Sep 2019 02:28:00 +0000 (UTC) From: "maoling (Jira)" To: issues@zookeeper.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (ZOOKEEPER-3535) add a new property:initial-cluster-token to identify a ensemble MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 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 cluste= r configuration and a user-provided unique=C2=A0initial-cluster-token=C2=A0= value. By having unique cluster ID=E2=80=99s, zk is protected from cross-cl= uster interaction which could corrupt the cluster. Usually this warning happens after tearing down an old cluster, then reusin= g some of the peer addresses for the new cluster. If any zk process from th= e 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 a= nd emit this warning. This warning is often cleared by ensuring peer addres= ses among distinct clusters are disjoint. -- This message was sent by Atlassian Jira (v8.3.2#803003)