You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Cosmin Lehene (JIRA)" <ji...@apache.org> on 2015/01/13 01:47:35 UTC
[jira] [Resolved] (HBASE-3243) Disable Table closed region on wrong
host
[ https://issues.apache.org/jira/browse/HBASE-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Cosmin Lehene resolved HBASE-3243.
----------------------------------
Resolution: Cannot Reproduce
[~tlipcon], [~stack], [~streamy] this is old. Closing as probably everything changed in the meantime and not an issue anymore.
> 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
> Labels: delete
> Attachments: 3243-v2.patch, HBASE-3243-v1.patch, hbase-3243-logs.tar.bz2, hri.diff
>
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)