[
https://issues.apache.org/jira/browse/HIVE-26509?focusedWorklogId=812339&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-812339
]
ASF GitHub Bot logged work on HIVE-26509:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 27/Sep/22 03:16
Start Date: 27/Sep/22 03:16
Worklog Time Spent: 10m
Work Description: dengzhhu653 commented on code in PR #3567:
URL: https://github.com/apache/hive/pull/3567#discussion_r980691090
##########
standalone-metastore/metastore-common/src/main/java/org/apache/hadoop/hive/metastore/conf/MetastoreConf.java:
##########
@@ -562,6 +562,14 @@ public enum ConfVars {
"match that configuration. Otherwise it should be same as the hostname
returned by " +
"InetAddress#getLocalHost#getHostName(). Given the uncertainty in the
later " +
"it is desirable to configure metastore.thrift.bind.host on the
intended leader HMS."),
+
METASTORE_HOUSEKEEPING_LEADER_ELECTION("metastore.housekeeping.leader.election",
+ "metastore.housekeeping.leader.election",
Review Comment:
this is a newly introduced property, the `hive.` prefix is used to be
compatible with elder one, so I think it's ok to do this here.
Issue Time Tracking
-------------------
Worklog Id: (was: 812339)
Time Spent: 4h 20m (was: 4h 10m)
> 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
> Priority: Major
> Labels: pull-request-available
> Time Spent: 4h 20m
> 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)
