[
https://issues.apache.org/jira/browse/MAPREDUCE-4857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated MAPREDUCE-4857:
-------------------------------
Resolution: Not a Problem
Fix Version/s: (was: 1.0.4)
Target Version/s: (was: 1.0.4)
Status: Resolved (was: Patch Available)
Does not appear like we're planning any 1.0.x (vs. 1.1.x or 1.2.x) releases
anymore at this point, so am closing this out. Feel free to reopen though if I
have missed something.
> Fix 126 error during map/reduce phase
> -------------------------------------
>
> Key: MAPREDUCE-4857
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4857
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Affects Versions: 1.0.4
> Reporter: Fengdong Yu
> Attachments: MAPREDUCE-4857.patch
>
>
> There is rare happenings during map or reduce phase, but mostly in map phase,
> the Exception messages:
> java.lang.Throwable: Child Error
> at org.apache.hadoop.mapred.TaskRunner.run(TaskRunner.java:271)
> Caused by: java.io.IOException: Task process exit with nonzero status of 126.
> at org.apache.hadoop.mapred.TaskRunner.run(TaskRunner.java:258)
> and error logs are cleaned, so It's very hard to debug.
> but I compared DefaultTaskController.java with 0.22, they use "bash command"
> to start the job scritp, but 1.0.4 use "bash, "-c", command".
> I removed "-c", everything is ok, 126 error code never happen again.
> I read man document of bash, it indicates when fork a new thread with write
> command, another thread with "bash -c" also has a writable fd. so I think it
> could return 126 status occasionally.
> So, there is only one line fix for this issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
