hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "dhruba borthakur (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-6082) Elegant decommission of lighty loaded tasktrackers from a map-reduce cluster
Date Fri, 19 Jun 2009 06:25:07 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-6082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12721672#action_12721672
] 

dhruba borthakur commented on HADOOP-6082:
------------------------------------------

Also, we might not need any changes to the decommissioning feature because when a node is
decommissioned, currently running tasks are "killed" and not "failed", so they do increase
the probability of a job failure.

> Elegant decommission of lighty loaded tasktrackers from a map-reduce cluster
> ----------------------------------------------------------------------------
>
>                 Key: HADOOP-6082
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6082
>             Project: Hadoop Core
>          Issue Type: New Feature
>          Components: mapred
>            Reporter: dhruba borthakur
>            Assignee: Namit Jain
>
> There is a need to elegantly move some machines from one map-reduce cluster to another.
This JIRA is to discuss how to find lightly loaded tasktrackers that are candidates for decommissioning
and then to elegantly decommission them by waiting for existing tasks to finish.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message