[
https://issues.apache.org/jira/browse/OOZIE-1178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16490722#comment-16490722
]
Andras Piros commented on OOZIE-1178:
-------------------------------------
[~dbist13] not exactly. This JIRA is about having the whole workflow (all
applications) run on YARN in a single {{WorkflowAM}} ApplicationMaster, whereas
[*Oozie On YARN*|https://issues.apache.org/jira/browse/OOZIE-1770] was about
having one workflow application's launcher run on YARN as a {{LauncherAM}}
ApplicationMaster. I wouldn't close for that reason.
Another question can be if we really want to support something like that; in
the meanwhile we have workflow actions that are meant to run on one of the
Oozie servers (synchronous actions) that cannot be run directly on a YARN
NodeManager container in any case. [~gezapeti] what are your two cents?
> Workflow Application Master in YARN
> -----------------------------------
>
> Key: OOZIE-1178
> URL: https://issues.apache.org/jira/browse/OOZIE-1178
> Project: Oozie
> Issue Type: New Feature
> Reporter: Bo Wang
> Priority: Major
> Attachments: MAPREDUCE-4495-v1.1.patch, MAPREDUCE-4495-v1.patch,
> MapReduceWorkflowAM.pdf, yapp_proposal.txt
>
>
> 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 was sent by Atlassian JIRA
(v7.6.3#76005)
