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 "Jeff Hammerbacher (JIRA)" <ji...@apache.org> on 2009/09/28 06:53:16 UTC

[jira] Commented: (MAPREDUCE-1044) Ability to automatically move machines from one MR compute cluster to another

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

Jeff Hammerbacher commented on MAPREDUCE-1044:
----------------------------------------------

Hey Dhruba,

Rather than moving nodes from MR cluster to another, couldn't you just grow/shrink the minimum allocation of a pool in the Fair Share scheduler? Inserting another daemon outside of the scope of the JT to perform this dynamic resource allocation while the JTs themselves are trying to perform resource allocation seems to be complicating things a bit.

Thanks,
Jeff

> Ability to automatically move machines from one MR compute cluster to another
> -----------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-1044
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1044
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>            Reporter: dhruba borthakur
>            Assignee: Dmytro Molkov
>
> We have multiple map-reduce clusters that provide different service and support levels for their users. We have seen that utilization of hardware resources are not optimized if we have a static partition of existing hardware resources into these separate MR clusters. It would be nice to have a automatic way to move nodes from one MR cluster to another based on load characteristics and configured policies. This JIRA will discuss some of the ideas and possible implementations of those ideas.

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