[
https://issues.apache.org/jira/browse/OOZIE-2590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15366990#comment-15366990
]
Robert Kanter edited comment on OOZIE-2590 at 7/8/16 12:13 AM:
---------------------------------------------------------------
The patch implements the {{LauncherAM}} which has a lot of similar code to
{{LauncherMapper}}, but is cleaned up a bit and simplified a little. It's also
obviously an Application Master and not a Map Task.
The patch also modifies {{JavaActionExecutor}} to run the {{LauncherAM}} via
{{YarnClient}} instead of {{LauncherMapper}}.
The Launcher Job used to always succeed. The Launcher AM's status will be
whatever status is correct. So if an error occurs, the Launcher AM will show
that. I've also made it so that Oozie can fallback to reading the action data
if it can't find the Launcher AM when querying the RM; this wasn't a problem
with the MR Launcher because we'd check the JHS, but now we can't and we don't
have to require the ATS this way. Though I believe {{YarnClient}} will do that
automatically if enabled, so that will be done for free if it's there.
The scope of this JIRA is to just get the AM working. Hence, some limitations
for now:
- {{LauncherAM}} is currently hardcoded to run a Dummy Main "action" instead of
the configured action. This was useful for testing, and we'll remove it when
we start doing the sibling JIRAs to update the actions.
- There's a number of TODOs but we can figure these out later. I've named them
all {{TODO: OYA: <message>}} so they're easy to identify. We should continue
to use these for subsequent JIRAs (you can configure most IDEs to keep track of
these).
- There's a number of unit tests that are currently broken. I think that's
fine for now (we're on a feature branch) until we get more of OYA done.
was (Author: rkanter):
The patch implements the {{LauncherAM}} which has a lot of similar code to
{{LauncherMapper}}, but is cleaned up a bit and simplified a little. It's also
obviously an Application Master and not a Map Task.
The patch also modifies {{JavaActionExecutor}} to run the {{LauncherAM}} via
{{YarnClient}} instead of {{LauncherMapper}}.
The scope of this JIRA is to just get the AM working. Hence, some limitations
for now:
- {{LauncherAM}} is currently hardcoded to run a Dummy Main "action" instead of
the configured action. This was useful for testing, and we'll remove it when
we start doing the sibling JIRAs to update the actions.
- There's a number of TODOs but we can figure these out later. I've named them
all {{TODO: OYA: <message>}} so they're easy to identify. We should continue
to use these for subsequent JIRAs (you can configure most IDEs to keep track of
these).
- There's a number of unit tests that are currently broken. I think that's
fine for now (we're on a feature branch) until we get more of OYA done.
> OYA: Create basic Oozie Launcher Application Master
> ---------------------------------------------------
>
> Key: OOZIE-2590
> URL: https://issues.apache.org/jira/browse/OOZIE-2590
> Project: Oozie
> Issue Type: Sub-task
> Affects Versions: oya
> Reporter: Robert Kanter
> Assignee: Robert Kanter
> Fix For: oya
>
> Attachments: OOZIE-2590.001.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
