[ https://issues.apache.org/jira/browse/HIVE-26794?focusedWorklogId=837826&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-837826 ]
ASF GitHub Bot logged work on HIVE-26794: ----------------------------------------- Author: ASF GitHub Bot Created on: 09/Jan/23 08:42 Start Date: 09/Jan/23 08:42 Worklog Time Spent: 10m Work Description: dengzhhu653 commented on code in PR #3817: URL: https://github.com/apache/hive/pull/3817#discussion_r1064388571 ########## standalone-metastore/metastore-server/src/main/java/org/apache/hadoop/hive/metastore/datasource/DbCPDataSourceProvider.java: ########## @@ -112,9 +113,17 @@ public DataSource create(Configuration hdpConfig, int maxPoolSize) throws SQLExc objectPool.setSoftMinEvictableIdleTimeMillis(softMinEvictableIdleTimeMillis); objectPool.setLifo(lifo); + if ("mutex".equalsIgnoreCase(poolName)) { Review Comment: Done Issue Time Tracking ------------------- Worklog Id: (was: 837826) Time Spent: 4h 40m (was: 4.5h) > 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 > Assignee: Zhihua Deng > Priority: Major > Labels: pull-request-available > Time Spent: 4h 40m > Remaining Estimate: 0h > > Instead of creating a fixed size connection pool for TxnHandler#MutexAPI, the > pool can be assigned to a more dynamic size pool 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; > -- This message was sent by Atlassian Jira (v8.20.10#820010)