[ https://issues.apache.org/jira/browse/OOZIE-2129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14310913#comment-14310913 ]
Jaydeep Vishwakarma commented on OOZIE-2129: -------------------------------------------- I have done the test in following scenarios: +Workflow with pig/java action+ - Kill Launcher mapper attempt - Restart node manager on which app-master is running - Kill launcher job - Follow up with workflow retry +Coord job +Direct workflow with pig/java action+ - Kill Launcher mapper attempt - Restart node manager on which app-master is running - Kill launcher job - Follow up with workflow retry - Kill launcher job - Follow up with coord action retry +Coord job +Subflow workflow with pig/java action+ - Kill Launcher mapper attempt - Restart node manager on which app-master is running - Kill launcher job - Follow up with workflow retry - Kill launcher job - Follow up with coord action retry > 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)