[
https://issues.apache.org/jira/browse/HADOOP-3895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12619824#action_12619824
]
Steve Loughran commented on HADOOP-3895:
----------------------------------------
The last stack trace shows that main() is waiting for a response from the
server about filesystem versions; if it quits after this then it may be that
the versions of the different processes are inconsistent. Nothing else looks
busy
at java.lang.Object.wait(Native Method)
- waiting on <0x56d716d8> (a org.apache.hadoop.ipc.Client$Call)
at org.apache.hadoop.ipc.Client.call(Client.java:465)
- locked <0x56d716d8> (a org.apache.hadoop.ipc.Client$Call)
at org.apache.hadoop.ipc.RPC$Invoker.invoke(RPC.java:163)
at org.apache.hadoop.dfs.$Proxy0.getProtocolVersion(Unknown Source)
at org.apache.hadoop.ipc.RPC.getProxy(RPC.java:247)
at org.apache.hadoop.dfs.DFSClient.<init>(DFSClient.java:105)
at
org.apache.hadoop.dfs.DistributedFileSystem$RawDistributedFileSystem.initialize(DistributedFileSystem.java:67)
at
org.apache.hadoop.fs.FilterFileSystem.initialize(FilterFileSystem.java:57)
at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:160)
- locked <0x88f65668> (a java.lang.Class for
org.apache.hadoop.fs.FileSystem)
at org.apache.hadoop.fs.FileSystem.getNamed(FileSystem.java:119)
at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:91)
at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:144)
- locked <0x88f65668> (a java.lang.Class for
org.apache.hadoop.fs.FileSystem)
at org.apache.hadoop.fs.Path.getFileSystem(Path.java:159)
at org.apache.hadoop.fs.Trash.<init>(Trash.java:58)
at org.apache.hadoop.dfs.NameNode.init(NameNode.java:184)
at org.apache.hadoop.dfs.NameNode.<init>(NameNode.java:195)
at org.apache.hadoop.dfs.NameNode.main(NameNode.java:728)
> 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.
