You are viewing a plain text version of this content. The canonical link for it is here.

Posted to hdfs-dev@hadoop.apache.org by "Harsh J (JIRA)" <ji...@apache.org> on 2014/02/03 11:40:09 UTC

[jira] [Resolved] (HDFS-160) namenode fails to run on ppc

     [ https://issues.apache.org/jira/browse/HDFS-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Harsh J resolved HDFS-160.
--------------------------

    Resolution: Cannot Reproduce

This has likely gone stale now, and no similar reports have been received (PPC may be the reason?) - closing this one out as Cannot Reproduce.

> namenode fails to run on ppc
> ----------------------------
>
>                 Key: HDFS-160
>                 URL: https://issues.apache.org/jira/browse/HDFS-160
>             Project: Hadoop HDFS
>          Issue Type: Bug
>         Environment: PowerPC using Fedora 9 (all updates) and gcj-1.5.0.0
>            Reporter: Fabian Deutsch
>            Priority: Minor
>         Attachments: build.log, hadoop-env.sh, hadoop-site.xml, java.hprof.txt, jdb-namenode-QUIT.log, netstat.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 was sent by Atlassian JIRA
(v6.1.5#6160)