hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jean-Marc Spaggiari (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-11158) bin/hbase upgrade -check should also check compression codecs
Date Fri, 16 May 2014 11:24:38 GMT

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

Jean-Marc Spaggiari commented on HBASE-11158:
---------------------------------------------

Ok. I thought about it a bit and it's not the best way to solve this. There is already a command
to validate compression codecs. So I think a better way to inform user about this is to list
the codes used when checking the upgrade, and document in the upgrade process to recommend
to check the available codecs when upgrade to a new cluster by pointing to the right documentation.
If you are fine with this approach I will close this JIRA, open one to add the codecs dump
in the -check portion, and another to update the documentation.

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

Mime
View raw message