Return-Path: Delivered-To: apmail-hadoop-zookeeper-user-archive@minotaur.apache.org Received: (qmail 49116 invoked from network); 1 Jul 2009 17:35:05 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 1 Jul 2009 17:35:05 -0000 Received: (qmail 36393 invoked by uid 500); 1 Jul 2009 17:35:16 -0000 Delivered-To: apmail-hadoop-zookeeper-user-archive@hadoop.apache.org Received: (qmail 36336 invoked by uid 500); 1 Jul 2009 17:35:15 -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 36326 invoked by uid 99); 1 Jul 2009 17:35:15 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Jul 2009 17:35:15 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of n13m3y3r@gmail.com designates 209.85.220.220 as permitted sender) Received: from [209.85.220.220] (HELO mail-fx0-f220.google.com) (209.85.220.220) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Jul 2009 17:35:04 +0000 Received: by fxm20 with SMTP id 20so1067505fxm.29 for ; Wed, 01 Jul 2009 10:34:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:from:date:x-google-sender-auth:message-id:subject:to :content-type:content-transfer-encoding; bh=dRYbzhEUqN64d3aIFcBPMdS9T1MwiJt/NEotaO1m4uQ=; b=HH+kdQ6ZBYnCzx5mcpSaBhjPeZyvo4BFrcCLCwdZaSFldE4HBqueehTS/zs1eNPMBY uQ/d7AkmUQdGvnv2jQ410obUS7RVZJwq+S8lC7BhYVPPmbu3gCMNN1EbYWU2xZjnO3O5 sv02EPOLOrIpCcsuTbacpyyMghy3AISuJW/Nk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:content-type :content-transfer-encoding; b=K0tbZ8WpKtr/826YWL7toLZBJpnDxYJKXXfSd+tkLlpJRvPrVU34fXq680xOpiDwrw U6I22zPqwyq0FRn5C/wGRo//eUrZcHrL6q+OyiG3+hQBujFLVGBQOmYinvmzpTVCYjAc riwRxsP+K23U3TgwLgfvELRO2uaf7LedjxUIc= MIME-Version: 1.0 Sender: n13m3y3r@gmail.com Received: by 10.239.157.140 with SMTP id q12mr841441hbc.80.1246469684272; Wed, 01 Jul 2009 10:34:44 -0700 (PDT) In-Reply-To: References: <9dba5ed30907010707y33f928ebi9e7836113eb869d9@mail.gmail.com> <643d90130907010801q54826a7cyf752be23f2dde57e@mail.gmail.com> From: Gustavo Niemeyer Date: Wed, 1 Jul 2009 14:34:23 -0300 X-Google-Sender-Auth: 7b77ffb290c1946c Message-ID: <643d90130907011034i3bb3f01arc6e1da770edebdab@mail.gmail.com> Subject: Re: Dynamic servers addition and persistent storage. To: zookeeper-user@hadoop.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi again Henry, > I hope to have a patch for both fairly soon. I should at least get ZK-368 to > a workable position this week, and ZK-107 will hopefully not be an enormous > amount of work on top of that. However, there doubtless be some slack time > for picking up bugs etc. before it gets committed as it will be a reasonably > sized patch. That's great news. I've added myself as a watcher on both tickets. > Out of interest, what's your application for this? I guess the same basic idea that everyone else has for it: bringing additional systems up and down dynamically to control scalability and reliability vs. cost of having many machines running at once. I understand it is possible to restart the servers one at a time to change the server list without a full stop, but if we end up bundling this in some open source framework for people to use in the wild, the least manual interaction and procedural maintenance the best. Having ZooKeeper clients learning about the server list dynamically will help a lot in this scenario too. -- Gustavo Niemeyer http://niemeyer.net