[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Patrick Hunt updated ZOOKEEPER-287:
-----------------------------------

    Fix Version/s: 3.2.0
     Release Note: Marking as 3.2 -- we should resolve or close this as 
unreproduceable.

> high cpu utilization caused by nioserver factory thread
> -------------------------------------------------------
>
>                 Key: ZOOKEEPER-287
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-287
>             Project: Zookeeper
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 3.0.1
>         Environment: Linux 2.6.9-67.ELsmp #1 SMP Wed Nov 7 13:58:04 EST 2007 
> i686 i686 i386 GNU/Linux
> the servers were running in vmware vms
> java version "1.6.0_06"
> Java(TM) SE Runtime Environment (build 1.6.0_06-b02)
> Java HotSpot(TM) Client VM (build 10.0-b22, mixed mode)
>            Reporter: Patrick Hunt
>            Priority: Critical
>             Fix For: 3.2.0
>
>
> a user reported that a long running server, part of a 2 server ensemble, 
> started using 100%cpu (1 server of the ensemble, the other was fine).
> mahadev tracked it down to a thread in the server running epoll in a tight 
> loop - the thread was the nio server factory thread that selects on client 
> fds.

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