You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Zoltan Haindrich (Jira)" <ji...@apache.org> on 2021/10/27 07:21:00 UTC
[jira] [Resolved] (HIVE-25633) Prevent shutdown of MetaStore
scheduled worker ThreadPool
[ https://issues.apache.org/jira/browse/HIVE-25633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zoltan Haindrich resolved HIVE-25633.
-------------------------------------
Fix Version/s: 4.0.0
Resolution: Fixed
merged into master. Thank you [~euigeun_chung] and [~kkasa] for reviewing the changes!
> Prevent shutdown of MetaStore scheduled worker ThreadPool
> ---------------------------------------------------------
>
> Key: HIVE-25633
> URL: https://issues.apache.org/jira/browse/HIVE-25633
> Project: Hive
> Issue Type: Bug
> Reporter: Zoltan Haindrich
> Assignee: Zoltan Haindrich
> Priority: Major
> Labels: pull-request-available
> Fix For: 4.0.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> [~lpinter] have noticed that this patch has some sideffect:
> in HIVE-23164 the patch have added a {{ThreadPool#shutdown}} to {{HMSHandler#shutdown}} - which could cause trouble in case a {{HMSHandler}} is shutdown and a new one is created
> I was looking for cases in which a HMSHandler is created inside the metastore (beyond the one HiveMetaStore is using) - and I think tasks like PartitionManagementTask which uses Msck which uses HMC to access the metastore - and they close the client - which closes the hmshandler client ; which will shut down the threadpool
--
This message was sent by Atlassian Jira
(v8.3.4#803005)