[
https://issues.apache.org/jira/browse/HBASE-10273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861226#comment-13861226
]
Feng Honghua commented on HBASE-10273:
--------------------------------------
[~ram_krish] : Sounds great. I found this inconsistency and fixed it when
reviewing our internal 0.94.3 code base several months ago, and opened jira
together with other accumulated bug fixes in a batch mode these days, so do
less home work to find if there is already jira for it except I found it's
fixed when rebasing the fix against the latest code from HBase svn repository.
At least this bug still exists in latest 0.94.16. :-)
> AssignmentManager.regions(region to regionserver assignment map) and
> AssignmentManager.servers(regionserver to regions assignment map) are not
> always updated in tandem with each other
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-10273
> URL: https://issues.apache.org/jira/browse/HBASE-10273
> Project: HBase
> Issue Type: Bug
> Components: master
> Affects Versions: 0.94.16
> Reporter: Feng Honghua
> Assignee: Feng Honghua
> Fix For: 0.94.16
>
> Attachments: HBASE-10273-0.94_v0.patch
>
>
> By definition, AssignmentManager.servers and AssignmentManager.regions are
> tied and should be updated in tandem with each other under a lock on
> AssignmentManager.regions, but there are two places where this protocol is
> broken.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
