You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Prasanth Jayachandran (JIRA)" <ji...@apache.org> on 2016/09/12 21:34:21 UTC
[jira] [Created] (HIVE-14739) Replace runnables directly added to
runtime shutdown hooks to avoid deadlock
Prasanth Jayachandran created HIVE-14739:
--------------------------------------------
Summary: Replace runnables directly added to runtime shutdown hooks to avoid deadlock
Key: HIVE-14739
URL: https://issues.apache.org/jira/browse/HIVE-14739
Project: Hive
Issue Type: Bug
Affects Versions: 2.2.0
Reporter: Deepesh Khandelwal
Assignee: Prasanth Jayachandran
[~deepesh] reported that a deadlock can occur when running queries through hive cli. [~cnauroth] analyzed it and reported that hive adds shutdown hooks directly to java Runtime which may execute in non-deterministic order causing deadlocks with hadoop's shutdown hooks. In one case, hadoop shutdown locked FileSystem#Cache and FileSystem.close whereas hive shutdown hook locked FileSystem.close and FileSystem#Cache order causing a deadlock.
Hive and Hadoop has ShutdownHookManager that runs the shutdown hooks in deterministic order based on priority. We should use that to avoid deadlock throughout the code.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)