You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Jerry He (JIRA)" <ji...@apache.org> on 2014/09/13 00:30:34 UTC

[jira] [Commented] (HBASE-11965) Optimize locking in HRegion

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

Jerry He commented on HBASE-11965:
----------------------------------

Trying to understand the bottleneck for the cases you mentioned.
Won't they only be acquiring region read lock, and concurrent read locks are allowed? 

> Optimize locking in HRegion
> ---------------------------
>
>                 Key: HBASE-11965
>                 URL: https://issues.apache.org/jira/browse/HBASE-11965
>             Project: HBase
>          Issue Type: Bug
>          Components: Performance
>            Reporter: Vladimir Rodionov
>            Assignee: Vladimir Rodionov
>
> Described in this thread:
> http://mail-archives.apache.org/mod_mbox/hbase-dev/201409.mbox/%3CCAAg3a2qmWJtQbdAk7PrX%2BW8SZWxsYhNggM5f2RNkGTXUri34YQ%40mail.gmail.com%3E
> *startRegionOperation* and *closeRegionOperation* in HRegion acquires and releases region-wide lock. The locking happens for every mutation, read and scan next. This is a serious bottleneck if we do:
> * Mutli - get on a same region.
> * Run multiple scanners on same region.
> * Do scan during compaction.
> * Access region simultaneously from different threads (most generic case)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)