[
https://issues.apache.org/jira/browse/HIVE-26155?focusedWorklogId=760699&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-760699
]
ASF GitHub Bot logged work on HIVE-26155:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 22/Apr/22 08:54
Start Date: 22/Apr/22 08:54
Worklog Time Spent: 10m
Work Description: deniskuzZ commented on code in PR #3223:
URL: https://github.com/apache/hive/pull/3223#discussion_r855946205
##########
standalone-metastore/metastore-server/src/main/java/org/apache/hadoop/hive/metastore/datasource/HikariCPDataSourceProvider.java:
##########
@@ -45,15 +45,19 @@ public class HikariCPDataSourceProvider implements
DataSourceProvider {
@Override
public DataSource create(Configuration hdpConfig) throws SQLException {
+ int maxPoolSize = MetastoreConf.getIntVar(hdpConfig,
Review Comment:
Could we extract this into the default method in the interface since we
always use the same conf -
MetastoreConf.ConfVars.CONNECTION_POOLING_MAX_CONNECTIONS?
Issue Time Tracking
-------------------
Worklog Id: (was: 760699)
Time Spent: 20m (was: 10m)
> 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: 20m
> 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)
