You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hive.apache.org by "tenglei (Jira)" <ji...@apache.org> on 2021/12/21 14:27:00 UTC

[jira] [Created] (HIVE-25830) Hive::loadPartitionInternal occur connection leak

tenglei created HIVE-25830:
------------------------------

             Summary: Hive::loadPartitionInternal occur connection leak
                 Key: HIVE-25830
                 URL: https://issues.apache.org/jira/browse/HIVE-25830
             Project: Hive
          Issue Type: Bug
            Reporter: tenglei


when Hive::loadPartitionInternal is invoked and there's no metastore connection in Hive.ThreadLocalHive, will create a metastore connection  for Hive.ThreadLocalHive, if external part hold the Hive.ThreadLocalHive for cache, and Hive.ThreadLocalHive update in some special scene, this will cause external part hold the different Hive object to Hive.ThreadLocalHive.when external part want to create a metastore connection by invoking Hive::loadPartitionInternal, Hive will create a metastore connection for Hive.ThreadLocalHive, not for external part's holding.so these can cause a connection leaks easliy.

I found it will cause a metastore connection leak in spark-beeline when invoke Hive::loadPartitionInternal.

there's a commit HIVE-25075 relate before, I think it should remove the Hive.get() in Hive::loadPartitionInternal at the same time.




--
This message was sent by Atlassian Jira
(v8.20.1#820001)