[
https://issues.apache.org/jira/browse/MAPREDUCE-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12998977#comment-12998977
]
Arun C Murthy commented on MAPREDUCE-279:
-----------------------------------------
bq. +1 An easy way to achieve this here would be to put the resource manager
code and new MapReduce ApplicationMaster code into separate source trees under
mapreduce.
Agreed! We have done exactly that in the prototype and plan to continue
improving modularity.
bq. Going further, the work to separate out the API and libraries from the
implementation should help this effort too, since it will involve removing hard
dependencies on the jobtracker from the API classes
+1
> 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
