Mailing-List: contact user-help@zookeeper.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@zookeeper.apache.org
Received-SPF: pass (athena.apache.org: domain of tivv00@gmail.com designates
 209.85.160.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAJwFCa0bUh=fuQgN8Yo1R+C4VfWQqDjQRe0tNrf-XgZUqsyyqg@mail.gmail.com>
References: <4F60C181.90802@nokia.com>
	<4F60CED2.5080601@nokia.com>
	<CANcXBFP7WUceMbmEJ2etU3NESProbY01UNafnVYiQEvFOdQgmA@mail.gmail.com>
	<4F61BB76.5040505@nokia.com>
	<CANcXBFN9ASke0CUzL+Rh9tR1CjDGbojPY1oBFRvPS7JBPi6EpA@mail.gmail.com>
	<BCCAB10C331D2F4294626F5E2BE466501630ADA5@008-AM1MPN1-073.mgdnok.nokia.com>
	<CAJwFCa0bUh=fuQgN8Yo1R+C4VfWQqDjQRe0tNrf-XgZUqsyyqg@mail.gmail.com>
Date: Thu, 15 Mar 2012 22:29:54 +0200
Message-ID: 
 <CABWW-d2+mRArT8n6m972dCE0jgCEUeKij40jHFVyzsz9kaafWg@mail.gmail.com>
Subject: Re: Zookeeper on short lived VMs and ZOOKEEPER-107
From: =?KOI8-U?B?96bUwcymyiD0yc3eydvJzg==?= <tivv00@gmail.com>
To: user@zookeeper.apache.org
Cc: shralex@gmail.com
Content-Type: multipart/alternative; boundary=20cf302d4b36698c2f04bb4df4da

--20cf302d4b36698c2f04bb4df4da
Content-Type: text/plain; charset=ISO-8859-1

As for me this can work in given environment (where is it externally
ensured that old server is down until new one is up), but can't be
introduced as generic zookeeper patch. Simply because without such an
external ensurance, two servers with different IPs and same name can be
recognized by different parts of the ensemble.
BTW: Are there possibility of such a problem now with dynamic DNS and
servers started at different DNS states?
As for me, better option would be to assign IPs to your VMs dynamically.
E.g. when you think given server should become serverA, you should simply
add IPa as an alias IP for it. ARP will ensure you won't have two As and
you don't need to touch the code.

Best regards, Vitalii Tymchyshyn

--20cf302d4b36698c2f04bb4df4da--