[
https://issues.apache.org/jira/browse/AMBARI-17776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15383419#comment-15383419
]
Hudson commented on AMBARI-17776:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #5336 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5336/])
AMBARI-17776. HiveServer interactive stop should wait for 30 second (ajit:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=e405f5277a9fcf3c5d2c4844c7a43a5422052afb])
*
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hive_service_interactive.py
* ambari-server/src/test/python/stacks/2.5/HIVE/test_hive_server_int.py
> 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)
