You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Stamatis Zampetakis (Jira)" <ji...@apache.org> on 2025/04/17 11:42:00 UTC
[jira] [Resolved] (HIVE-28900) Make the objectstore-secondary connection pool size configurable
[ https://issues.apache.org/jira/browse/HIVE-28900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stamatis Zampetakis resolved HIVE-28900.
----------------------------------------
Fix Version/s: 4.1.0
Resolution: Fixed
Fixed in https://github.com/apache/hive/commit/a0465a9aa08e550f4cc497e929b7b2fe8979d615
> Make the objectstore-secondary connection pool size configurable
> ----------------------------------------------------------------
>
> Key: HIVE-28900
> URL: https://issues.apache.org/jira/browse/HIVE-28900
> Project: Hive
> Issue Type: Improvement
> Affects Versions: 4.0.1
> Reporter: Miklos Szurap
> Assignee: Miklos Szurap
> Priority: Major
> Labels: pull-request-available
> Fix For: 4.1.0
>
>
> The secondary connection factory is used for schema generation, and for value generation operations. Under normal circumstances 2 connections should be sufficient, however, we have found in HIVE-28839 that connection starvation may still happen. (in that case due to a datanucleus bug)
> We should make the "objectstore-secondary" pool size configurable. This is needed at least until a final fix is not available for HIVE-28839, but probably it is good to have on the long run if we find other edge cases too.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)