[
https://issues.apache.org/jira/browse/HIVE-12544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eugene Koifman updated HIVE-12544:
----------------------------------
Description:
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()_ 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.
was:
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.
> 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
> Assignee: Eugene Koifman
>
> 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()_ 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
(v6.3.15#6346)