[
https://issues.apache.org/jira/browse/HDFS-1756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uma Maheswara Rao G moved HADOOP-7186 to HDFS-1756:
---------------------------------------------------
Component/s: (was: ipc)
(was: io)
name-node
Key: HDFS-1756 (was: HADOOP-7186)
Project: Hadoop HDFS (was: Hadoop Common)
> BackUpNameNode is using 100% CPU and not accepting any requests.
> -----------------------------------------------------------------
>
> Key: HDFS-1756
> URL: https://issues.apache.org/jira/browse/HDFS-1756
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: name-node
> Reporter: Uma Maheswara Rao G
>
> In our environment, after 3 days long run Backup NameNode is using 100% CPU
> and not accepting any calls.
> *Thread dump*
> "IPC Server Responder" daemon prio=10 tid=0x00007f86c41c6800 nid=0x3b2a
> runnable [0x00007f86ce579000]
> java.lang.Thread.State: RUNNABLE
> at sun.nio.ch.EPollArrayWrapper.epollWait(Native Method)
> at sun.nio.ch.EPollArrayWrapper.poll(EPollArrayWrapper.java:215)
> at sun.nio.ch.EPollSelectorImpl.doSelect(EPollSelectorImpl.java:65)
> at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:69)
> locked <0x00007f86d67e2a20> (a sun.nio.ch.Util$1)
> locked <0x00007f86d67e2a08> (a java.util.Collections$UnmodifiableSet)
> locked <0x00007f86d67e26a8> (a sun.nio.ch.EPollSelectorImpl)
> at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:80)
> at org.apache.hadoop.ipc.Server$Responder.run(Server.java:501)
> Looks like we are running into similar issue like this Jetty one.
> http://jira.codehaus.org/browse/JETTY-937
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
