[ 
https://issues.apache.org/jira/browse/HADOOP-3895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12619918#action_12619918
 ] 

Raghu Angadi commented on HADOOP-3895:
--------------------------------------

This mostly not because of mismatch since this is running inside the NameNode 
it wants to contact. Output of '-QUIT' seems to show that RPC server in 
NameNode is stuck in side Seletctor, which is unusual. We could take thread 
stacks multiple times with 'jstack'. Do unit tests under core/io and core/net 
pass?

{noformat}
"IPC Server listener on 9000" daemon prio=10 tid=0x1006d570 nid=0x8d5 runnable 
[0x8e3c2000..0x8e3c2ae0]
   java.lang.Thread.State: RUNNABLE
        at java.util.HashMap.keySet(HashMap.java:886)
        at java.util.HashSet.iterator(HashSet.java:170)
        at sun.nio.ch.SelectorImpl.processDeregisterQueue(SelectorImpl.java:145)
        - locked <0x56d679d8> (a java.util.HashSet)
        at sun.nio.ch.EPollSelectorImpl.doSelect(EPollSelectorImpl.java:87)
        at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:87)
        - locked <0x56d61c20> (a sun.nio.ch.Util$1)
        - locked <0x56d61c30> (a java.util.Collections$UnmodifiableSet)
        - locked <0x56d61be0> (a sun.nio.ch.EPollSelectorImpl)
        at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:98)
        at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:102)
        at org.apache.hadoop.ipc.Server$Listener.run(Server.java:253)
{noformat}


> namenode fails to run on ppc
> ----------------------------
>
>                 Key: HADOOP-3895
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3895
>             Project: Hadoop Core
>          Issue Type: Bug
>    Affects Versions: 0.17.1
>         Environment: PowerPC using Fedora 9 (all updates) and gcj-1.5.0.0
>            Reporter: Fabian Deutsch
>            Priority: Minor
>         Attachments: hadoop-env.sh, hadoop-site.xml, java.hprof.txt, 
> jdb-namenode-QUIT.log
>
>
> Hadoop starts, but eats 100% CPU. Data- and Secondarynamenodes can not 
> connect. No jobs were run, just trying to start the daemon. using 
> bin/start-dfs.sh.
> Using the same simple configuration on an x86-arch - also using Fedora 9 and 
> gcj-1.5.0.0 - works perfectly.

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