[
https://issues.apache.org/jira/browse/HBASE-6611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13454133#comment-13454133
]
Jacques commented on HBASE-6611:
--------------------------------
Reminders from the PowWow yesterday...
JD requested that you verify that force close continues to function despite
changes.
JD & Andrew both requested that you run some performance tests to ensure that
region assignment doesn't take substantially longer than 0.94. Something along
the lines of bulk assignment of 10,000 regions and also checking to ensure that
region failover isn't substantially longer.
> Forcing region state offline cause double assignment
> ----------------------------------------------------
>
> Key: HBASE-6611
> URL: https://issues.apache.org/jira/browse/HBASE-6611
> Project: HBase
> Issue Type: Bug
> Components: master
> Reporter: Jimmy Xiang
> Assignee: Jimmy Xiang
> Fix For: 0.96.0
>
>
> In assigning a region, assignment manager forces the region state offline if
> it is not. This could cause double assignment, for example, if the region is
> already assigned and in the Open state, you should not just change it's state
> to Offline, and assign it again.
> I think this could be the root cause for all double assignments IF the region
> state is reliable.
> After this loophole is closed, TestHBaseFsck should come up a different way
> to create some assignment inconsistencies, for example, calling region server
> to open a region directly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
