[
https://issues.apache.org/jira/browse/OOZIE-2129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14341030#comment-14341030
]
Robert Kanter commented on OOZIE-2129:
--------------------------------------
Sorry for the late response. By the way, there’s a “preview” button so you can
verify your formatting before posting.
# Even though they’re not indexed, it should still be faster because times are
in order. Consider if there’s 1 million jobs going back 3 years. Our job only
started yesterday, so there’s no reason to look through all 1 million jobs;
only the smaller number that occurred today and yesterday.
# I know that many users run MR jobs from the Java action, but in general,
we’ve avoided adding any MR specific extras to that action; they belong in the
MR action. The Java action is designed for arbitrary Java tasks. For example,
we don’t load the Configuration or handle the delegation tokens for MR jobs in
the Java action. Like those, if the user wants to take advantage of this
feature in their Java action, they have to implement some code. In fact, we
already have {{LauncherMainHadoopUtils.killChildYarnJobs(actionConf);}} in
JavaMain, so if they launched their MR job using the prepared action conf, that
should work automatically.
# {quote}Even now also LauncherMapper does not pass tag to child jobs{quote}
Isn’t that exactly what the original OOZIE-2129 did? It kills launched jobs
via tags when starting the launcher job.
# thanks
# I’m not sure I understand what you mean here. I don’t see why we’re adding a
new file to pass info to launcher jobs, when we already have the action conf
file.
Backing up for a moment, why does this matter to coord action rerun? You
shouldn’t be able to rerun a coord action if the original coord action, and
therefore workflow, and therefore any launcher jobs in that workflow, are still
running.
> 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-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)
