[
https://issues.apache.org/jira/browse/HBASE-18233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16055096#comment-16055096
]
stack commented on HBASE-18233:
-------------------------------
bq. We should 'flush' batches with read locks and then come back to try the
failed readlock again.
Ok.
I think this needs comment in the code. We are familiar w/ how it works now but
who knows who is going to be in here next and it takes a while to figure its
workings.
bq. As you can see in the new added UT
org.apache.hadoop.hbase.client.TestMultiParallel.testMultiThreadWithRowLocks,
if we wait for the lock, we will face 30 seconds timeout of getting locks
Why (I just skimmed the test). This is with sort in place? Why we get to 30
seconds waiting on a lock?
Thanks.
> We shouldn't wait for readlock in doMiniBatchMutation in case of deadlock
> -------------------------------------------------------------------------
>
> Key: HBASE-18233
> URL: https://issues.apache.org/jira/browse/HBASE-18233
> Project: HBase
> Issue Type: Bug
> Affects Versions: 1.2.7
> Reporter: Allan Yang
> Assignee: Allan Yang
> Attachments: HBASE-18233-branch-1.2.patch,
> HBASE-18233-branch-1.2.v2.patch
>
>
> Please refer to the discuss in HBASE-18144
> https://issues.apache.org/jira/browse/HBASE-18144?focusedCommentId=16051701&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16051701
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
