Mailing-List: contact user-help@zookeeper.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@zookeeper.apache.org
Received-SPF: pass (athena.apache.org: domain of
 german.blanco.blanco@gmail.com designates 209.85.223.172 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CANMELZvdpt1k50a94z5-ZhsEmH30sGr+iPZbe7wo8PNjqZh_kQ@mail.gmail.com>
References: 
 <CANMELZvdpt1k50a94z5-ZhsEmH30sGr+iPZbe7wo8PNjqZh_kQ@mail.gmail.com>
Date: Wed, 29 May 2013 11:46:10 +0200
Message-ID: 
 <CAEH-zfpmeaK=hbS7R8qsMT2Dw53rfSNK-K=kdjxk9uNULovk5A@mail.gmail.com>
Subject: Re: Clarification regarding maxClientCnxns parameter
From: German Blanco <german.blanco.blanco@gmail.com>
To: user@zookeeper.apache.org
Content-Type: multipart/alternative; boundary=20cf303bff72746d1e04ddd8407f

--20cf303bff72746d1e04ddd8407f
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hello Richards Peter,
There is no load balancing, however clients may specify a list of servers
in their connection string.
The client library connects to any of the servers in the list and if there
is a failure it will try an alternative server of the list.
I recently posted an explanation to a similar question:
http://mail-archives.apache.org/mod_mbox/zookeeper-user/201305.mbox/browser
The answer didn't apply to that question, but maybe it applies to yours
better.
The restriction is per-server. My guess is that the reason for this is
because these kinds of resources (i.e. socket connections or file
descriptors) are limited per-server, and the best way to control that the
consumption of these resources by the ZooKeeper server doesn't disturb the
rest of the processes is to limit it using the same scope (per-server).
I haven't tested it, but I am quite confident that connections made from
different virtual IP's will be treated as different origin IP, and
connections made from the same virtual IP will be treated as the same
origin IP. As far as I know there will be no way for the ZooKeeper server
to tell if this is a virtual IP or not.
I hope this helps.
Regards,
Germ=E1n Blanco.


On Tue, May 28, 2013 at 9:41 AM, Richards Peter <hbkrichards@gmail.com>wrot=
e:

> Hi,
>
> I am new to zookeeper. I am using twitter's open source CEP project calle=
d
> storm. It uses zookeeper to store the state information. It is used
> internally by storm and our project is not using zookeeper to store any
> information. Few days back we had an issue in our setup. We debugged the
> issue and found that we had not increased the value of maxClientCnxns in
> the zoo.cfg file to meet our requirements. When we increased this value
> everything worked fine. I have a query related to the explanation of this
> parameter in
>
> http://zookeeper.apache.org/doc/r3.3.3/zookeeperAdmin.html#sc_advancedCon=
figuration
>
> The documentation says that, this is the max number of concurrent client
> connections that can be made from a single IP address to a single member =
of
> zookeeper ensemble. I would like to know whether clients connect to
> different machines in the ensemble for each connection. I mean is there a
> kind of load balancing taking place when a client tries to make connectio=
n
> to zookeeper ensemble. Why is there a restriction on per-zookeeper-server
> basis?
>
> I would also like to know whether virtual IPs are treated as different IP=
s
> by zookeeper. Will I be able to check this in some log file of zookeeper?
>
> Thanks,
> Richards Peter.
>

--20cf303bff72746d1e04ddd8407f--