You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hive.apache.org by "Jeongdae Kim (Jira)" <ji...@apache.org> on 2022/03/08 09:50:00 UTC

[jira] [Commented] (HIVE-25846) Ensure that deregistering hive servers works, even after zookeeper session expired

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

Jeongdae Kim commented on HIVE-25846:
-------------------------------------

Is there anyone who can take a look at this? https://github.com/apache/hive/pull/2920

> Ensure that deregistering hive servers works, even after zookeeper session expired
> ----------------------------------------------------------------------------------
>
>                 Key: HIVE-25846
>                 URL: https://issues.apache.org/jira/browse/HIVE-25846
>             Project: Hive
>          Issue Type: Bug
>    Affects Versions: 2.3.8, 3.1.2
>            Reporter: Jeongdae Kim
>            Assignee: Jeongdae Kim
>            Priority: Minor
>              Labels: pull-request-available
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Zookeeper watchers are one time trigger and when zookeeper session is expired by long gc pause or something and is reconnected, all watchers already registered are gone, and deregister mechanism doesn't work.
> We should register deregister watchers again to get notification, after session re-established.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)