[
https://issues.apache.org/jira/browse/MAPREDUCE-3473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13158611#comment-13158611
]
Eli Collins commented on MAPREDUCE-3473:
----------------------------------------
The issue is that the single failure can be visible to the client. Eg when the
JobClient tries to get the tasklog from from a particular TT that's failed. The
reliability mechanism should be invisible to the client. See also
MAPREDUCE-2960 (A single TT disk failure can cause the job to fail). To see
what I'm talking about run a job in a loop and then fail one of the disks on
one of the TTs, some percentage of the time this single failure on a single TT
can cause the entire job to fail.
> Task failures shouldn't result in Job failures
> -----------------------------------------------
>
> Key: MAPREDUCE-3473
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3473
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: tasktracker
> Affects Versions: 0.20.205.0, 0.23.0
> Reporter: Eli Collins
>
> Currently some task failures may result in job failures. Eg a local TT disk
> failure seen in TaskLauncher#run, TaskRunner#run, MapTask#run is visible to
> and can hang the JobClient, causing the job to fail. Job execution should
> always be able to survive a task failure if there are sufficient resources.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
