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] [Updated] (HIVE-26237) Check if replication cause metastore connection leakage.

     [ https://issues.apache.org/jira/browse/HIVE-26237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated HIVE-26237:
----------------------------------
    Labels: pull-request-available  (was: )

> 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
>              Labels: pull-request-available
>          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)