[
https://issues.apache.org/jira/browse/PIG-4921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15318938#comment-15318938
]
Rohini Palaniswamy commented on PIG-4921:
-----------------------------------------
bq. It kills active session but not idle sessions. Idle session will go away
when expire, so probably no big deal.
Yes. Also they will not be running any code as there is no DAG submitted to
them. So idle sessions are not a problem. The problem was active sessions as
many times the orphaned jobs interfered with job reruns.
bq. But when you say HangingJobKiller duplicates TezSessionManager.shutdown,
it's not true, TezSessionManager.shutdown does more than HangingJobKiller.
Yes. TezSessionManager.shutdown does all that HangingJobKiller does and more.
That is why getting rid of HangingJobKiller.
> 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)
