You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "mrunmayi Sahasrabudhe (JIRA)" <ji...@apache.org> on 2018/10/30 16:09:00 UTC
[jira] [Created] (HIVE-20837) Tez AM container do not get killed
after killing hive jvm when HS2 is not up
mrunmayi Sahasrabudhe created HIVE-20837:
--------------------------------------------
Summary: Tez AM container do not get killed after killing hive jvm when HS2 is not up
Key: HIVE-20837
URL: https://issues.apache.org/jira/browse/HIVE-20837
Project: Hive
Issue Type: Bug
Components: Hive
Affects Versions: 2.3.2
Reporter: mrunmayi Sahasrabudhe
Reproduction steps :
1. Start hive by setting execution engine to tez
3. Run any command
4. yarn application -list
5. Kill the command before it finishes.
6. check in yarn application -list for the same application id. It is visible till upto 10mins and gets shutdown due to timeout.
Ideally it should kill all the non default sessions.
In case of Non HS2 all the session are non default.
Other details:
1. This issue is reproducible with hive-2.1.1 and not in hive1.2
3. Does status of application should be shown as killed or succeed should be decided.
for that refer QTEZ-137
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)