[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12916446#action_12916446
 ] 

Flavio Junqueira commented on ZOOKEEPER-883:
--------------------------------------------

I think this issue is related to ZOOKEEPER-880. It seems that the connections 
nagios creates start a RecvWorker and a SendWorker, and once they close, they 
kill RecvWorker but not SendWorker, so for every notification sent there is an 
orphan RecvWorker.

I see two options:

# Patch it so that it also kills the SendWorker instance;
# Decline connection requests from unknown servers.

I'm also curious to understand why you guys are monitoring the election port.

> 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.

Reply via email to