You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Lars George (JIRA)" <ji...@apache.org> on 2010/09/30 10:54:32 UTC
[jira] Commented: (ZOOKEEPER-883) Idle cluster increasingly
consumes CPU resources
[ https://issues.apache.org/jira/browse/ZOOKEEPER-883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12916413#action_12916413 ]
Lars George commented on ZOOKEEPER-883:
---------------------------------------
Here is the config, which is a modified CDH3 version, pretty much standard:
{code}
# The number of milliseconds of each tick
tickTime=2000
# The number of ticks that the initial
# synchronization phase can take
initLimit=10
# The number of ticks that can pass between
# sending a request and getting an acknowledgement
syncLimit=5
# the directory where the snapshot is stored.
dataDir=/var/zookeeper
# the port at which the clients will connect
clientPort=2181
server.0=hadoop-primary.i.foobar.com:2888:3888
server.1=hadoop-a.i.foobar.com:2888:3888
server.2=hadoop-c.i.foobar.com:2888:3888
{code}
> Idle cluster increasingly consumes CPU resources
> ------------------------------------------------
>
> Key: ZOOKEEPER-883
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-883
> Project: Zookeeper
> Issue Type: Bug
> Components: server
> Affects Versions: 3.3.1
> Reporter: Lars George
> Attachments: Archive.zip
>
>
> Monitoring the ZooKeeper nodes by polling the various ports using Nagios' open port checks seems to cause a substantial raise of CPU being used by the ZooKeeper daemons. Over the course of a week an idle cluster grew from a baseline 2% to >10% CPU usage. Attached is a stack dump and logs showing the occupied threads. At the end the daemon starts failing on "too many open files" errors as all handles are used up.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.