Return-Path: Delivered-To: apmail-hadoop-zookeeper-user-archive@minotaur.apache.org Received: (qmail 99183 invoked from network); 4 May 2009 18:11:36 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 4 May 2009 18:11:36 -0000 Received: (qmail 8489 invoked by uid 500); 4 May 2009 18:11:36 -0000 Delivered-To: apmail-hadoop-zookeeper-user-archive@hadoop.apache.org Received: (qmail 8438 invoked by uid 500); 4 May 2009 18:11:36 -0000 Mailing-List: contact zookeeper-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: zookeeper-user@hadoop.apache.org Delivered-To: mailing list zookeeper-user@hadoop.apache.org Received: (qmail 8428 invoked by uid 99); 4 May 2009 18:11:36 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 May 2009 18:11:36 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of ted.dunning@gmail.com designates 209.85.217.167 as permitted sender) Received: from [209.85.217.167] (HELO mail-gx0-f167.google.com) (209.85.217.167) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 May 2009 18:11:28 +0000 Received: by gxk11 with SMTP id 11so7914399gxk.5 for ; Mon, 04 May 2009 11:11:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:message-id:subject:to:content-type; bh=0RZYyL8QP36KF286i461N/fXJ2I6mvosmmzYAKiqUeY=; b=O494Xz3GJf2uKfS+xsUda1IaUbr7fNy7gbbaACdGS5av9Fpiy62WIzoUJcjBg8iAhy i/mEVJ47QtysIgXww+SA+Jns6+W2Yhdo75WY3GsCcDHbi77phZyvaB5Y9FhNyeZdI1YC AbNge6+Fe/WZDE4X7hujoPVcLbUxZcHleAjx8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; b=on7PqQ0gaMskAggwk92Md58gkX5Uj38CPY8UGb6/T76Zyv1HD/50GxTvqmRWZqOuwo 8wsucv3yLRZSr0PIp8pOPTZpdGzusWeGry3cT+cMq1IUgr6SvEExcRWzb2b/Vcsr2zAo TNPKgNa1HdpzssydBBJo4wr30rUD23Zj9ws2w= MIME-Version: 1.0 Received: by 10.151.143.3 with SMTP id v3mr12662118ybn.6.1241460667135; Mon, 04 May 2009 11:11:07 -0700 (PDT) In-Reply-To: References: From: Ted Dunning Date: Mon, 4 May 2009 11:10:52 -0700 Message-ID: Subject: Re: Moving ZooKeeper Servers To: zookeeper-user@hadoop.apache.org Content-Type: multipart/alternative; boundary=00151757080211366c04691a16d9 X-Virus-Checked: Checked by ClamAV on apache.org --00151757080211366c04691a16d9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I think it would be easier to add the production machines to the cluster one by one and then remove the pre-production ZK instances from the cluster one by one. This gives you continuity that you lack otherwise. Adding machines is a matter of changing the configuration on each ZK and restarting ZK on that machine. You could add the machines in a lump if you don't add so many as to prevent the cluster from having a quorum. The configuration change and restart can be easily scripted and goes quite quickly. After the hand-off, you can bring the pre-production machines machines back up with a smaller cluster configuration. Of course, this trick only works if you have no production ZK already in place so it won't work the second time around. It is also a bit unusual for the complete state of a pre-production staging cluster to be important enough to preserve. On Mon, May 4, 2009 at 10:35 AM, Satish Bhatti wrote: > ... (2) At some point, we want to switch the preproduction instance to be > the > production instance. For the ZooKeeper servers, we will copy the data + > logs directories from the pre machines currently running ZooKeeper to the > prod machines that will be running ZooKeeper, and start up ZooKeeper on > those machines. Is this all that is necessary so that the new ZooKeeper > cluster effectively continues from where the pre cluster left off? Am I > missing something? > > -- Ted Dunning, CTO DeepDyve --00151757080211366c04691a16d9--