Return-Path: Delivered-To: apmail-hadoop-zookeeper-user-archive@minotaur.apache.org Received: (qmail 478 invoked from network); 26 Feb 2009 18:24:50 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 26 Feb 2009 18:24:50 -0000 Received: (qmail 22399 invoked by uid 500); 26 Feb 2009 18:24:49 -0000 Delivered-To: apmail-hadoop-zookeeper-user-archive@hadoop.apache.org Received: (qmail 22325 invoked by uid 500); 26 Feb 2009 18:24:49 -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 22297 invoked by uid 99); 26 Feb 2009 18:24:49 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Feb 2009 10:24:49 -0800 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 beeblezap@gmail.com designates 209.85.198.229 as permitted sender) Received: from [209.85.198.229] (HELO rv-out-0506.google.com) (209.85.198.229) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Feb 2009 18:24:41 +0000 Received: by rv-out-0506.google.com with SMTP id k40so611329rvb.29 for ; Thu, 26 Feb 2009 10:24:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=rwF0g3lOwTxxa7PIj8ts4r1EdDL/bRciPPXZw38SRaE=; b=hpfzA2+7IraTp0KmFCFycWPW38or5FJFsRp8DE0Jq78eZpOAhFdAWD6ZHSFmIl9ift vkUp1AzQu4KzfGgPNxQURzBmQVMrOnGdQ9ko4YKym6GRZweBEX9Pn/c9DfhEOHSLFbFB J5YerjWhYRhlJ8R4RbAKj6lcLabPR3lSeQVWk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=bjwvZnlknZq44hAHLoMzdN9AHcEUkt9eAV4FBqVtL3WqmrnNoxkgDNnY2FxnZaNvvL sVnDciPlYfbHpBZYsS2BG4b5eDSqJUQyC5hksHxRK93/8LcTclllhRZ9Z4/Ttag6IEAG fof0RevUeAixazVqMmvkd1hV5SxVHawbLyQ7w= MIME-Version: 1.0 Received: by 10.140.157.1 with SMTP id f1mr758021rve.196.1235672660351; Thu, 26 Feb 2009 10:24:20 -0800 (PST) Date: Thu, 26 Feb 2009 10:24:20 -0800 Message-ID: Subject: Anyone using Zookeeper in AWS (Amazon Cloud)? From: bebble zap 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 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