[
https://issues.apache.org/jira/browse/HBASE-11290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15262660#comment-15262660
]
Francis Liu commented on HBASE-11290:
-------------------------------------
[~mantonov] At the moment we just need it to get into branch-1 no worries about
not getting it into 1.3. With that I'd be happy to update this patch if you're
still up for reviewing it this weekend (tho you don't have to)? BTW the current
patch I have is for trunk are you asking me to rebase onto trunk? Or create
patches for both trunk and 1.x?
What's the name of the lock? I can take a look. Tho if it's usable maybe we can
just replace Idlock once HBASE-15648 goes 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.4.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)
