Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Duplicate
-
0.23.0
-
None
-
None
Description
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
Attachments
Issue Links
- duplicates
-
HADOOP-7191 BackUpNameNode is using 100% CPU and not accepting any requests.
- Resolved