[
https://issues.apache.org/jira/browse/OOZIE-1770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15755533#comment-15755533
]
Peter Cseh commented on OOZIE-1770:
-----------------------------------
Thanks for taking the time to review this. It's a huge change, but a lot of the
patch is removing things that are not needed any more :)
We've tested with the workflow from OOZIE-1978. It contains 120 shell actions
in a bunch of forks. It took 25-30 mins to execute it with MR launchers and
around 6-8 mins with the new launcher. This was measured only a couple times on
one cluster, so it's not an exact thing, but I think it's reasonable to expect
to cut job submission time by 60-70% compared to an MR launcher. We have tested
with ubermode disabled, so it might be less with ubermode.
We're seeing a lot of single-action workflows which are taking less then a
minute, those can benefit from this change greatly.
> Create Oozie Application Master for YARN
> ----------------------------------------
>
> Key: OOZIE-1770
> URL: https://issues.apache.org/jira/browse/OOZIE-1770
> Project: Oozie
> Issue Type: New Feature
> Reporter: Bowen Zhang
> Assignee: Peter Cseh
> Attachments: OOZIE-1770-001.patch, OOZIE-1770-002.patch, OYA Scoping
> Doc 001.pdf, OozieYarnAM.pdf, Prelim OYA Scoping Doc 001.pdf, Prelim OYA
> Scoping Doc 002.pdf, Prelim OYA Scoping Doc 003.pdf, oya-rm-screenshot.jpg,
> oya.patch
>
>
> After the first release of oozie on hadoop 2, it will be good if users can
> set execution engine in oozie conf, be it YARN AM or traditional MR. We can
> target this for post oozie 4.1 release.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
