[ 
https://issues.apache.org/jira/browse/HIVE-16136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prasanth Jayachandran updated HIVE-16136:
-----------------------------------------
    Description: 
Sometime daemons can get killed by YARN's pmem monitor which issue a kill 
followed by kill -9 after 250ms. This is really a short duration to collect 
anything useful. 
There is no clean way to trap SIGKILL in java.  
One option is to increase the time between kill and kill -9 in YARN and during 
that time we can have a shutdown hook handler to collect all diagnostics 
information like heapdump, jstack, jmx output etc. in a non-container directory.

  was:Sometime daemons can get killed by YARN's pmem monitor which issue a kill 
followed by kill -9 after 250ms. This is really a short duration to collect 
anything useful. One option is to optionally trap SIGKILL requests and collect 
all diagnostics information like heapdump, jstack, jmx output etc. in a 
non-container directory.


> LLAP: Before SIGKILL and collect diagnostic information before daemon goes 
> down
> -------------------------------------------------------------------------------
>
>                 Key: HIVE-16136
>                 URL: https://issues.apache.org/jira/browse/HIVE-16136
>             Project: Hive
>          Issue Type: Bug
>          Components: llap
>    Affects Versions: 2.2.0
>            Reporter: Prasanth Jayachandran
>            Assignee: Prasanth Jayachandran
>
> Sometime daemons can get killed by YARN's pmem monitor which issue a kill 
> followed by kill -9 after 250ms. This is really a short duration to collect 
> anything useful. 
> There is no clean way to trap SIGKILL in java.  
> One option is to increase the time between kill and kill -9 in YARN and 
> during that time we can have a shutdown hook handler to collect all 
> diagnostics information like heapdump, jstack, jmx output etc. in a 
> non-container directory.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to