You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2014/05/13 22:27:17 UTC

[jira] [Commented] (HBASE-11158) bin/hbase upgrade -check should also check compression codecs

    [ https://issues.apache.org/jira/browse/HBASE-11158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13996857#comment-13996857 ] 

stack commented on HBASE-11158:
-------------------------------

It can't check the whole cluster though JMS, right?  And checking for libs is orthogonal to upgrade?  Thanks.

> 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)