hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (Jira)" <>
Subject [jira] [Work logged] (HIVE-24713) HS2 never knows deregistering from Zookeeper in the particular case
Date Sat, 03 Jul 2021 00:09:00 GMT


ASF GitHub Bot logged work on HIVE-24713:

                Author: ASF GitHub Bot
            Created on: 03/Jul/21 00:08
            Start Date: 03/Jul/21 00:08
    Worklog Time Spent: 10m 
      Work Description: github-actions[bot] commented on pull request #1932:

   This pull request has been automatically marked as stale because it has not had recent
activity. It will be closed if no further activity occurs.
   Feel free to reach out on the list if the patch is in need of reviews.

This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail:

For queries about this service, please contact Infrastructure at:

Issue Time Tracking

    Worklog Id:     (was: 618300)
    Time Spent: 1h 40m  (was: 1.5h)

> HS2 never knows deregistering from Zookeeper in the particular case
> -------------------------------------------------------------------
>                 Key: HIVE-24713
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: HiveServer2
>            Reporter: Eugene Chung
>            Assignee: Eugene Chung
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 4.0.0
>          Time Spent: 1h 40m
>  Remaining Estimate: 0h
> While using zookeeper discovery mode, the problem that HS2 never knows deregistering
from Zookeeper always happens.
> Reproduction is simple.
>  # Find one of the zk servers which holds the DeRegisterWatcher watches of HS2 instances.
If the version of ZK server is 3.5.0 or above, it's easily found with [http://zk-server:8080/commands/watches] (ZK
AdminServer feature)
>  # Check which HS2 instance is watching on the ZK server found at 1, say it's _hs2-of-2_
>  # Restart the ZK server found at 1
>  # Deregister _hs2-of-2_ with the command
> {noformat}
> hive --service hiveserver2 -deregister hs2-of-2{noformat}
>  # _hs2-of-2_ never knows that it must be shut down because the watch event of DeregisterWatcher
was already fired at the time of 3.
> The reason of the problem is explained at []
> I added some logging to DeRegisterWatcher and checked what events were occurred at the
time of 3(restarting of ZK server);
>  # WatchedEvent state:Disconnected type:None path:null
>  # WatchedEvent[WatchedEvent state:SyncConnected type:None path:null]
>  # WatchedEvent[WatchedEvent state:SaslAuthenticated type:None path:null]
>  # WatchedEvent[WatchedEvent state:SyncConnected type:NodeDataChanged
>  path:/hiveserver2/serverUri=hs2-of-2:10000;version=3.1.2;sequence=0000000711]
> As the zk manual says, watches are one-time triggers. When the connection to the ZK server
was reestablished, state:SyncConnected type:NodeDataChanged for the path is fired and it's
the end. *DeregisterWatcher must be registered again for the same znode to get a future NodeDeleted

This message was sent by Atlassian Jira

View raw message