[jira] [Resolved] (IMPALA-12402) Make CatalogdMetaProvider's cache concurrency level configurable

["Michael Smith (Jira)" <ji...@apache.org>]

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

Michael Smith resolved IMPALA-12402.
------------------------------------
    Fix Version/s: Impala 4.4.0
       Resolution: Fixed

> Make CatalogdMetaProvider's cache concurrency level configurable
> ----------------------------------------------------------------
>
>                 Key: IMPALA-12402
>                 URL: https://issues.apache.org/jira/browse/IMPALA-12402
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: fe
>            Reporter: Maxwell Guo
>            Assignee: Maxwell Guo
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: Impala 4.4.0
>
>
> when the cluster contains many db and tables such as if there are more than 100000 tables, and if we restart the impalad , the local cache_ CatalogMetaProvider's need to doing some loading process. 
> As we know that the goole's guava cache 's concurrencyLevel os set to 4 by default. 
> but if there is many tables the loading process will need more time and increase the probability of lock contention, see [here|https://github.com/google/guava/blob/master/guava/src/com/google/common/cache/CacheBuilder.java#L437]. 
> So we propose to add some configurations here, the first is the concurrency of cache.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)