You are viewing a plain text version of this content. The canonical link for it is here.

Posted to mapreduce-issues@hadoop.apache.org by "Harsh J (JIRA)" <ji...@apache.org> on 2013/07/14 04:06:48 UTC

[jira] [Commented] (MAPREDUCE-5381) Support graceful decommission of tasktracker

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

Harsh J commented on MAPREDUCE-5381:
------------------------------------

Does the NM in YARN already have this feature? If not, that should be covered first, before MR1 is enhanced.
                
> 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
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira