hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Prasanth Jayachandran (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HIVE-14739) Replace runnables directly added to runtime shutdown hooks to avoid deadlock
Date Tue, 13 Sep 2016 22:06:21 GMT

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

Prasanth Jayachandran updated HIVE-14739:
-----------------------------------------
    Attachment: HIVE-14739.4.patch

This patch introduced a change to ptest2 module which is not required (unwanted dependency
to hive breaking the build). Fixed it and committed. Uploading the relevant patch. 

> 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
>             Fix For: 2.2.0
>
>         Attachments: HIVE-14739.1.patch, HIVE-14739.2.patch, HIVE-14739.3.patch, HIVE-14739.4.patch
>
>
> [~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)

Mime
View raw message