hadoop-common-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sagar Naik <sn...@attributor.com>
Subject Re: sudden instability in 0.18.2
Date Wed, 28 Jan 2009 17:40:54 GMT
Pl check which nodes have these failures.

I guess the new tasktrackers/machines  are not configured correctly.
As a result, the map-task will die and the remaining map-tasks will be 
sucked onto these machines


-Sagar

David J. O'Dell wrote:
> We've been running 0.18.2 for over a month on an 8 node cluster.
> Last week we added 4 more nodes to the cluster and have experienced 2
> failures to the tasktrackers since then.
> The namenodes are running fine but all jobs submitted will die when
> submitted with this error on the tasktrackers.
>
> 2009-01-28 08:07:55,556 INFO org.apache.hadoop.mapred.TaskTracker:
> LaunchTaskAction: attempt_200901280756_0012_m_000074_2
> 2009-01-28 08:07:55,682 WARN org.apache.hadoop.mapred.TaskRunner:
> attempt_200901280756_0012_m_000074_2 Child Error
> java.io.IOException: Task process exit with nonzero status of 1.
>         at org.apache.hadoop.mapred.TaskRunner.runChild(TaskRunner.java:462)
>         at org.apache.hadoop.mapred.TaskRunner.run(TaskRunner.java:403)
>
> I tried running the tasktrackers in debug mode but the entries above are
> all that show up in the logs.
> As of now my cluster is down.
>
>   

Mime
View raw message