[
https://issues.apache.org/jira/browse/HBASE-10196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13852525#comment-13852525
]
Jean-Marc Spaggiari commented on HBASE-10196:
---------------------------------------------
I think it's good enough like that. Doesn't need to do anything else, as long
as it's reporting the situation. Odds are low for CatalogJ to not clear the
regions, so this should almost never occurs.
One small comment which can be done on commit, I will add a S at "its file" in
the log message.
+1!
Thanks for doing it.
> 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, hbase-10196-trunkv2.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)
