[
https://issues.apache.org/jira/browse/HBASE-20649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16534106#comment-16534106
]
Mike Drob commented on HBASE-20649:
-----------------------------------
{code}
+ for (Path p : corrupted) {
+ LOG.warn("Corrupt file: {}", p);
+ }
{code}
HFileCorruptionChecker looks like it will also log the same
https://github.com/apache/hbase/blob/master/hbase-server/src/main/java/org/apache/hadoop/hbase/util/hbck/HFileCorruptionChecker.java#L103
Does this get too chatty?
Have you tried running this against files with prefix tree headers?
I'm not sure how the archive files are laid out, I'll defer to [~busbey] there
since he was already considering it.
> Validate HFiles do not have PREFIX_TREE DataBlockEncoding
> ---------------------------------------------------------
>
> Key: HBASE-20649
> URL: https://issues.apache.org/jira/browse/HBASE-20649
> Project: HBase
> Issue Type: New Feature
> Reporter: Peter Somogyi
> Assignee: Balazs Meszaros
> Priority: Minor
> Fix For: 3.0.0
>
> Attachments: HBASE-20649.master.001.patch,
> HBASE-20649.master.002.patch, HBASE-20649.master.003.patch,
> HBASE-20649.master.004.patch
>
>
> HBASE-20592 adds a tool to check column families on the cluster do not have
> PREFIX_TREE encoding.
> Since it is possible that DataBlockEncoding was already changed but HFiles
> are not rewritten yet we would need a tool that can verify the content of
> hfiles in the cluster.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
