You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Marcus Herou (JIRA)" <ji...@apache.org> on 2009/03/16 20:57:50 UTC
[jira] Issue Comment Edited: (HADOOP-4964) Task process exit with
nonzero status of 134.
[ https://issues.apache.org/jira/browse/HADOOP-4964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12682435#action_12682435 ]
Marcus Herou edited comment on HADOOP-4964 at 3/16/09 12:57 PM:
----------------------------------------------------------------
Confirmed, happens all the time at least a few hundred times a day.
We use Hadoop-0.18.3
was (Author: marcusherou):
Confirmed
> Task process exit with nonzero status of 134.
> -----------------------------------------------------
>
> Key: HADOOP-4964
> URL: https://issues.apache.org/jira/browse/HADOOP-4964
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.19.0
> Environment: Linux OS, 1 Namenode, 5 Datanode
> Reporter: sha feng
> Priority: Minor
>
> During fetcher2 stage, i got these errors on all datanodes.
> java.io.IOException: Task process exit with nonzero status of 134.
> at org.apache.hadoop.mapred.TaskRunner.run(TaskRunner.java: 424)
> When fetching more than 1000000 urls, these errors occur.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.