You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Srikanth Sundarrajan (JIRA)" <ji...@apache.org> on 2016/04/26 06:54:13 UTC

[jira] [Commented] (OOZIE-1770) Create Oozie Application Master for YARN

    [ https://issues.apache.org/jira/browse/OOZIE-1770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15257566#comment-15257566 ] 

Srikanth Sundarrajan commented on OOZIE-1770:
---------------------------------------------

Thanks [~rkanter] for summarizing the discussions. Here are some additional things to think about while considering an AM pool

1. Currently we have one external url per action to track the execution of the action and associated logs. With the Yarn app per action, this would continue to work cleanly. It might introduce avoidable overheads to use AM Pool if logs & action execution details have to be tracked per action
2. With AppMaster being the launcher, it might be trivilally simple to handle AM restarts and RM restarts/fail overs. With the AM pool, I am guessing we need to worry about AM failures and container failures


> 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: Bowen Zhang
>         Attachments: OozieYarnAM.pdf, Prelim OYA Scoping Doc 001.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)