Return-Path: Delivered-To: apmail-hadoop-zookeeper-user-archive@minotaur.apache.org Received: (qmail 95098 invoked from network); 21 Jul 2010 17:40:45 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 21 Jul 2010 17:40:45 -0000 Received: (qmail 84460 invoked by uid 500); 21 Jul 2010 17:40:45 -0000 Delivered-To: apmail-hadoop-zookeeper-user-archive@hadoop.apache.org Received: (qmail 84420 invoked by uid 500); 21 Jul 2010 17:40:44 -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 84412 invoked by uid 99); 21 Jul 2010 17:40:44 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Jul 2010 17:40:44 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of ted.dunning@gmail.com designates 209.85.216.48 as permitted sender) Received: from [209.85.216.48] (HELO mail-qw0-f48.google.com) (209.85.216.48) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Jul 2010 17:40:36 +0000 Received: by mail-qw0-f48.google.com with SMTP id 7so3890407qwd.35 for ; Wed, 21 Jul 2010 10:40:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:content-type; bh=v9RbkfgAJmc9dmMj58MCKE5ZExfmxGF9ieXS1zGRpIw=; b=rRfppR62nVZ+e5RwJdcLX+R8p84YvfMOM4Uk2dQNLBXVXk8s8dTFDcccwJRVqaT3Pc 79OHd7Fy9bxpfHDCqSKGLtCpE6Ww/BGe0CxR+e8EJofHMFZWy/1+cTfGr0m0admkB139 3guIAObNc9ebmF4wUbBqj8G4FJFX3yXCw0lQE= 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=NVugLxVp9ThF5hAEEAPfQzUaaUUb73UmGjLsLlkmyOt5sICac40TMTnUSxdbMEug5S W3xdShEgCZVry82+gJ+PrX2ggzkHcxflQwun5U9D/lYP990TXJWHyMS0V6mb/GYMP0kq dFlUTMGuviKH5tbXgePCIWIiPxYJr6K0Sy+LA= Received: by 10.224.26.229 with SMTP id f37mr402322qac.12.1279734016219; Wed, 21 Jul 2010 10:40:16 -0700 (PDT) MIME-Version: 1.0 Received: by 10.224.3.7 with HTTP; Wed, 21 Jul 2010 10:39:56 -0700 (PDT) In-Reply-To: References: From: Ted Dunning Date: Wed, 21 Jul 2010 10:39:56 -0700 Message-ID: Subject: Re: Adding observers To: zookeeper-user@hadoop.apache.org Content-Type: multipart/alternative; boundary=00c09f8998bc719a89048be94b3f X-Virus-Checked: Checked by ClamAV on apache.org --00c09f8998bc719a89048be94b3f Content-Type: text/plain; charset=UTF-8 On Wed, Jul 21, 2010 at 10:30 AM, Avinash Lakshman < avinash.lakshman@gmail.com> wrote: > > (1) Is it possible to increase the number of observers in the cluster > dynamically? > Not quite, but practically speaking you can do as good as this. In general, pretty much any ZK configuration change can be done without service interruption by using a rolling restart. > (2) How many observers can I add given that I will seldom write into the > cluster but will have a lot of reads coming into the system? Can I run a > cluster with say 100 observers? > Others will give more authoritative answers, but I am pretty sure that the limitation on the number of observers is strictly related to write rate x number of observers. This is related to the fact that writes need to come from the current master. It isn't hard to imagine how to write a reflector that watches for all changes and writes these to a secondary cluster. That would essentially eliminate the limit on number of observers. Something like that may already be possible within the current system (I couldn't say since I haven't looked into observers that much). --00c09f8998bc719a89048be94b3f--