[
https://issues.apache.org/jira/browse/HBASE-11965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Kyle Purtell resolved HBASE-11965.
-----------------------------------------
Assignee: (was: Vladimir Rodionov)
Resolution: Invalid
> 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
> Priority: Major
>
> 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
(v8.20.7#820007)
