[
https://issues.apache.org/jira/browse/HIVE-26155?focusedWorklogId=762822&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-762822
]
ASF GitHub Bot logged work on HIVE-26155:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 27/Apr/22 12:02
Start Date: 27/Apr/22 12:02
Worklog Time Spent: 10m
Work Description: deniskuzZ commented on code in PR #3223:
URL: https://github.com/apache/hive/pull/3223#discussion_r859708999
##########
standalone-metastore/metastore-server/src/main/java/org/apache/hadoop/hive/metastore/txn/TxnHandler.java:
##########
@@ -5836,11 +5835,11 @@ private void removeTxnsFromMinHistoryLevel(Connection
dbConn, List<Long> txnids)
}
}
- private synchronized static DataSource setupJdbcConnectionPool(Configuration
conf, int maxPoolSize, long getConnectionTimeoutMs) {
+ protected synchronized static DataSource
setupJdbcConnectionPool(Configuration conf, int maxPoolSize) {
Review Comment:
oh, it's in TxnHandler, my bad
Issue Time Tracking
-------------------
Worklog Id: (was: 762822)
Time Spent: 1h (was: 50m)
> Create a new connection pool for compaction
> -------------------------------------------
>
> Key: HIVE-26155
> URL: https://issues.apache.org/jira/browse/HIVE-26155
> Project: Hive
> Issue Type: Improvement
> Components: Standalone Metastore
> Reporter: Antal Sinkovits
> Assignee: Antal Sinkovits
> Priority: Major
> Labels: compaction, pull-request-available
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Currently the TxnHandler uses 2 connection pools to communicate with the HMS:
> the default one and one for mutexing. If compaction is configured incorrectly
> (e.g. too many Initiators are running on the same db) then compaction can use
> up all the connections in the default connection pool and all user queries
> can get stuck.
> We should have a separate connection pool (configurable size) just for
> compaction-related activities.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
