You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/05/18 08:48:00 UTC
[jira] [Work logged] (HIVE-26237) Check if replication cause metastore connection leakage.
[ https://issues.apache.org/jira/browse/HIVE-26237?focusedWorklogId=771753&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-771753 ]
ASF GitHub Bot logged work on HIVE-26237:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 18/May/22 08:47
Start Date: 18/May/22 08:47
Worklog Time Spent: 10m
Work Description: hmangla98 opened a new pull request, #3298:
URL: https://github.com/apache/hive/pull/3298
Problems:
1. Some replication tests don't close the ongoing HMS connections.
2. At one place in ReplLoadTask, we initiate a fresh HMS connection but don't close it.
3. In DDLOperationContext.java, sometimes stored Hive db object is closed and a new object is instantiated. In this case, Actual ddl operations (say CreateDatabaseOperation) will make fresh HMS connection in outdated Hive obj and it will never get closed since that this connection is not accessible. This is causing connection leakage.
Issue Time Tracking
-------------------
Worklog Id: (was: 771753)
Remaining Estimate: 0h
Time Spent: 10m
> Check if replication cause metastore connection leakage.
> --------------------------------------------------------
>
> Key: HIVE-26237
> URL: https://issues.apache.org/jira/browse/HIVE-26237
> Project: Hive
> Issue Type: Bug
> Reporter: Haymant Mangla
> Assignee: Haymant Mangla
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> It is observed that the after running replication unit tests, in some cases, the final number of metastore connections is not logged as 0.
> Sample test : TestReplicationScenarios.testBasic
> The last entry of hive.log which records connection count is as follows:
> INFO [main] metastore.HiveMetaStoreClient: Closed a connection to metastore, current connections: 3
--
This message was sent by Atlassian Jira
(v8.20.7#820007)