[
https://issues.apache.org/jira/browse/OOZIE-2129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaydeep Vishwakarma updated OOZIE-2129:
---------------------------------------
Attachment: OOZIE-2129-v6.patch
# Removed :
{code}
+ } else {
+ launcherTag = action.getId();
+ }
{code}
# {{LauncherMain}} is in sharelib module. Is that fine to add dependency to use
the variable only? I have created local constant variable for now.
# Keeping value as {{"oozie.child.mapreduce.job.tags"}} , It will also indicate
that this config is for child job launched by launcher.
# Passing {{MAPRED_JOB_TAGS}} so that other tags which added by user will pass
to hive conf.
# Removed {writeJobIdFile(idFile, jobId)} and other related code.
#
{code}
+ arguments.add("mapreduce.job.tags=" +
actionConf.get("mapreduce.job.tags"));
{code}
I am calling method {{setYarntag}} during initializing configuration. So it is
fine. By this we will be able to pass user tags as well.
I have done one more change in {{LauncherMainHadoopUtils}}.
{code}
String tag = actionConf.get(CHILD_MAPREDUCE_JOB_TAGS);
{code}
Earlier it was {{String tag = actionConf.get(MAPREDUCE_JOB_TAGS);}}, It will
give only the tag which created by oozie.
> 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-2129-v1.patch,
> OOZIE-2129-v2.patch, OOZIE-2129-v3.patch, OOZIE-2129-v4.patch,
> OOZIE-2129-v5.patch, OOZIE-2129-v6.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)
