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

Denys Kuzmenko updated HIVE-22906:
----------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

> Redundant checkLock Mutex blocks concurrent Lock requests
> ---------------------------------------------------------
>
>                 Key: HIVE-22906
>                 URL: https://issues.apache.org/jira/browse/HIVE-22906
>             Project: Hive
>          Issue Type: Improvement
>          Components: Locking
>            Reporter: Denys Kuzmenko
>            Assignee: Denys Kuzmenko
>            Priority: Major
>         Attachments: HIVE-22906.1.patch
>
>
> enqueueLocks is already serialising locks creation via (SELECT NL_NEXT FROM 
> NEXT_LOCK_ID FOR UPDATE). Requested locks would be assigned 'W' state.
> checkLock is iterating over the sorted set of conflicting locks below current 
> EXT_LOCK_ID. It does handle the situation when there is conflicting lock with 
> lower ID in 'W' state - lock request would be denied and retried later.   



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to