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 28103CCD8 for ; Fri, 19 Jul 2013 18:46:21 +0000 (UTC) Received: (qmail 38735 invoked by uid 500); 19 Jul 2013 18:46:19 -0000 Delivered-To: apmail-zookeeper-user-archive@zookeeper.apache.org Received: (qmail 38723 invoked by uid 500); 19 Jul 2013 18:46:19 -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 38715 invoked by uid 99); 19 Jul 2013 18:46:18 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Jul 2013 18:46:18 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of shralex@gmail.com designates 209.85.223.180 as permitted sender) Received: from [209.85.223.180] (HELO mail-ie0-f180.google.com) (209.85.223.180) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Jul 2013 18:46:12 +0000 Received: by mail-ie0-f180.google.com with SMTP id f4so9938734iea.39 for ; Fri, 19 Jul 2013 11:45:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=kMZaJOhNM0plAxdJ5ZOpOhNxQcIjE5+WcuV7wZm7Rgw=; b=BhZBpLmYnHf3cOknIcedlIZDMJUUWAW3kT2aGWsVmTpOjaR/yvAtmmlI/Vx8CW3sFb pbos1nm9pI8J0uc4FmyLFkl7eLUhv78pQNaf/2I+icLlESyvUkNxbMhM0CgqhKB+EZ1s aYnphT08W/3JfDVEvLH3V1+DtDiiNlFrol9Y0QbHdkx6KaPzKTLghbM4z6WemhrP/3sA /PjOSKiXFS+18JLKVrcHVL/sHaq4k+4z2A5SpXv3DbjO436Ro3gMnDrzOSg4XfAO3LW5 AGD/MR4wH3JZcHoogOi7YKUNaJV8wr9/Ef7vhVHCLnbq1NDNmPEtKBkg79mpPdkSH3Jf bcIA== X-Received: by 10.42.63.207 with SMTP id d15mr12202963ici.21.1374259551322; Fri, 19 Jul 2013 11:45:51 -0700 (PDT) MIME-Version: 1.0 Received: by 10.64.131.106 with HTTP; Fri, 19 Jul 2013 11:45:31 -0700 (PDT) In-Reply-To: References: <7527D9F1-F9A5-44C7-9739-790ECBE138CE@jordanzimmerman.com> From: Alexander Shraer Date: Fri, 19 Jul 2013 11:45:31 -0700 Message-ID: Subject: Re: Zookeeper ensemble backup questions? To: user@zookeeper.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org thanks, Sergey! On Fri, Jul 19, 2013 at 11:38 AM, Sergey Maslyakov wrote: > Alexander, > > I cannot speak to that intelligently. I don't know implementation and > design details well enough. However, a snapshot of this kind, if it is > produced by ZooKeeperServer.takeSnapshot() method, should contain not just > the DataTree content but the sessions too. I am not sure if this covers > ephemeral nodes though but I am pretty sure this is way Zookeeper server > takes snapshots driven by the transaction count. > > > Regards, > /Sergey > > > On Fri, Jul 19, 2013 at 1:26 PM, Alexander Shraer wrote: > >> Sergey, >> >> Can you explain what happens with ephemeral nodes during snapshot and >> restore ? >> >> Thanks, >> Alex >> >> On Fri, Jul 19, 2013 at 11:21 AM, Sergey Maslyakov >> wrote: >> > Jordan, >> > >> > It depends on the use case. Some use cases deal with 99% or more of >> static >> > non-ephemeral nodes. And this is why the Exhibitor approach does not work >> > for those use cases. >> > >> > >> > Regards, >> > /Sergey >> > >> > >> > On Fri, Jul 19, 2013 at 1:13 PM, Jordan Zimmerman < >> > jordan@jordanzimmerman.com> wrote: >> > >> >> I'm a bit late to this one but I don't understand the need for complete >> >> backup of ZK data. In my experience, 99% of ZNodes are ephemeral. >> >> Therefore, it would be wrong to restore those nodes. In a disaster, the >> >> connection sessions would expire and you would not want ephemeral nodes >> >> restored. This is why in Exhibitor I took the approach of selective >> restore. >> >> >> >> -Jordan >> >> >> >> On Jul 19, 2013, at 11:00 AM, jack ma wrote: >> >> >> >> > I asked those question in the thread >> >> > >> >> >> http://mail-archives.apache.org/mod_mbox/zookeeper-user/201307.mbox/%3cCAB+cfdwhOV0JfB04=MpO_+i-4ou=VbL=EG2XS557+j+698jx3A@mail.gmail.com%3e >> >> , >> >> > but there is no response for that. >> >> > >> >> > So I posted those questions again here, hopefully I could get helps >> >> > from the community. >> >> > >> >> > I want to make sure I am fully understanding the procedures of >> zookeeper >> >> > backup and disaster recovery: >> >> > >> >> > For the backup procedures at zookeeper assemble: >> >> > (1) Login to any host which state is "Serving" >> >> > Question: >> >> > Do I have to login to leader node, or any node is ok? >> >> > (2) Copy latest snapshot file and transaction log from version-2 >> >> directory. >> >> > Question: >> >> > How to make sure we do not copy corrupt files if the >> >> > snapshot/transaction log is in the middle of update? Do we have to >> >> shutdown >> >> > the node to make the copy? >> >> > besides the transaction log and snapshot, do we have >> to >> >> > copy other files such as the ecoch files >> >> > >> >> > For the disaster recovery procedures at zookeeper assemble: >> >> > (1) recreate the machines for the zookeeper ensemble >> >> > (2) copy snapshot/transaction log we backed up into the zookeeper >> >> > dataDir\version-2 and logDir\version2. >> >> > Question: >> >> > Do we have to copy the epoch files? >> >> > Do we have to copy snapshot/transaction log backed up >> to >> >> > all the zookeeper node, or just the first node we starts? >> >> > >> >> > Appreciate your time and help. >> >> > Jack >> >> >> >> >>