Return-Path: Delivered-To: apmail-hadoop-zookeeper-user-archive@minotaur.apache.org Received: (qmail 73578 invoked from network); 24 Jul 2010 21:13:24 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 24 Jul 2010 21:13:24 -0000 Received: (qmail 4059 invoked by uid 500); 24 Jul 2010 21:13:24 -0000 Delivered-To: apmail-hadoop-zookeeper-user-archive@hadoop.apache.org Received: (qmail 4010 invoked by uid 500); 24 Jul 2010 21:13:24 -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 4002 invoked by uid 99); 24 Jul 2010 21:13:23 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 24 Jul 2010 21:13:23 +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 (athena.apache.org: domain of ted.dunning@gmail.com designates 209.85.216.169 as permitted sender) Received: from [209.85.216.169] (HELO mail-qy0-f169.google.com) (209.85.216.169) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 24 Jul 2010 21:13:18 +0000 Received: by qyk9 with SMTP id 9so1407314qyk.14 for ; Sat, 24 Jul 2010 14:12:58 -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=t11NHQLK+Jx/gcKUBsA4KENaMb7f12Dc1kKmGvjhuiI=; b=Bhw4Lo22CPZ1WXJAY1K+/cY/KEL0+ygS8wF9UY5Ro7/PUcjBM4taEN9EIMPTXhuOPB aELwLthjSMejzGDCPHvASxhQVBBMuRdlKgBC7MzxrXht2+14dzlqf/wE7TRC5Bnx/zrx Bk+a1rOr9h4nqoYJ9/VCW2wDZh1JoD4j7A1Uk= 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=TS0iptQs4HVtqHHlm/SkATrfwbe4AzLlKVLMcXoHbMyKbCYYGyDjg+fUy2OI7mzLus 5cUwESG71I9/63+JeDTgslNPEPgCzyAIPWSmk26IUq4C0EedD6Dp2hnQXp3tl41UjdB9 tUVeCv+KEvC8Njsg39L0fGJKe3rP5XVksw4Lg= Received: by 10.224.46.5 with SMTP id h5mr4317471qaf.378.1280005978079; Sat, 24 Jul 2010 14:12:58 -0700 (PDT) MIME-Version: 1.0 Received: by 10.224.3.7 with HTTP; Sat, 24 Jul 2010 14:12:38 -0700 (PDT) In-Reply-To: <4C4AF915.10902@vrijheid.net> References: <4C4AF915.10902@vrijheid.net> From: Ted Dunning Date: Sat, 24 Jul 2010 14:12:38 -0700 Message-ID: Subject: Re: node symlinks To: zookeeper-user@hadoop.apache.org Content-Type: multipart/alternative; boundary=0015175cdff8a24422048c289da1 --0015175cdff8a24422048c289da1 Content-Type: text/plain; charset=UTF-8 Depending on your application, it might be good to simply hash the node name to decide which ZK cluster to put it on. Also, a scalable key value store like Voldemort or Cassandra might be more appropriate for your application. Unless you need the hard-core guarantees of ZK, they can be better for large scale storage. On Sat, Jul 24, 2010 at 7:30 AM, Maarten Koopmans wrote: > Hi, > > I have a number of nodes that will grow larger than one cluster can hold, > so I am looking for a way to efficiently stack clusters. One way is to have > a zookeeper node "symlink" to another cluster. > > Has anybody ever done that and some tips, or alternative approaches? > Currently I use Scala, and traverse zookeeper trees by proper tail > recursion, so adapting the tail recursion to process "symlinks" would be my > approach. > > Bst, Maarten > --0015175cdff8a24422048c289da1--