[
https://issues.apache.org/jira/browse/KUDU-2582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
xiaokai.wang updated KUDU-2582:
-------------------------------
Summary: Locks are acquired to cost much time in transactions (was: Lock
are acquired to cost much time in transactions)
> Locks are acquired to cost much time in transactions
> ----------------------------------------------------
>
> Key: KUDU-2582
> URL: https://issues.apache.org/jira/browse/KUDU-2582
> Project: Kudu
> Issue Type: Bug
> Reporter: xiaokai.wang
> Priority: Major
>
> Hi guys, I met a problem about the keys locks that almost impacts the service
> normal writing.
> As we all know, a transaction which get all row_key locks will go on next
> step in kudu. Everything looks good, if keys are not concurrent updated. But
> when keys are updated by more than one client at the same time, locks are
> acquired to wait much time. The cases are often in my product environment.
> Does anybody meet the problem? Has any good ideal for this?
> Thanks.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
