[
https://issues.apache.org/jira/browse/HIVE-26794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhihua Deng updated HIVE-26794:
-------------------------------
Summary: Explore retiring TxnHandler#connPoolMutex idle connections (was:
Explore changing TxnHandler#connPoolMutex to NoPoolConnectionPool)
> Explore retiring TxnHandler#connPoolMutex idle connections
> ----------------------------------------------------------
>
> Key: HIVE-26794
> URL: https://issues.apache.org/jira/browse/HIVE-26794
> Project: Hive
> Issue Type: Improvement
> Components: Standalone Metastore
> Reporter: Zhihua Deng
> Priority: Major
> Labels: pull-request-available
> Time Spent: 2h
> Remaining Estimate: 0h
>
> Instead of creating a fixed size connection pool for TxnHandler#MutexAPI, the
> pool can be assigned to NoPoolConnectionPool due to:
> * TxnHandler#MutexAPI is primarily designed to provide coarse-grained mutex
> support to maintenance tasks running inside the Metastore, these tasks are
> not user faced;
> * A fixed size connection pool as same as the pool used in ObjectStore is a
> waste for other non leaders in the warehouse;
> The NoPoolConnectionPool provides connection on demand, and
> TxnHandler#MutexAPI only uses getConnection method to fetch a connection from
> the pool, so it's doable to change the pool to NoPoolConnectionPool, this
> would make the HMS more scaleable.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
