[
https://issues.apache.org/jira/browse/HBASE-20649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16539329#comment-16539329
]
Zach York commented on HBASE-20649:
-----------------------------------
Trying to get up to speed on this all. Overall looks like a handy upgrade tool!
[~busbey] Your steps are what we want to document as an operator?
It would be awesome if we could provide more info when running the specific
tool (if it fails in root dir, suggest trying a major compaction if data
encoding for the table is correct. If it fails in archive dir, see if any
Snapshots reference these files).
Could we have a tool/script to help automate determining which snapshot is
'dirty' and help to automatically clean it? It just seems like a lot of manual
steps to get your cluster upgrade ready (imagine if you had a number of
incremental snapshots).
> 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-20649.master.005.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)
