[
https://issues.apache.org/jira/browse/HIVE-26509?focusedWorklogId=822168&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-822168
]
ASF GitHub Bot logged work on HIVE-26509:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 01/Nov/22 02:21
Start Date: 01/Nov/22 02:21
Worklog Time Spent: 10m
Work Description: dengzhhu653 commented on PR #3567:
URL: https://github.com/apache/hive/pull/3567#issuecomment-1297932228
Hi @nrg4878, cloud you please take a quick look if have some secs? Thank you
in advance!
Issue Time Tracking
-------------------
Worklog Id: (was: 822168)
Time Spent: 5h 50m (was: 5h 40m)
> Introduce dynamic leader election in HMS
> ----------------------------------------
>
> Key: HIVE-26509
> URL: https://issues.apache.org/jira/browse/HIVE-26509
> Project: Hive
> Issue Type: New Feature
> Components: Standalone Metastore
> Reporter: Zhihua Deng
> Assignee: Zhihua Deng
> Priority: Major
> Labels: pull-request-available
> Time Spent: 5h 50m
> Remaining Estimate: 0h
>
> From HIVE-21841 we have a leader HMS selected by configuring
> metastore.housekeeping.leader.hostname on startup. This approach saves us
> from running duplicated HMS's housekeeping tasks cluster-wide.
> In this jira, we introduce another dynamic leader election: adopt hive lock
> to implement the leader election. Once a HMS owns the lock, then it becomes
> the leader, carries out the housekeeping tasks, and sends heartbeats to renew
> the lock before timeout. If the leader fails to reclaim the lock, then stops
> the already started tasks if it has, the electing event is audited. We can
> achieve a more dynamic leader when the original goes down or in the public
> cloud without well configured property, and reduce the leader’s burdens by
> running these tasks among different leaders.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
