[
https://issues.apache.org/jira/browse/ZOOKEEPER-863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12906014#action_12906014
]
Stephen McCants commented on ZOOKEEPER-863:
-------------------------------------------
Removing the registered service after ZK had stopped running away, causes ZK to
return to using 100% of the CPU.
> Runaway thread - Zookeeper inside Eclipse
> -----------------------------------------
>
> Key: ZOOKEEPER-863
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-863
> Project: Zookeeper
> Issue Type: Bug
> Affects Versions: 3.3.0
> Environment: Linux; x86
> Reporter: Stephen McCants
> Priority: Critical
>
> I'm running Zookeeper inside an Eclipse application. When I launch the
> application from inside Eclipse I use the following arguments:
> -Dzoodiscovery.autoStart=true
> -Dzoodiscovery.flavor=zoodiscovery.flavor.centralized=localhost
> This causes the application to start its own ZooKeeper server inside the
> JVM/application. It immediately goes into a runaway state. The name of the
> runaway thread is "NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181". When I
> suspend this thread, the CPU usage returns to 0. Here is a stack trace from
> that thread when it is suspended:
> EPollArrayWrapper.epollWait(long, int, long, int) line: not available [native
> method]
> EPollArrayWrapper.poll(long) line: 215
> EPollSelectorImpl.doSelect(long) line: 77
> EPollSelectorImpl(SelectorImpl).lockAndDoSelect(long) line: 69
> EPollSelectorImpl(SelectorImpl).select(long) line: 80
> NIOServerCnxn$Factory.run() line: 232
> Any ideas what might be going wrong?
> Thanks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
