[
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-v1.patch
[~shwethags]
1. All ActionExecutor extends JavaActionExecutor so no issue with it.
2. I just went through hadoop-3 profile. I am unable to even compile it, I can
see various issues with it. I will create the separate jira and fix the profile
and then i will have only single hadoop-utils. For now I am just doing copy
paste of it the same code.
3. Using child.mapreduce.job.tags in LauncherMainHadoopUtils.
4. printing application id as well.
5. Passing tag as --hiveconf in Hive2Main
> 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-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)
