hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allan Yang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-18144) Forward-port the old exclusive row lock; there are scenarios where it performs better
Date Fri, 02 Jun 2017 03:48:04 GMT

    [ https://issues.apache.org/jira/browse/HBASE-18144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034091#comment-16034091
] 

Allan Yang commented on HBASE-18144:
------------------------------------

Hi, [~stack], I uploaded a patch(HBASE-17924) with a UT to simulating disordered batch and
increment at the same time. Disordered batch put and increment may be the root cause of your
costumer's strange thread dump.
You can see, without of HBASE-17924, the UT will timeout and fail, but with HBASE-17924, this
UT can run normally. I haven't looked deep into it. But it clearly showed there is a problem
with lock efficiency. 

> 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
>
>
> Description to follow.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message