Return-Path: Delivered-To: apmail-zookeeper-user-archive@www.apache.org Received: (qmail 18205 invoked from network); 5 Dec 2010 17:48:16 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 5 Dec 2010 17:48:16 -0000 Received: (qmail 63562 invoked by uid 500); 5 Dec 2010 17:48:16 -0000 Delivered-To: apmail-zookeeper-user-archive@zookeeper.apache.org Received: (qmail 63520 invoked by uid 500); 5 Dec 2010 17:48:15 -0000 Mailing-List: contact user-help@zookeeper.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@zookeeper.apache.org Delivered-To: mailing list user@zookeeper.apache.org Received: (qmail 63512 invoked by uid 99); 5 Dec 2010 17:48:15 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 05 Dec 2010 17:48:15 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of dlc@chiba.halibut.com designates 204.238.213.130 as permitted sender) Received: from [204.238.213.130] (HELO chiba.halibut.com) (204.238.213.130) by apache.org (qpsmtpd/0.29) with SMTP; Sun, 05 Dec 2010 17:48:09 +0000 Received: (qmail 14596 invoked by uid 10174); 5 Dec 2010 17:47:48 -0000 Date: Sun, 5 Dec 2010 09:47:48 -0800 From: David Carmean To: ZK Users Subject: [newb] cross-WAN ZK use? Message-ID: <20101205094748.P1527@halibut.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i Greetings, I've been reading about ZK (and Hedwig) off and on for a few days, and I have a small application where ZK might be useful, but there is some doubt. My present app has very low performance requirements; I'm looking to maintain no more than a couple of thousand tiny znodes as configuration items and coordination bits for a monitoring application. I'm experimenting with cross-site failover capability for various tiers of this application. One of the requirements, however, is to be robust against a complete outage of any one datacenter (client has been burned by such an outage recently...) Is it possible to turn some knobs that would relax the latency requirements in the ensemble voting process in return for giving up performance? I really don't need more than a few tens of writes per second for this app. Thanks.