hadoop-mapreduce-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (MAPREDUCE-5381) Support graceful decommission of tasktracker
Date Mon, 09 Feb 2015 18:48:35 GMT

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

Vinod Kumar Vavilapalli resolved MAPREDUCE-5381.
    Resolution: Won't Fix

Hardly any development is happening in 1.x now. I am closing this in favor of YARN's YARN-914.
Please reopen if need be.

> Support graceful decommission of tasktracker
> --------------------------------------------
>                 Key: MAPREDUCE-5381
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5381
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: mrv1
>    Affects Versions: 1.2.0
>            Reporter: Luke Lu
>            Assignee: Binglin Chang
>         Attachments: MAPREDUCE-5381-graceful-decomm.v1.patch
> When TTs are decommissioned for non-fault reasons (capacity change etc.), it's desirable
to minimize the impact to running jobs.
> Currently if a TT is decommissioned, all running tasks on the TT need to be rescheduled
on other TTs. Further more, for finished map tasks, if their map output are not fetched by
the reducers of the job, these map tasks will need to be rerun as well.
> We propose to introduce a mechanism to optionally gracefully decommission a tasktracker.

This message was sent by Atlassian JIRA

View raw message