[
https://issues.apache.org/jira/browse/HIVE-14979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15587245#comment-15587245
]
Thejas M Nair edited comment on HIVE-14979 at 10/19/16 1:02 AM:
----------------------------------------------------------------
I believe the large session timeout was set because we have seen some cases
where gc pauses or temporary network issues cause persistent ephemeral nodes to
go away.
It didn't hurt to have the entry around a bit longer, as the client would retry
connect to other HS2 nodes.
was (Author: thejas):
I believe the large session timeout was set because we have seen some cases
where gc pauses or temporary network issues cause persistent ephemeral nodes to
go away.
It didn't hurt to have the entry around a bit longer, as the client would retry
connect to other nodes.
> 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)
