[
https://issues.apache.org/jira/browse/MAPREDUCE-4495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13427434#comment-13427434
]
Robert Joseph Evans commented on MAPREDUCE-4495:
------------------------------------------------
@Josh,
Pleased to meet you :) feel free to call me Bobby, or really whatever you want.
I'll answer to most anything.
As I told Arun in IM. I am personally fine with going what ever rout the
community decides we should go in. Either big full blown oozie support or
small JobControl++. I would prefer to ultimately get to full oozie support as
I stated previously, but it is long road with many steps.
I would love to see this ultimately become a separate project, but I would also
love to see Map/Reduce, YARN, HDFS and Common split up into truly separate and
independent projects as well. However, right now, as was discussed on the
mailing list recently, it is not feasible. But I think we need to look at what
it would take to go in that direction. I am +1 for filing JIRAs and starting
to design and plan this feature. As part of the work though, I would suggest
that we include looking at what it would take to split this, and MR along with
it, into either one or two separate top level projects.
> Workflow Application Master in YARN
> -----------------------------------
>
> Key: MAPREDUCE-4495
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4495
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
> Affects Versions: 2.0.0-alpha
> Reporter: Bo Wang
> Assignee: Bo Wang
>
> It is useful to have a workflow application master, which will be capable of
> running a DAG of jobs. The workflow client submits a DAG request to the AM
> and then the AM will manage the life cycle of this application in terms of
> requesting the needed resources from the RM, and starting, monitoring and
> retrying the application's individual tasks.
> Compared to running Oozie with the current MapReduce Application Master,
> these are some of the advantages:
> - Less number of consumed resources, since only one application master will
> be spawned for the whole workflow.
> - Reuse of resources, since the same resources can be used by multiple
> consecutive jobs in the workflow (no need to request/wait for resources for
> every individual job from the central RM).
> - More optimization opportunities in terms of collective resource requests.
> - Optimization opportunities in terms of rewriting and composing jobs in the
> workflow (e.g. pushing down Mappers).
> - This Application Master can be reused/extended by higher systems like Pig
> and hive to provide an optimized way of running their workflows.
--
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
