You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Lars Hofhansl (JIRA)" <ji...@apache.org> on 2013/05/21 06:09:16 UTC
[jira] [Updated] (HBASE-7959) HBCK skips regions that have been
recently modified, which then leads to it to report holes in region chain
[ https://issues.apache.org/jira/browse/HBASE-7959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Hofhansl updated HBASE-7959:
---------------------------------
Fix Version/s: (was: 0.94.8)
0.94.9
Pushing to 0.94.9.
> HBCK skips regions that have been recently modified, which then leads to it to report holes in region chain
> -----------------------------------------------------------------------------------------------------------
>
> Key: HBASE-7959
> URL: https://issues.apache.org/jira/browse/HBASE-7959
> Project: HBase
> Issue Type: Bug
> Components: hbck
> Reporter: Enis Soztutar
> Fix For: 0.98.0, 0.94.9
>
>
> While lots of region splits going on, HBCK incorrectly reports inconsistencies since it skips recently modified, but does not take those into account for computing the region chain.
> {code}
> 13/02/28 03:33:16 WARN util.HBaseFsck: Region { meta => cluster_test,,1362021481742.69639761fdf693ab1e2bf33f523cd1ae., hdfs => NN:8020/apps/hbase-trunk/data/cluster_test/69639761fdf693ab1e2bf33f523cd1ae, deployed => } was recently modified -- skipping
> 13/02/28 03:33:16 DEBUG util.HBaseFsck: There are 23 region info entries
> ERROR: (region cluster_test,0ccccccc,1362021481742.ec3ba583b4ea01393591572bf1f31e07.) First region should start with an empty key. You need to create a new region and regioninfo in HDFS to plug the hole.
> ERROR: Found inconsistency in table cluster_test
> Summary:
> -ROOT- is okay.
> Number of regions: 1
> Deployed on: RSs
> .META. is okay.
> Number of regions: 1
> Deployed on: RSs
> Table cluster_test is inconsistent.
> Number of regions: 19
> Deployed on: RSs
> 1 inconsistencies detected.
> Status: INCONSISTENT
> {code}
--
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