You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Ajit Kumar (JIRA)" <ji...@apache.org> on 2016/07/18 21:26:20 UTC
[jira] [Updated] (AMBARI-17776) HiveServer interactive stop should
wait for 30 second before sending kill -9
[ https://issues.apache.org/jira/browse/AMBARI-17776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ajit Kumar updated AMBARI-17776:
--------------------------------
Attachment: rb50159.patch
> HiveServer interactive stop should wait for 30 second before sending kill -9
> ----------------------------------------------------------------------------
>
> Key: AMBARI-17776
> URL: https://issues.apache.org/jira/browse/AMBARI-17776
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.4.0
> Reporter: Ajit Kumar
> Assignee: Ajit Kumar
> Fix For: 2.4.0
>
> Attachments: rb50159.patch
>
>
> Currently when stopping Hive server interactive, the following steps seem to be taken.
> 1. Send kill to hive server interactive process
> 2. Wait for 5 seconds and send kill -9 if process in not killed.
> If HS2 is not shutdown properly - long running sessions (AMs) started by it will not be killed. In case of LLAP - these sessions will typically run for hours. Without the kill - LLAP cannot be restarted, since the old sessions will exist in the LLAP queue, and due to the precise capacity calculations - the queue will not have enough capacity to start new sessions.
> Ideally it should wait for 30 second before sending kill -9
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)