You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Mikhail Antonov (JIRA)" <ji...@apache.org> on 2016/04/27 10:20:12 UTC
[jira] [Commented] (HBASE-11290) Unlock RegionStates
[ https://issues.apache.org/jira/browse/HBASE-11290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15259758#comment-15259758 ]
Mikhail Antonov commented on HBASE-11290:
-----------------------------------------
Unfortunately, I don't think I have any bandwidth to review it :( and this change would require thorough review/testing..
[~toffer], [~stack], [~eclark] - what do you guys think? I'm going to bump to 1.4 if we can't get it in.
> Unlock RegionStates
> -------------------
>
> Key: HBASE-11290
> URL: https://issues.apache.org/jira/browse/HBASE-11290
> Project: HBase
> Issue Type: Sub-task
> Affects Versions: 1.2.0, 1.3.0
> Reporter: Francis Liu
> Assignee: Francis Liu
> Fix For: 2.0.0, 1.3.0, 0.98.20
>
> Attachments: HBASE-11290-0.98.patch, HBASE-11290-0.98_v2.patch, HBASE-11290.draft.patch, HBASE-11290_trunk.patch
>
>
> Even though RegionStates is a highly accessed data structure in HMaster. Most of it's methods are synchronized. Which limits concurrency. Even simply making some of the getters non-synchronized by using concurrent data structures has helped with region assignments. We can go as simple as this approach or create locks per region or a bucket lock per region bucket.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)