hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alan Gates (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-13013) Further Improve concurrency in TxnHandler
Date Thu, 11 Feb 2016 19:37:18 GMT

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

Alan Gates commented on HIVE-13013:
-----------------------------------

This will take me a bit to comb through completely as the changes are pretty in depth, but
one piece of early feedback is that it would be useful to distinguish the new lock() and unlock()
functions with names like derbyLock() or localLock() or something since there's multiple types
of locks floating around here.  

> Further Improve concurrency in TxnHandler
> -----------------------------------------
>
>                 Key: HIVE-13013
>                 URL: https://issues.apache.org/jira/browse/HIVE-13013
>             Project: Hive
>          Issue Type: Bug
>          Components: Metastore, Transactions
>    Affects Versions: 1.0.0
>            Reporter: Eugene Koifman
>            Assignee: Eugene Koifman
>            Priority: Critical
>         Attachments: HIVE-13013.patch
>
>
> There are still a few operations in TxnHandler that run at Serializable isolation.
> Most or all of them can be dropped to READ_COMMITTED now that we have SELECT ... FOR
UPDATE support.  This will reduce number of deadlocks in the DBs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message