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 "Leitao Guo (JIRA)" <ji...@apache.org> on 2011/03/01 08:09:37 UTC

[jira] Commented: (MAPREDUCE-279) Map-Reduce 2.0

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

Leitao Guo commented on MAPREDUCE-279:
--------------------------------------

@Arun
I also suspect the assumption that the AM has a basic idea about resource requirements. For example in hive scenario, how does AM know the requirements for resources when facing all kinds of query requests?

At the same time, if AM finds the request for resources is not enough for the application, will it re-request more resources or just fail?

> Map-Reduce 2.0
> --------------
>
>                 Key: MAPREDUCE-279
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-279
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: jobtracker, tasktracker
>            Reporter: Arun C Murthy
>            Assignee: Arun C Murthy
>             Fix For: 0.23.0
>
>
> Re-factor MapReduce into a generic resource scheduler and a per-job, user-defined component that manages the application execution. 

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira