Return-Path: X-Original-To: apmail-zookeeper-user-archive@www.apache.org Delivered-To: apmail-zookeeper-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0944C100CD for ; Fri, 19 Dec 2014 15:47:18 +0000 (UTC) Received: (qmail 90558 invoked by uid 500); 19 Dec 2014 15:47:17 -0000 Delivered-To: apmail-zookeeper-user-archive@zookeeper.apache.org Received: (qmail 90505 invoked by uid 500); 19 Dec 2014 15:47:17 -0000 Mailing-List: contact user-help@zookeeper.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@zookeeper.apache.org Delivered-To: mailing list user@zookeeper.apache.org Received: (qmail 90489 invoked by uid 99); 19 Dec 2014 15:47:16 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Dec 2014 15:47:16 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW X-Spam-Check-By: apache.org Received-SPF: error (athena.apache.org: local policy) Received: from [209.85.212.181] (HELO mail-wi0-f181.google.com) (209.85.212.181) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Dec 2014 15:47:11 +0000 Received: by mail-wi0-f181.google.com with SMTP id r20so2217575wiv.2 for ; Fri, 19 Dec 2014 07:46:30 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=qyMIISB8cLC4AYlhMBcam8mfDM/j0ATTCo/eszu//Vs=; b=BFLQMRIcjGC0NhIyE9eBIo3R49YHDgkcWzBu6FFd9ZuMkvjzVFZE7ptOMyh7rl2cvu 510X3EkSY17R9pWyMCE7AFgMHimsDfi1pRn9J3c8w21jviEsOy35/46RDgs5F+R//BQK 2YsSEcIVVnLV/lL1tGBQYlfYyY/dxII05OxTlfoWH6Juomilvwsf1CGdYBtFuTlmYIyJ 6ArJWg52c6go4GqknIU4mfeh+XQtUVfyXre8JHGSt/9/03YZ0db33muBgiMI+Y+QysJW m4QvVrWfKzbNwmrU/ffOFM+zVfzIdV8JSNvNIbbfemap4UmQzDYwGlW3QaCqSMyJ29G6 K79A== X-Gm-Message-State: ALoCoQm1sPI8x03SckKi9sFpU/cMYkl2sS5iFwUowKuJreEtz3S0tP90C/32l15WcD8hpA8mJPeO MIME-Version: 1.0 X-Received: by 10.194.110.69 with SMTP id hy5mr16076517wjb.121.1419003990540; Fri, 19 Dec 2014 07:46:30 -0800 (PST) Received: by 10.180.106.9 with HTTP; Fri, 19 Dec 2014 07:46:30 -0800 (PST) In-Reply-To: References: Date: Fri, 19 Dec 2014 10:46:30 -0500 Message-ID: Subject: Re: why is the myid file needed? From: Ben Hsu To: user@zookeeper.apache.org Content-Type: multipart/alternative; boundary=089e010d867acaa2ad050a939c36 X-Virus-Checked: Checked by ClamAV on apache.org --089e010d867acaa2ad050a939c36 Content-Type: text/plain; charset=UTF-8 Hello Alex, Thats interesting. Does that mean if I lose a VM, I can spin a new VM with the same DNS name and myid file, attach it to the cluster, and ZK will fill in the data bits? On Thu, Dec 18, 2014 at 5:41 PM, Alexander Shraer wrote: > > Hi, > > The id uniquely identifies a server during its lifetime. IP and port can be > change during runtime but the id remains. > > Also theoretically its possible for multiple servers to have the same IP > and port, although probably no one will define it like that :) > > Alex > > On Thu, Dec 18, 2014 at 12:47 PM, Ben Hsu > wrote: > > > > Hello > > > > A friend at work asked me why the myid file is needed. Can't zookeeper > > divine which node a request is coming from based on the source IP and > port? > > > --089e010d867acaa2ad050a939c36--