[
https://issues.apache.org/jira/browse/OOZIE-2129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14313710#comment-14313710
]
Shwetha G S commented on OOZIE-2129:
------------------------------------
ActionStartXCommand:
{code}
+ } else if (wfJob.getParentId() != null) {
+ context.setVar(COORD_ACTION_TAG, wfJob.getParentId() + "@"
+ wfAction.getName());
+ }
{code}
If coord action id is not set and there is no parent, set it to workflow action
id. I know that it defaults to workflow action id in Java Action Executor, but
it won't work for non-java derived actions.
The changes for launcher are just in hadoop-2
(hadoop-utils-2/src/main/java/org/apache/oozie/action/hadoop/LauncherMainHadoopUtils.java).
We need to replicate the same for hadoop-3 as well. Instead, can we make only
one module for hadoop-utils which can be shared for both hadoop-2 and hadoop-3.
You can set oozie.hadoop-utils.version in main pom.xml for hadoop-2 and
hadoop-3 profiles to be the same
LauncherMainHadoopUtils.getChildYarnJobs():
String tag = actionConf.get("mapreduce.job.tags");
should read from child.mapreduce.job.tags
+System.out.println(childYarnJobs.size() + " Child yarn jobs are found");
Print all the child job ids?
Hive2Main:
I don't think we are passing the action conf to child jobs, so job tags might
not work
LauncherMapper.propagateConf():
Use loadActionConf()
> Duplicate child jobs per instance
> ---------------------------------
>
> Key: OOZIE-2129
> URL: https://issues.apache.org/jira/browse/OOZIE-2129
> Project: Oozie
> Issue Type: Bug
> Reporter: Shwetha G S
> Assignee: Jaydeep Vishwakarma
> Attachments: OOZIE-2129-v0.patch
>
>
> OOZIE-1722 ensures that child job is killed at launcher restart. But this
> doesn't work for java actions as the tag is not passed to the child job.
> In case of coord action rerun, new workflow is created and hence new tag. So,
> it doesn't ensure old child job is killed at launcher start
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
