[
https://issues.apache.org/jira/browse/MAPREDUCE-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13048465#comment-13048465
]
Tom White commented on MAPREDUCE-279:
-------------------------------------
{quote}
Both 'classic' and 'nextgen' MR use the same 'runtime' i.e. MapTask,ReduceTask,
shuffle etc. which is what is currently under 'mr-client'. I'm happy to
brainstorm on a better name for it... how about 'mr-runtime'?
{quote}
I think 'mr-runtime', or just 'runtime' given that the context is MapReduce,
would be fine. I guess that there would be a 'classic' submodule to contain
JobTracker, TaskTracker etc, that currently aren't in any MR-279 Maven modules.
bq. Yep, it would be nice to completely mavenize and I strongly believe it
should be our goal.
+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
>
> Attachments: MR-279.patch, MR-279.patch, MR-279.sh,
> MR-279_MR_files_to_move.txt, capacity-scheduler-dark-theme.png,
> multi-column-stable-sort-default-theme.png, yarn-state-machine.job.dot,
> yarn-state-machine.job.png, yarn-state-machine.task-attempt.dot,
> yarn-state-machine.task-attempt.png, yarn-state-machine.task.dot,
> yarn-state-machine.task.png
>
>
> 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
