Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 23 Sep 2011 18:55:26 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <1514344196.7669.1316804126211.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1794372783.1302.1316678606146.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HBASE-4458) HBase should give actionable
 information when a region is compressed with a codec that is not available.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

stack commented on HBASE-4458:
------------------------------

So HBASE-2514 didn't work?  Or, wasn't used I suppose.  Here is doc on lzo: http://hbase.apache.org/book.html#lzo.compression  It wasn't followed?  I agree it'd be better having issue show on master UI if we can.

> HBase should give actionable information when a region is compressed with a codec that is not available.
> --------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-4458
>                 URL: https://issues.apache.org/jira/browse/HBASE-4458
>             Project: HBase
>          Issue Type: Improvement
>    Affects Versions: 0.90.3
>            Reporter: Jonathan Hsieh
>
> A cluster that previously used LZO codec was upgraded with the intent of moving away from the codec to another.  Several regions failed to deploy because the LZO codec was no longer present.  However, there was little indication that this as the problem.
> Ideally, the master web ui or hbck would detect these problems and provide why it fails to deploy and also provide an actionable error message.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira