[
https://issues.apache.org/jira/browse/HBASE-10196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13852460#comment-13852460
]
chunhui shen commented on HBASE-10196:
--------------------------------------
Yes, nuil means no merge,
a general region doesn't have the MEAGE_A and MERGE_B qualifier.
Janitor couldn't cleant up the files of merge regions until the merged region
complete compaction,
it means the files will exist for a uncertain time.
The Janitor will log ERROR if failed cleaning up,
Also HBCK won't alert if the split parent region exist in META or HDFS.
So I think we could just treat it like Split Transaction, alert seems not
necessary and not easy to add.
> 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)
