[
https://issues.apache.org/jira/browse/OOZIE-1025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13551620#comment-13551620
]
Robert Kanter commented on OOZIE-1025:
--------------------------------------
I looked at that with [~cheolsoo] and you're right, when you run a job from Pig
it will try to kill it (I was wrong before). However, the shutdown hook
doesn't seem to get triggered when Oozie kills the pig launcher job. According
to the [javadoc for the shutdown
hook|http://docs.oracle.com/javase/6/docs/api/java/lang/Runtime.html#addShutdownHook(java.lang.Thread)]
it is possible for the shutdown hook not to get triggered when the JVM is
terminated externally (e.g. a SIGKILL). I'm not sure how the JobTracker kills
its jobs, but because the shutdown hook isn't getting triggered, I'd guess its
doing a SIGKILL or something similar.
I was talking with [~tucu00] about this, and he had another idea where once we
kill the pig launcher job, we could then have Oozie go through and kill any
still-running jobs that were launched by scooping up the launched job IDs from
the launcher (it prints them out once the Pig job(s) have finished). I looked
into this a bit, and unfortunately, that will require a bit of extra work
because if you kill the pig launcher job, it doesn't get a chance to write out
the launched job IDs (I'd guess for the same reason the shutdown hook isn't
getting triggered: the JT is violently killing it). We could do something
where the launcher job has another thread which keeps checking for the job IDs
that Pig launched and writes them out to a file as it sees new ones; then Oozie
would be able to pick up the IDs from that file even if the launcher job is
killed. I'm pretty sure a similar solution would work for other actions that
have this issue.
> Killing oozie job kills oozie launcher job alone in hadoop.
> -----------------------------------------------------------
>
> Key: OOZIE-1025
> URL: https://issues.apache.org/jira/browse/OOZIE-1025
> Project: Oozie
> Issue Type: Bug
> Environment: Centos-5.8,Hadoop 2.0.0-cdh4.0.1
> Reporter: PriyaSundararajan
>
> As per the release build version: 3.1.3-cdh4.0.1 killing oozie job using
> kill command kills the oozie launcher job alone in hadoop and all other jobs
> associated with that workflow is running till it gets complete.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
