[
https://issues.apache.org/jira/browse/PIG-4921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15319414#comment-15319414
]
Rohini Palaniswamy commented on PIG-4921:
-----------------------------------------
bq. in case of Oozie interruption, Pig call HangingJobKiller; In case of other
interruption, Pig call TezSessionManager.shutdown
In case of Oozie interruption, Pig will call kill directly and
HangingJobKiller(mapreduce)/TezSessionManager.shutdown will also be invoked as
part of shutdown hook. In commandline, only
HangingJobKiller(mapreduce)/TezSessionManager.shutdown is called. This is
required because with launcher is killed, enough time is not given for the
shutdown hook to execute before the container is shot down with SIGTERM (kill
-9). In case of command line, when user does Ctrl+C shutdown hook has all the
time to execute. Also there is no InterruptedException as no one interrupts the
Thread like in launcher.
> Kill running jobs on InterruptedException
> -----------------------------------------
>
> Key: PIG-4921
> URL: https://issues.apache.org/jira/browse/PIG-4921
> Project: Pig
> Issue Type: Bug
> Reporter: Rohini Palaniswamy
> Assignee: Rohini Palaniswamy
> Fix For: 0.17.0
>
> Attachments: PIG-4921-1.patch, PIG-4921-2.patch, PIG-4921-3.patch
>
>
> Shutdown hook kills running jobs, but when running in Oozie launcher
> sometimes NodeManager can issue a SIGKILL after AM unregisters and before
> shutdown hook gets to execute causing orphaned jobs that continue to run. So
> it is better to kill when we see the InterruptedException.
> Added additional System.err logging to code in shutdown hooks as
> LogManager.shutdown() is called by mapreduce AM (Oozie launcher job is
> mapreduce) and log4j logging does not appear anymore.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
