Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Plain View
Zookeeper >> mail # user >> Clarification regarding maxClientCnxns parameter


+
Richards Peter 2013-05-28, 07:41
+
Flavio Junqueira 2013-05-29, 09:52
Copy link to this message
-
Re: Clarification regarding maxClientCnxns parameter
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.
+
Thawan Kooburat 2013-05-31, 02:01
+
Richards Peter 2013-05-31, 05:16
+
German Blanco 2013-05-29, 09:46
+
Richards Peter 2013-05-29, 09:27
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB