hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eugene Koifman (Jira)" <j...@apache.org>
Subject [jira] [Assigned] (HIVE-12544) ErrorMsg. LOCK_ACQUIRE_TIMEDOUT should include info about lock that caused the timeut
Date Wed, 28 Jul 2021 14:14:03 GMT

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

Eugene Koifman reassigned HIVE-12544:
-------------------------------------

    Assignee:     (was: Eugene Koifman)

> ErrorMsg. LOCK_ACQUIRE_TIMEDOUT should include info about lock that caused the timeut
> -------------------------------------------------------------------------------------
>
>                 Key: HIVE-12544
>                 URL: https://issues.apache.org/jira/browse/HIVE-12544
>             Project: Hive
>          Issue Type: Improvement
>          Components: Transactions
>    Affects Versions: 1.0.0
>            Reporter: Eugene Koifman
>            Priority: Major
>
> When lock acquisition times out, it would be useful to include info in the message about
the lock that caused the current request to block.
> It will help identify runaway processes, etc.
> This would require a Thrift change to pass that info up to the client which determines
when to give up waiting.
> Implementation:
>  
> In _case WAIT:_ in _TxnHandler.checkLock(Connection dbConn, long extLockId)_ add to _org.apache.hadoop.hive.metastore.api.LockResponse_
info from {code}locks[i]{code} which already has the ids and human readable info about conflicting
lock.



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

Mime
View raw message