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 ACAF254E7 for ; Thu, 12 May 2011 17:17:08 +0000 (UTC) Received: (qmail 96419 invoked by uid 500); 12 May 2011 17:17:08 -0000 Delivered-To: apmail-zookeeper-user-archive@zookeeper.apache.org Received: (qmail 96394 invoked by uid 500); 12 May 2011 17:17:08 -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 96386 invoked by uid 99); 12 May 2011 17:17:08 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 May 2011 17:17:08 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of ted.dunning@gmail.com designates 209.85.212.42 as permitted sender) Received: from [209.85.212.42] (HELO mail-vw0-f42.google.com) (209.85.212.42) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 May 2011 17:17:03 +0000 Received: by vwl1 with SMTP id 1so1838826vwl.15 for ; Thu, 12 May 2011 10:16:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type; bh=6i5Q/ZMui0P4nFapyoXw9XtBIz6s7IaPoflvcnUiPm0=; b=vHxPeArLjicChBwsIaWjF/uHPAdfjbpBaDryMKNBHT+vSwTFf1sHDXz1tHPQUGazvP YY5zXHmoYmSRygYsJX6kPJDQNO9iw+rYH747k1q2ak9ah2EqFsiJV5CIaTdGskcxj0QE UwIg1Zv/9D+WMzZk+vyyQftE35UJLV2LoEXZA= 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=R4eYLl9+Ce/ZZ8M8/Qhgk4gurPPR8DmGKbllxQHsS1UXAOv+G0IWQrZ3jQuPxn+uQb HcHGLmSEhlcdMsF45FMziRaHVpY/zKALRhM+5j2EvBcFU+ygfW1I2gQ8kRLngQdCnPZk uD9uT8HpZgUsUoI4gMsJtNaFtKDD02yFI6G2U= Received: by 10.52.91.241 with SMTP id ch17mr648970vdb.190.1305220602141; Thu, 12 May 2011 10:16:42 -0700 (PDT) MIME-Version: 1.0 Received: by 10.52.110.2 with HTTP; Thu, 12 May 2011 10:16:22 -0700 (PDT) In-Reply-To: <939285.27386.qm@web137316.mail.in.yahoo.com> References: <774134.13077.qm@web137313.mail.in.yahoo.com> <22975.34233.qm@web137310.mail.in.yahoo.com> <432932.89619.qm@web137310.mail.in.yahoo.com> <939285.27386.qm@web137316.mail.in.yahoo.com> From: Ted Dunning Date: Thu, 12 May 2011 10:16:22 -0700 Message-ID: Subject: Re: Changing hosts To: user@zookeeper.apache.org, "Murali Krishna. P" Content-Type: multipart/alternative; boundary=20cf307c9db2581a9104a3175a51 --20cf307c9db2581a9104a3175a51 Content-Type: text/plain; charset=UTF-8 When you ask each of the new nodes what their status is, what do they say? On Thu, May 12, 2011 at 9:09 AM, Murali Krishna. P wrote: > Hi, > even after 1 hour, the version-2 dir seems to be empty on all 3 new > nodes. Can i just copy the last log.x and last snapshot.x file from > corresponding old nodes and bounce new nodes with new config? > > > Thanks, > Murali Krishna > > > ________________________________ > From: Murali Krishna. P > To: Vishal Kher ; "user@zookeeper.apache.org" < > user@zookeeper.apache.org> > Sent: Thursday, 12 May 2011 8:45 PM > Subject: Re: Changing hosts > > Thanks for the suggestion, but I had already started the process which Alex > had mentioned and DEF is started with ABC. How can we know whether DEF is > synced ? the data/version-2 dir is empty, i guess i need to wait till it > gets some data there? > > > Thanks, > Murali Krishna > > > ________________________________ > From: Vishal Kher > To: user@zookeeper.apache.org; Murali Krishna. P > Sent: Thursday, 12 May 2011 7:24 PM > Subject: Re: Changing hosts > > > Hi, > > Since you can stop clients, another way to achieve what Alex suggested is > to: > > 1. stop clients > 2. stop all current zk servers (a_i) > 3. scp -r /etc/zookeeper/ from a_i to b_i > 4. scp -r /var/zookeeper/ from a_i to b_i > 5. On all b_i, edit /etc/zookeeper/zoo.cfg to reflect the correct IP > addresses > 5 start all b_i > > This is assuming that stopping ZK server is ok in our environment. > > -Vishal > > > On Thu, May 12, 2011 at 2:07 AM, Murali Krishna. P > wrote: > > Thanks for the responses, > > I have the luxury of stopping the clients during the operations. So, > I would go with the second approach of cloning. > > > > > >Thanks, > >Murali Krishna > > > > > > > >________________________________ > >From: Ted Dunning > >To: Alexander Shraer > >Cc: "user@zookeeper.apache.org" ; Murali > Krishna. P ; "zookeeper-user@hadoop.apache.org" < > zookeeper-user@hadoop.apache.org> > >Sent: Thursday, 12 May 2011 5:27 AM > >Subject: Re: Changing hosts > > > > > > > >Alex, > > > >I think that this process does a slightly different thing. Your process > is good for cloning a cluster, but it doesn't address the problem of > transitioning a working cluster. My process never has two clusters with the > same data so all transactions will always be applied to a single notional > version of the data. > > > >The reason that this is important is a part of the process that neither of > us mentioned. That is how to transition the clients. My assumption is that > before the transition, all clients would re-open their ZK connection with > all 6 nodes in the list of servers. Once this is done, my process will lead > the clients through the transition in a way that all updates will be visible > to all clients. At the end, the clients should (eventually) trim their list > of servers to the shorter list of new servers. > > > >With a cluster clone operation, there will be moments when some clients > connect to one cluster and some connect to the other. That makes it hard to > understand how this will work well. > > > >The OP can probably clarify which task they really wanted to accomplish. > > > > > > > > > >On Wed, May 11, 2011 at 4:49 PM, Alexander Shraer > wrote: > > > >Hi Ted, > >> > >>There's a simpler way that works. Suppose that the original servers are > A, B and C, and the new ones > >>are D, E, F. Configure D, E and F to be in the configuration A, B, C, D, > E, F and start them. Don't do any changes to > >>A, B and C. After D, E and F synch with the leader (or at least 2 of them > do), turn them off, change their config files to D, E, F and bring them up > again. > >> > >>Alex > >> > >> > >> > >> > >> > >>> -----Original Message----- > >>> From: Ted Dunning [mailto:ted.dunning@gmail.com] > >>> Sent: Tuesday, May 10, 2011 8:39 AM > >>> To: user@zookeeper.apache.org; Murali Krishna. P > >>> Cc: zookeeper-user@hadoop.apache.org > >>> Subject: Re: Changing hosts > >>> > >>> Step 1: configure two of the new hosts to be part of a 5 node cluster > >>> containing all of the > >>> original nodes. > >>> > >>> Step 2: reconfigure each of the original 3 nodes to be part of the the > >>> 5 > >>> node cluster. > >>> > >>> Step 3: bounce each of the originals and start the two new servers. > >>> > >>> Step 4: configure the 6th server (previously untouched) to be part of a > >>> three node cluster > >>> containing only the 3 new nodes. > >>> > >>> Step 5: reconfigure servers 4 and 5. > >>> > >>> Step 6: bounce servers 4 and 5 and start server 6. > >>> > >>> Done. > >>> > >>> (wait for somebody else to critique this procedure before proceeding > >>> with > >>> it) > >>> > >>> On Tue, May 10, 2011 at 7:54 AM, Murali Krishna. P > >>> wrote: > >>> > >>> > Hi, > >>> > I have a zookeeper cluster (3.2.2) with 3 hosts. I need to > >>> replace all > >>> > the 3 hosts with different machines. What is the best way to achieve > >>> this > >>> > without any data loss? I can shutdown my clients during this > >>> operation. > >>> > > >>> > > >>> > > >>> > Thanks, > >>> > Murali Krishna > >> --20cf307c9db2581a9104a3175a51--