[ 
https://issues.apache.org/jira/browse/HIVE-25633?focusedWorklogId=668878&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-668878
 ]

ASF GitHub Bot logged work on HIVE-25633:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 22/Oct/21 10:40
            Start Date: 22/Oct/21 10:40
    Worklog Time Spent: 10m 
      Work Description: dengzhhu653 commented on pull request #2737:
URL: https://github.com/apache/hive/pull/2737#issuecomment-949503476


   +1


-- 
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: gitbox-unsubscr...@hive.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 668878)
    Time Spent: 20m  (was: 10m)

> 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
>          Time Spent: 20m
>  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)

Reply via email to