[
https://issues.apache.org/jira/browse/ZOOKEEPER-1030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13016801#comment-13016801
]
Hudson commented on ZOOKEEPER-1030:
-----------------------------------
Integrated in ZooKeeper-trunk #1146 (See
[https://hudson.apache.org/hudson/job/ZooKeeper-trunk/1146/])
ZOOKEEPER-1030: Increase default for maxClientCnxns (missed docs) (Todd
Lipcon via breed/mahadev/phunt)
ZOOKEEPER-1030: Increase default for maxClientCnxns (Todd Lipcon via
breed/mahadev/phunt)
> Increase default for maxClientCnxns
> -----------------------------------
>
> Key: ZOOKEEPER-1030
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1030
> Project: ZooKeeper
> Issue Type: Improvement
> Affects Versions: 3.2.2
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Priority: Trivial
> Fix For: 3.4.0
>
> Attachments: zk-1030.txt, zk-1030.txt
>
>
> The default for maxClientCnxns is 10, which is too low for many applications.
> For example, HBase users often run MR jobs where each task needs to use
> ZooKeeper to talk to HBase. This means that each slot on the tasktracker will
> have at least one ZK connection. With today's beefy machines, that's easily
> 20+ connections per node.
> I would suggest bumping the default to 60, which will still protect against
> runaway nodes (eg a leak in a tight loop) but won't impact MR jobs that need
> to talk to ZK.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
