[
https://issues.apache.org/jira/browse/KUDU-2582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adar Dembo resolved KUDU-2582.
------------------------------
Resolution: Information Provided
Fix Version/s: NA
This is indeed a known issue in Kudu, and one of several reasons why Kudu
performs suboptimally for UPDATE-heavy workloads.
In any case, Jira isn't the right medium for open-ended discussion like this;
please e-mail [u...@kudu.apache.org|mailto:u...@kudu.apache.org], or join the
Kudu Slack community.
> 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
> Fix For: NA
>
>
> 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)
