[jira] [Commented] (HIVE-19177) ObjectStore.setConf() is doing dangerous work while holding global lock

["Sergey Shelukhin (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HIVE-19177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16439829#comment-16439829 ] 

Sergey Shelukhin commented on HIVE-19177:
-----------------------------------------

What is this lock actually for? It may be protecting datanucleus automatic database initialization...

> ObjectStore.setConf() is doing dangerous work while holding global lock
> -----------------------------------------------------------------------
>
>                 Key: HIVE-19177
>                 URL: https://issues.apache.org/jira/browse/HIVE-19177
>             Project: Hive
>          Issue Type: Bug
>          Components: Metastore
>    Affects Versions: 2.0.2, 3.0.0, 3.1.0
>            Reporter: Alexander Kolbasov
>            Priority: Major
>
> The {{ObjectStore.setConf()}} function grabs static {{pmfPropLock}} and then calls {{initialize}} which goes through DataNucleus, accesses database, waits on DB thread pools, retries with sleep, etc, all while holding the lock.
> This is rather dangerous and expensive since no one else can call setConf at the same time on a different instance. All of these should be done without holding the lock.
> [~vihangk1] FYI.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)