hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sergio Peña (JIRA) <>
Subject [jira] [Commented] (HIVE-14187) JDOPersistenceManager objects remain cached if MetaStoreClient#close is not called
Date Fri, 15 Jul 2016 21:48:20 GMT


Sergio Peña commented on HIVE-14187:

thanks [~mohitsabharwal] I committed this to 2.2

> JDOPersistenceManager objects remain cached if MetaStoreClient#close is not called
> ----------------------------------------------------------------------------------
>                 Key: HIVE-14187
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Mohit Sabharwal
>            Assignee: Mohit Sabharwal
>             Fix For: 2.2.0
>         Attachments: HIVE-14187.1.patch, HIVE-14187.2.patch, HIVE-14187.patch, HIVE-14187.patch
> JDOPersistenceManager objects are cached in JDOPersistenceManagerFactory by DataNuclues.
> A new JDOPersistenceManager object gets created for every HMS thread since ObjectStore
is a thread local.
> In non-embedded metastore mode, JDOPersistenceManager associated with a thread only gets
cleaned up if IMetaStoreClient#close is called by the client (which calls ObjectStore#shutdown
which calls JDOPersistenceManager#close which in turn removes the object from cache in JDOPersistenceManagerFactory#releasePersistenceManager
i.e. the object will remain cached if client does not call close.
> For example: If one interrupts out of hive CLI shell (instead of using 'exit;' command),
SessionState#close does not get called, and hence IMetaStoreClient#close does not get called.
> Instead of relying the client to call close, it's cleaner to automatically perform RawStore
related cleanup at the server end via deleteContext() which gets called when the server detects
a lost/closed connection.

This message was sent by Atlassian JIRA

View raw message