hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jean-Marc Spaggiari (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-10196) Enhance HBCK to understand the case after online region merge
Date Thu, 19 Dec 2013 02:06:07 GMT

    [ https://issues.apache.org/jira/browse/HBASE-10196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13852468#comment-13852468
] 

Jean-Marc Spaggiari commented on HBASE-10196:
---------------------------------------------

Is it not possible to just add a message like:

{code}
+      if (hbi.isMerged()) {
+        // This region has already been merged, the remaining hdfs file will be
+        // cleaned by CatalogJanitor later
+        hbi.setSkipChecks(true);
+        LOG.info("Region " + hbi.getHdfsHRI() + " got merge recently, will be cleaned by
CatalogJanitor later");
+        return;
+      }
{code}

So if people keep seeing the same region again and again they might know there is something
wrong?

> Enhance HBCK to understand the case after online region merge
> -------------------------------------------------------------
>
>                 Key: HBASE-10196
>                 URL: https://issues.apache.org/jira/browse/HBASE-10196
>             Project: HBase
>          Issue Type: Bug
>            Reporter: chunhui shen
>            Assignee: chunhui shen
>             Fix For: 0.96.2, 0.98.1, 0.99.0
>
>         Attachments: hbase-10196-trunk.patch
>
>
> HBCK will report an error now after the online merge,
> because the files of merging regions still remain on HDFS which will be cleaned by CatalogJanitor
later.
> ERROR: Region { meta => null, hdfs =>
> hdfs://hbasetest1:9000/hbase/data/default/dns/c6569a72cc3c2750d14976ab85f02315,
> deployed =>  } on HDFS, but not listed in hbase:meta or deployed on any region server



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)

Mime
View raw message