[
https://issues.apache.org/jira/browse/HBASE-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12932825#action_12932825
]
Todd Lipcon commented on HBASE-3243:
------------------------------------
Just grasping at straws here... but another thought is this:
The keys of the {{regions}} map are HRegionInfo, where compareTo() includes
calling down to compareTo() on HTableDescriptor. HTableDescriptor's compareTo
eventually delegates to hashcode on the {{values}} instance... do we end up
changing the {{values}} instance when a table gets disabled? Perhaps this is
then changing the sort order in the TreeMap and confusing things?
> Disable Table closed region on wrong host
> -----------------------------------------
>
> Key: HBASE-3243
> URL: https://issues.apache.org/jira/browse/HBASE-3243
> Project: HBase
> Issue Type: Bug
> Components: master
> Affects Versions: 0.90.0
> Reporter: Todd Lipcon
> Priority: Blocker
> Fix For: 0.90.0
>
>
> I ran some YCSB benchmarks which resulted in about 150 regions worth of data
> overnight. Then I disabled the table, and the master for some reason closed
> one region on the wrong server. The server ignored this, but the region
> remained open on a different server, which later flipped out when it tried to
> flush due to hlog accumulation.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
