[
https://issues.apache.org/jira/browse/IMPALA-9375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17315220#comment-17315220
]
Robbie Zhang commented on IMPALA-9375:
--------------------------------------
[~vihangk1], except for DirectMetaProvider, there is one more HMS connection in
each executor:
[https://github.com/apache/impala/blob/1231208da7104c832c13f272d1e5b8f554d29337/fe/src/main/java/org/apache/impala/service/Frontend.java#L348]
Should we remove this connection as well?
> Remove DirectMetaProvider usage from CatalogMetaProvider
> --------------------------------------------------------
>
> Key: IMPALA-9375
> URL: https://issues.apache.org/jira/browse/IMPALA-9375
> Project: IMPALA
> Issue Type: Improvement
> Components: Catalog
> Affects Versions: Impala 3.4.0
> Reporter: Vihang Karajgaonkar
> Assignee: Vihang Karajgaonkar
> Priority: Critical
>
> I see that CatalogMetaProvider uses {{DirectMetaProvider}} here
> https://github.com/apache/impala/blob/master/fe/src/main/java/org/apache/impala/catalog/local/CatalogdMetaProvider.java#L239
> There are only a couple of places where it is used within
> CatalogMetaProvider. We should implement those remaining APIs in catalog-v2
> mode and remove the usage of DirectMetaProvider from CatalogMetaProvider.
> DirectMetaProvider starts by default a MetastoreClientPool (with 10
> connections). This is unnecessary given that catalog already makes the
> connections to HMS at its startup. It also slows down the coordinator startup
> time if there are HMS connection issues.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
