[
https://issues.apache.org/jira/browse/MAPREDUCE-3315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13245600#comment-13245600
]
Vinod Kumar Vavilapalli commented on MAPREDUCE-3315:
----------------------------------------------------
We have a hadoop-yarn/hadoop-yarn-applications/ module under which you can put
your framework (as a sibling to hadoop-yarn-applications-distributedshell/).
The example could go as a sub-module under yours.
Taking a step back, I think you should start with writing down the APIs:
(1) The client API for submission and getting the app-status.
(2) The task API: which the users can override and provide their own impl.
Advanced: (3) The master API: as to how to order the tasks (a queue?) etc.
> Master-Worker Application on YARN
> ---------------------------------
>
> Key: MAPREDUCE-3315
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3315
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
> Reporter: Sharad Agarwal
> Assignee: Sharad Agarwal
> Fix For: 0.24.0
>
> Attachments: MAPREDUCE-3315.patch
>
>
> Currently master worker scenarios are forced fit into Map-Reduce. Now with
> YARN, these can be first class and would benefit real/near realtime workloads
> and be more effective in using the cluster resources.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
