[jira] [Resolved] (IMPALA-9824) MetastoreClientPool should be singleton

["Vihang Karajgaonkar (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IMPALA-9824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vihang Karajgaonkar resolved IMPALA-9824.
-----------------------------------------
    Fix Version/s: Not Applicable
       Resolution: Won't Fix

Resolving as "won't fix" due to complications in FE tests when changing MetastoreClientPool into singleton. Currently, this is not critical since we make sure that coordinator and catalog instantiate one pool each.

> MetastoreClientPool should be singleton
> ---------------------------------------
>
>                 Key: IMPALA-9824
>                 URL: https://issues.apache.org/jira/browse/IMPALA-9824
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Catalog
>            Reporter: Vihang Karajgaonkar
>            Assignee: Vihang Karajgaonkar
>            Priority: Minor
>             Fix For: Not Applicable
>
>
> Currently,  the MetastoreClientPool is instantiated at multiple places in the code and it would be good to refactor the code to make it a singleton. Each MetastoreClientPool creates multiple clients to HMS and unnecessary creation of multiple pools could cause problems on HMS side. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)