hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter Vary (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-14979) Removing stale Zookeeper locks at HiveServer2 initialization
Date Wed, 19 Oct 2016 11:42:58 GMT

    [ https://issues.apache.org/jira/browse/HIVE-14979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15588516#comment-15588516
] 

Peter Vary commented on HIVE-14979:
-----------------------------------

In this case it would be good to have a way to remove these "almost persistent" :) lock entries
from Zookeeper in case of a catastrophic failure.

Worth to mention, that (according to the documentation) the Zookeeper server could overrule
the requested timeout with its own maxSessionTimeout configuration variable, which makes the
usefulness of this feature very (Zookeeper and Hive) configuration dependent.

> Removing stale Zookeeper locks at HiveServer2 initialization
> ------------------------------------------------------------
>
>                 Key: HIVE-14979
>                 URL: https://issues.apache.org/jira/browse/HIVE-14979
>             Project: Hive
>          Issue Type: Improvement
>          Components: Locking
>            Reporter: Peter Vary
>            Assignee: Peter Vary
>         Attachments: HIVE-14979.3.patch, HIVE-14979.patch
>
>
> HiveServer2 could use Zookeeper to store token that indicate that particular tables are
locked with the creation of persistent Zookeeper objects. 
> A problem can occur when a HiveServer2 instance creates a lock on a table and the HiveServer2
instances crashes ("Out of Memory" for example) and the locks are not released in Zookeeper.
This lock will then remain until it is manually cleared by an admin.
> There should be a way to remove stale locks at HiveServer2 initialization, helping the
admins life.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message