You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2017/06/30 12:24:00 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=16070007#comment-16070007 ]
stack commented on HBASE-11290:
-------------------------------
Removed 2.0.0. RegionStates is different in 2.0.0. Let this be about branch-1.
> 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: 1.5.0
>
> Attachments: HBASE-11290.01.branch-1.patch, HBASE-11290.02.patch, HBASE-11290.03.patch, 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.4.14#64029)