hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mahadev konar (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-3473) Task failures shouldn't result in Job failures
Date Tue, 29 Nov 2011 19:19:40 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-3473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13159468#comment-13159468

Mahadev konar commented on MAPREDUCE-3473:

I think we do need the defaults to be 0. Changing it to anything else will be a regression.
As Sharad said, losing data should not come as a surprise to users.
> 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.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


View raw message