hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Hsieh (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-4458) HBase should give actionable information when a region is compressed with a codec that is not available.
Date Fri, 23 Sep 2011 20:05:26 GMT

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

Jonathan Hsieh commented on HBASE-4458:
---------------------------------------

>From reading the description it looks like HBASE-2515 worked.  However, in this particular
scenario, *none* of the regions servers had LZO installed.  The goal was to move to another
codec and somehow during the migration some regions were missed.  

The symptom we saw was that regions failed to be deployed. Admittedly, we didn't initially
look at the logs.  We tried assigning from the shell, but I don't recall seeing any class
not found exceptions when the shell command failed.  We ended up figuring out the problem
by using HFile on the data in the hdfs region data and getting the ClassNotFound there.

This brings up four potential places for an error message -- in the shell, in hbck, in the
web ui, as well as in the logs.




> 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

        

Mime
View raw message