Details
-
New Feature
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
Description
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.
Attachments
Attachments
Issue Links
- is related to
-
OOZIE-593 WF lite2 implementation with testcases
- In Progress
-
HIVE-1107 Generic parallel execution framework for Hive (and Pig, and ...)
- Open
- relates to
-
OOZIE-1770 Create Oozie Application Master for YARN
- Closed
-
PIG-1734 Pig needs a more efficient DAG execution
- Resolved