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

Fabian Deutsch commented on HADOOP-3895:
----------------------------------------

During the following lines, java is hogging on the CPU:
{noformat}
[junit] 2008-08-06 15:12:41,355 INFO  ipc.Client 
(Client.java:setupIOstreams(190)) - Retrying connect to server: 
power.local/127.0.0.1:44005. Already tried 1 time(s).
    [junit] 2008-08-06 15:13:44,390 INFO  ipc.Client 
(Client.java:setupIOstreams(190)) - Retrying connect to server: 
power.local/127.0.0.1:44005. Already tried 2 time(s).
    [junit] 2008-08-06 15:14:47,439 INFO  ipc.Client 
(Client.java:setupIOstreams(190)) - Retrying connect to server: 
power.local/127.0.0.1:44005. Already tried 3 time(s).
    [junit] 2008-08-06 15:15:50,225 INFO  ipc.Client 
(Client.java:setupIOstreams(190)) - Retrying connect to server: 
power.local/127.0.0.1:44005. Already tried 4 time(s).
    [junit] 2008-08-06 15:16:53,196 INFO  ipc.Client 
(Client.java:setupIOstreams(190)) - Retrying connect to server: 
power.local/127.0.0.1:44005. Already tried 5 time(s).
{noformat}

I also attached a log of netstat. Interesting might be, that there is only a 
process bound to port 44005 on an ipv6 address.

> 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: build.log, 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