hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eli Collins (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-3473) A single task tracker failure shouldn't result in Job failure
Date Wed, 21 Dec 2011 18:59:31 GMT

     [ https://issues.apache.org/jira/browse/MAPREDUCE-3473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Eli Collins updated MAPREDUCE-3473:
-----------------------------------

    Summary: A single task tracker failure shouldn't result in Job failure   (was: Task failures
shouldn't result in Job failures )

@Subroto. Thanks for pinging. Users expect their jobs to complete even if a TT running one
of their jobs fails right? So we're clear on terminology, what I identified is that a single
TT failure can cause the job to fail. A job should be able to survive a single machine failure
right?
                
> A single task tracker failure shouldn't result in Job failure 
> --------------------------------------------------------------
>
>                 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

        

Mime
View raw message