[
https://issues.apache.org/jira/browse/MAPREDUCE-421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12750070#action_12750070
]
Christian Kunz commented on MAPREDUCE-421:
------------------------------------------
1) Tested by submitting 'mapred pipes' commands with incorrect parameters.
Obviously the patch does not impact correct pipes jobs, otherwise we would have
seen test failures.
2) I would interpret Amareshwari's '+1' as an indication that the tests failed
for unrelated reasons (unfortunately, cannot be verified, as the link to the
testReport no longer exists). That test fail for unrelated reasons is not
unusual -- it is my subjective impression that it happens often.
> mapred pipes might return exit code 0 even when failing
> -------------------------------------------------------
>
> Key: MAPREDUCE-421
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-421
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: pipes
> Reporter: Christian Kunz
> Assignee: Christian Kunz
> Fix For: 0.20.1
>
> Attachments: MAPREDUCE-421.patch
>
>
> up to hadoop 0.18.3 org.apache.hadoop.mapred.JobShell ensured that 'hadoop
> jar' returns non-zero exit code when the job fails.
> This is no longer true after moving this to org.apache.hadoop.util.RunJar.
> Pipes jobs submitted through cli never returned proper exit code.
> The main methods in org.apache.hadoop.util.RunJar. and
> org.apache.hadoop.mapred.pipes.Submitter should be modified to return an exit
> code similar to how org.apache.hadoop.mapred.JobShell did it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
