[
https://issues.apache.org/jira/browse/HBASE-18144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16055194#comment-16055194
]
Allan Yang edited comment on HBASE-18144 at 6/20/17 6:07 AM:
-------------------------------------------------------------
{quote}
The write-lock attempt is blocked (not able to acquire the lock), and this
attempt also blocks other read attempts on the same row it looks like.
{quote}
[~jerryhe], you are right, ReentrantReadWriteLock is a 'write first' lock. If
some thread is waiting on the write lock, it will also block any attempt to
grab the readlock. Otherwise, if some threads are continuing to read the
object, the write thread will never have chance to write.
was (Author: allan163):
{quote}
The write-lock attempt is blocked (not able to acquire the lock), and this
attempt also blocks other read attempts on the same row it looks like.
{quote}
[~jerryhe], you are right, ReentrantReadWriteLock is a 'write first' lock. If
some thread is waiting on the write lock, it will also block any attempt to
grab the readlock. Otherwise, if some thread is continuing read the object, the
write thread will never have chance to write.
> Forward-port the old exclusive row lock; there are scenarios where it
> performs better
> -------------------------------------------------------------------------------------
>
> Key: HBASE-18144
> URL: https://issues.apache.org/jira/browse/HBASE-18144
> Project: HBase
> Issue Type: Bug
> Components: Increment
> Affects Versions: 1.2.5
> Reporter: stack
> Assignee: stack
> Fix For: 2.0.0, 1.3.2, 1.2.7
>
> Attachments: DisorderedBatchAndIncrementUT.patch,
> HBASE-18144.master.001.patch
>
>
> Description to follow.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
