Return-Path: Delivered-To: apmail-hadoop-zookeeper-user-archive@minotaur.apache.org Received: (qmail 85068 invoked from network); 26 Jul 2010 16:13:18 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 26 Jul 2010 16:13:18 -0000 Received: (qmail 30114 invoked by uid 500); 26 Jul 2010 16:13:18 -0000 Delivered-To: apmail-hadoop-zookeeper-user-archive@hadoop.apache.org Received: (qmail 29994 invoked by uid 500); 26 Jul 2010 16:13:17 -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 29986 invoked by uid 99); 26 Jul 2010 16:13:16 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 26 Jul 2010 16:13:16 +0000 X-ASF-Spam-Status: No, hits=0.7 required=10.0 tests=RCVD_IN_DNSWL_NONE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [69.147.107.20] (HELO mrout1-b.corp.re1.yahoo.com) (69.147.107.20) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 26 Jul 2010 16:13:10 +0000 Received: from SNV-EXBH01.ds.corp.yahoo.com (snv-exbh01.ds.corp.yahoo.com [207.126.227.249]) by mrout1-b.corp.re1.yahoo.com (8.13.8/8.13.8/y.out) with ESMTP id o6QGCYR7010189 for ; Mon, 26 Jul 2010 09:12:34 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; s=serpent; d=yahoo-inc.com; c=nofws; q=dns; h=received:user-agent:date:subject:from:to:message-id: thread-topic:thread-index:in-reply-to:mime-version:content-type: content-transfer-encoding:return-path:x-originalarrivaltime; b=JVE+h/gF9RxYCTVjz7SlX6ZupMcnvKnuBnXCUps9eJfP2zyvHU3jFrJc5JQI2QNO Received: from SNV-EXVS09.ds.corp.yahoo.com ([207.126.227.86]) by SNV-EXBH01.ds.corp.yahoo.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 26 Jul 2010 09:12:33 -0700 Received: from 10.72.168.138 ([10.72.168.138]) by SNV-EXVS09.ds.corp.yahoo.com ([207.126.227.84]) via Exchange Front-End Server snv-webmail.corp.yahoo.com ([207.126.227.60]) with Microsoft Exchange Server HTTP-DAV ; Mon, 26 Jul 2010 16:12:33 +0000 User-Agent: Microsoft-Entourage/12.24.0.100205 Date: Mon, 26 Jul 2010 09:12:31 -0700 Subject: Re: node symlinks From: Mahadev Konar To: Message-ID: Thread-Topic: node symlinks Thread-Index: Acss3VluPktANlKQ1UCkIhehOJnTsQ== In-Reply-To: <4C4B5DA4.9030401@vrijheid.net> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-OriginalArrivalTime: 26 Jul 2010 16:12:33.0973 (UTC) FILETIME=[5B342650:01CB2CDD] HI Maarteen, Can you elaborate on your use case of ZooKeeper? We currently don't have any symlinks feature in zookeeper. The only way to do it for you would be a client side hash/lookup table that buckets data to different zookeeper servers. Or you could also store this hash/lookup table in one of the zookeeper clusters. This lookup table can then be cached on the client side after reading it once from zookeeper servers. Thanks mahadev On 7/24/10 2:39 PM, "Maarten Koopmans" wrote: > Yes, I thought about Cassandra or Voldemort, but I need ZKs guarantees > as it will provide the file system hierarchy to a flat object store so I > need locking primitives and consistency. Doing that on top of Voldemort > will give me a scalable version of ZK, but just slower. Might as well > find a way to scale across ZK clusters. > > Also, I want to be able to add clusters as the number of nodes grows. > Note that the #nodes will grow with the #users of the system, so the > clusters can grow sequentially, hence the symlink idea. > > --Maarten > > On 07/24/2010 11:12 PM, Ted Dunning wrote: >> 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 Koopmanswrote: >> >>> 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 >>> >> >