Return-Path: Delivered-To: apmail-hadoop-zookeeper-user-archive@minotaur.apache.org Received: (qmail 13575 invoked from network); 27 Apr 2010 17:56:46 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 27 Apr 2010 17:56:46 -0000 Received: (qmail 20649 invoked by uid 500); 27 Apr 2010 17:56:46 -0000 Delivered-To: apmail-hadoop-zookeeper-user-archive@hadoop.apache.org Received: (qmail 20632 invoked by uid 500); 27 Apr 2010 17:56:46 -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 20624 invoked by uid 99); 27 Apr 2010 17:56:46 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Apr 2010 17:56:46 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of avinash.lakshman@gmail.com designates 74.125.83.176 as permitted sender) Received: from [74.125.83.176] (HELO mail-pv0-f176.google.com) (74.125.83.176) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Apr 2010 17:56:38 +0000 Received: by pvg6 with SMTP id 6so303493pvg.35 for ; Tue, 27 Apr 2010 10:56:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=ccbRYpPIIim1bd09yU3kolNX5dJelG8eMhmnF2m6yHA=; b=EExyyRnSoeLCvbGCH1jq9rjK+bPWxDVJiz2nHtBYEYkHzrckBopdZZHXTBzk1yNbjU 38NfyY7xIEemsfjGuJ8RMRthEsA0l49N1Bqg2GmK138UuxyBGQ8qZQEZuQqQifYpfqwN sIdY37vzBExSXz+8CsL+ZLi8Yuc/YQRrqTekI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=BpWhddRXWH9jmSX4akZUw7iqxUjybJmrau+Z8L10gyhlEvWOExRPye6u/rQ9mv4QMP g6yLSVNkwnktxJ5F3+BR8gsmS6Y+MdNbbwO/+9lUp6IcBESFMe7IMIW0zPN3Z7JBpIfV RGPjU2h6fiLxdTU9VuETtls0d3bpPotQ/EANE= MIME-Version: 1.0 Received: by 10.141.107.9 with SMTP id j9mr6387862rvm.177.1272390974093; Tue, 27 Apr 2010 10:56:14 -0700 (PDT) Received: by 10.231.161.207 with HTTP; Tue, 27 Apr 2010 10:56:13 -0700 (PDT) Date: Tue, 27 Apr 2010 10:56:13 -0700 Message-ID: Subject: Zookeeper client From: Avinash Lakshman To: zookeeper-user@hadoop.apache.org Content-Type: multipart/alternative; boundary=000e0cd1391a06b9e304853b9c86 X-Virus-Checked: Checked by ClamAV on apache.org --000e0cd1391a06b9e304853b9c86 Content-Type: text/plain; charset=ISO-8859-1 Let's assume I have 100 clients connecting to a cluster of 5 Zookeeper servers over time. On the client side I instantiate a ZooKeeper instance and use it whenever I need to read/write into ZK. Now I know I can pass in a connect string with the list of all servers that make up the ZK cluster. Does the ZK client automatically maintain liveness information and load balance my connections across the machines? How can I do this effectively? I basically want to spread the connections from the 100 clients to the 5 ZK instances effectively. Thanks Avinash --000e0cd1391a06b9e304853b9c86--