Return-Path: X-Original-To: apmail-zookeeper-user-archive@www.apache.org Delivered-To: apmail-zookeeper-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9DAF3E88D for ; Wed, 29 May 2013 12:32:16 +0000 (UTC) Received: (qmail 90841 invoked by uid 500); 29 May 2013 12:32:16 -0000 Delivered-To: apmail-zookeeper-user-archive@zookeeper.apache.org Received: (qmail 90220 invoked by uid 500); 29 May 2013 12:32:09 -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 90152 invoked by uid 99); 29 May 2013 12:32:07 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 May 2013 12:32:07 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of hbkrichards@gmail.com designates 209.85.192.181 as permitted sender) Received: from [209.85.192.181] (HELO mail-pd0-f181.google.com) (209.85.192.181) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 May 2013 12:32:01 +0000 Received: by mail-pd0-f181.google.com with SMTP id bv13so6952413pdb.40 for ; Wed, 29 May 2013 05:31:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=I2dI5mk9oJKuSBTmf7m5Wi753G7zPj/dBl42oi6Bo8I=; b=BQfPCl4Wnpml3JtprjKf+5oatK3DE8hesbMEer6TRl/mSclTJWjdLqD59x8v8w6jc8 WHFmKrTfe4LYpHAydXuFEeZ39efGMJSU8vwRV0TrYnlP3lKmkqXe5mWvuzQHf7GpLVjh PgX8mFXZZgWi/FKfQaBJIZP94pHGtqTxL3WtJ8OqFJePruL5PkDNjFFdtaDnAJ8Dywbt YnlYJk2Z7JNS2On+kLym8iK7pktKGGwN7K5+YGSbItVpkKNbeUwPsYcm/z+DflG3BlkU +g4BA6rMUEn98YrJTNKF2HJBBRWrDCKR+hTJBbo6H+Mlk2u2+uF+KD5Cj2OlmADwwJOl jKHA== MIME-Version: 1.0 X-Received: by 10.66.189.130 with SMTP id gi2mr3220957pac.89.1369830700312; Wed, 29 May 2013 05:31:40 -0700 (PDT) Received: by 10.66.219.137 with HTTP; Wed, 29 May 2013 05:31:40 -0700 (PDT) In-Reply-To: References: Date: Wed, 29 May 2013 18:01:40 +0530 Message-ID: Subject: Re: Clarification regarding maxClientCnxns parameter From: Richards Peter To: user@zookeeper.apache.org Content-Type: multipart/alternative; boundary=047d7bf0d4124b702704ddda90e9 X-Virus-Checked: Checked by ClamAV on apache.org --047d7bf0d4124b702704ddda90e9 Content-Type: text/plain; charset=ISO-8859-1 Hi all, Thanks for your replies. I will try to describe my setting in very simple terms. Assume that I have n machines running m number of JVMs each. Each JVM would connect to zookeeper cluster(having 3 servers currently) to maintain some state information. In this case would you recommend me to restrict maxClientCnxns to m? Initially I was thinking that zookeeper cluster is keeping a kind of state replica in all the machines. But when I read about the description of maxClientCnxns, I felt that it is not replica which is stored in zookeeper. Each client connection could go to a different zookeeper server. So I wanted to confirm whether the clients would connect in a load balanced fashion. Since clients connect randomly to any server, would it lead to increased loads on some servers than the others? Thanks, Richards. --047d7bf0d4124b702704ddda90e9--