[
https://issues.apache.org/jira/browse/HBASE-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12932894#action_12932894
]
Jonathan Gray commented on HBASE-3243:
--------------------------------------
Dug into code around compareTo() and the values instance. Pretty sure we are
not touching that while a cluster is running, and definitely not during
disabling. We've actually even taken the 'offline' flag out of META as well,
it's a node in ZK now that signals the state of a table
(enabling/disabling/disabled).
It is interesting that HRI comparator uses the full HTD comparator. It should
probably just use the tableName itself to compare though considering HTD is a
member it might make sense in some circumstances to do the full HTD.compareTo()?
Looking around the code, it does look like there are multiple places we're
using regions w/o a lock in the disable table path. Pretty sure this is the
cause. Patch soon.
> 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.
