pig-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Dai (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PIG-4921) Kill running jobs on InterruptedException
Date Wed, 08 Jun 2016 07:38:20 GMT

    [ https://issues.apache.org/jira/browse/PIG-4921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15320189#comment-15320189
] 

Daniel Dai commented on PIG-4921:
---------------------------------

You mentioned TezSessionManager.shutdown is not effective in Oozie. If that happen, idle AM
will left behind. But I agree compare to dangling job, it is less a worry. +1 for PIG-4921-3.patch.

> 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)

Mime
View raw message