You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "ramkrishna.s.vasudevan (JIRA)" <ji...@apache.org> on 2011/05/19 12:48:47 UTC
[jira] [Created] (HADOOP-7304) BackUpNameNode is using 100% CPU and
not accepting any requests.
BackUpNameNode is using 100% CPU and not accepting any requests.
-----------------------------------------------------------------
Key: HADOOP-7304
URL: https://issues.apache.org/jira/browse/HADOOP-7304
Project: Hadoop Common
Issue Type: Bug
Components: ipc
Affects Versions: 0.21.0
Reporter: ramkrishna.s.vasudevan
Fix For: 0.20-append
In our environment, Backup NameNode is using 100% CPU and not accepting any calls in 3days long run.
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 same issue occurred in jetty also. 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
[jira] [Resolved] (HADOOP-7304) BackUpNameNode is using 100% CPU
and not accepting any requests.
Posted by "Uma Maheswara Rao G (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Uma Maheswara Rao G resolved HADOOP-7304.
-----------------------------------------
Resolution: Duplicate
> BackUpNameNode is using 100% CPU and not accepting any requests.
> -----------------------------------------------------------------
>
> Key: HADOOP-7304
> URL: https://issues.apache.org/jira/browse/HADOOP-7304
> Project: Hadoop Common
> Issue Type: Bug
> Components: ipc
> Affects Versions: 0.23.0
> Reporter: ramkrishna.s.vasudevan
>
> In our environment, Backup NameNode is using 100% CPU and not accepting any calls in 3days long run.
> 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 same issue occurred in jetty also. 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