[
https://issues.apache.org/jira/browse/HBASE-11158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14000154#comment-14000154
]
stack commented on HBASE-11158:
-------------------------------
I like your proposal.
Later we could add:
./bin/hbase codecs
And it would take optional codec name. It'd run
http://hbase.apache.org/book.html#compression.test across the cluster and
return ERROR if a regionserver was missing a codec or just list codecs if no
arg supplied?
> bin/hbase upgrade -check should also check compression codecs
> -------------------------------------------------------------
>
> Key: HBASE-11158
> URL: https://issues.apache.org/jira/browse/HBASE-11158
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.99.0
> Reporter: Jean-Marc Spaggiari
>
> When upgrading insitu from 0.94 to 0.96 or 0.98 codecs are usually already
> there in the servers so it's all fine.
> But when doing an upgrade by moving the data from one cluster to a brand new
> one, compression codecs might be missing.
> bin/hbase upgrade -check will not report any missing codec, but HBase will
> not be able to start after the upgrade because the codes are missing.
> I think bin/hbase upgrade -check should check the compression codecs
> configured on the tables and make sure they are available on the new cluster.
> f not, it should be reported.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
