[
https://issues.apache.org/jira/browse/HIVE-27692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhihua Deng resolved HIVE-27692.
--------------------------------
Fix Version/s: 4.0.0
Resolution: Fixed
Fix has been merged. Thank you Naveen for the review!
> Explore removing the always task from embedded HMS
> --------------------------------------------------
>
> Key: HIVE-27692
> URL: https://issues.apache.org/jira/browse/HIVE-27692
> Project: Hive
> Issue Type: Improvement
> Components: Standalone Metastore
> Reporter: Zhihua Deng
> Assignee: Zhihua Deng
> Priority: Major
> Labels: pull-request-available
> Fix For: 4.0.0
>
>
> The always tasks are running in the leader HMS now, the properties for
> configuring the leader should only belong to HMS, other engines such as
> Spark/Impala doesn't need to know these properties. For most cases, the
> engine only cares about the properties for connecting HMS, e.g,
> hive.metastore.uris.
> Every time when a new apps uses an embedded Metastore, it will start the HMS
> always tasks by default. Imaging we have hundreds of apps, then hundreds of
> pieces of the same tasks are running, this will put extra burden to the
> underlying databases, such as the flooding queries, connection limit.
> I think we can remove always tasks from the embeded Metastore, the always
> task will be taken care of by the standalone Metastore, as a standalone
> Metastore should be here in production environment.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
