[
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-v8.patch
Keeping {{writeJobIdFile}} method in {{MapReduceMain}} to write the job id.
It has been using in {{LauncherMapper}} for following code
{code}
// id swap
String newIdProp = System.getProperty(ACTION_PREFIX +
ACTION_DATA_NEW_ID);
if (newIdProp != null) {
File newId = new File(newIdProp);
if (newId.exists()) {
actionData.put(ACTION_DATA_NEW_ID,
getLocalFileContentStr(newId, "", -1));
}
}
{code}
Test cases are for same reason.
> 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-2129-v7.patch,
> OOZIE-2129-v8.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)
