Return-Path: Delivered-To: apmail-hadoop-zookeeper-user-archive@minotaur.apache.org Received: (qmail 24335 invoked from network); 26 Feb 2009 19:11:19 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 26 Feb 2009 19:11:19 -0000 Received: (qmail 7737 invoked by uid 500); 26 Feb 2009 19:11:19 -0000 Delivered-To: apmail-hadoop-zookeeper-user-archive@hadoop.apache.org Received: (qmail 7629 invoked by uid 500); 26 Feb 2009 19:11:19 -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 7618 invoked by uid 99); 26 Feb 2009 19:11:19 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Feb 2009 11:11:19 -0800 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [69.147.107.21] (HELO mrout2-b.corp.re1.yahoo.com) (69.147.107.21) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Feb 2009 19:11:09 +0000 Received: from SNV-EXPF01.ds.corp.yahoo.com (snv-expf01.ds.corp.yahoo.com [207.126.227.250]) by mrout2-b.corp.re1.yahoo.com (8.13.8/8.13.8/y.out) with ESMTP id n1QJADvp095570 for ; Thu, 26 Feb 2009 11:10:13 -0800 (PST) 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=hu7IasTq3d6ojzp63Yl36j/do9d1l4rF8662eIzfORePf3Ixda1bF51pEqdrB3gX Received: from SNV-EXVS09.ds.corp.yahoo.com ([207.126.227.87]) by SNV-EXPF01.ds.corp.yahoo.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 26 Feb 2009 11:10:13 -0800 Received: from 10.73.146.106 ([10.73.146.106]) by SNV-EXVS09.ds.corp.yahoo.com ([207.126.227.84]) via Exchange Front-End Server snv-webmail.corp.yahoo.com ([207.126.227.59]) with Microsoft Exchange Server HTTP-DAV ; Thu, 26 Feb 2009 19:10:12 +0000 User-Agent: Microsoft-Entourage/12.15.0.081119 Date: Thu, 26 Feb 2009 11:10:12 -0800 Subject: Re: Anyone using Zookeeper in AWS (Amazon Cloud)? From: Mahadev Konar To: Message-ID: Thread-Topic: Anyone using Zookeeper in AWS (Amazon Cloud)? Thread-Index: AcmYRdkkn9OrAfxSR0CLTAmnWpCRmw== In-Reply-To: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-OriginalArrivalTime: 26 Feb 2009 19:10:13.0211 (UTC) FILETIME=[D9DD8AB0:01C99845] X-Virus-Checked: Checked by ClamAV on apache.org Hi Greg, As for cross datacenters, we have tested zookeeper cross data centers and it works fine. The only thing is that you might have to tweak synclimit and tickTime to a little higher values for Zookeeper. http://hadoop.apache.org/zookeeper/docs/r3.1.0/zookeeperAdmin.html#sc_config uration provides documentation on these parameters. As for communication protocol within zookeeper servers, we currently use raw tcp sockets to send and receive data. I cannot estimate the time it would take the time for it to use https, but it wont be just a week of work for sure. Also, the client to zookeeper server is raw tcp again. We would certainly like to have security in Zookeeper. Currently, Hadoop Core is also working on getting security in place. We plan to have a similar security model as theirs (I think they are looking at kerberos -- not sure) . mahadev On 2/26/09 10:24 AM, "bebble zap" wrote: > We're thinking about using Zookeeper as our coordination service and > also for doing group membership in the Amazon Cloud. Currently our > applications are deployed in Amazon Cloud on multiple availability > zones (i.e. data centers), so this means that ZK nodes will be talking > across datacenters. I'm assuming that the additional latency from > going across datacenters shouldn't be too big of an issue. Also, we > are paranoid about security in the cloud, so we'd like to use https as > the communications protocol for Zookeeper -- not sure if this is a > trivial thing to do or not. Wondering if anyone's already doing this > today or whether Zookeeper is not the right solution given our > environment currently. > > Thanks > Greg