Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 9 May 2012 03:59:07 +0000 (UTC)
From: "Jean-Daniel Cryans (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <1469547861.42381.1336535947512.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1300360783.23239.1336072129079.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HBASE-5929) HBaseAdmin.compact and flush are
 giving confusing errors for ROOT, META, and regions that don't exist
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jean-Daniel Cryans commented on HBASE-5929:
-------------------------------------------

I spawed HBASE-5969 for the apparent randomness of the issue with the region that's pre 0.89
                
> HBaseAdmin.compact and flush are giving confusing errors for ROOT, META, and regions that don't exist
> -----------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-5929
>                 URL: https://issues.apache.org/jira/browse/HBASE-5929
>             Project: HBase
>          Issue Type: Bug
>          Components: client, shell
>    Affects Versions: 0.92.1
>         Environment: Linux Ubuntu Lucid 64bit
>            Reporter: Aravind Gottipati
>            Priority: Minor
>
> I have been noticing that calls to HBaseAdmin.majorCompact throws exceptions randomly for some regions.  I could not find a pattern to these exception.  The code I have simply does this admin.majorCompact(region.getRegionNameAsString()).  admin is an instance of HBaseAdmin and region is an instance of HRegionInfo.  The exception I get is 
> org.apache.hadoop.hbase.TableNotFoundException: -ROOT-,,0
>         at org.apache.hadoop.hbase.client.HBaseAdmin.tableNameString(HBaseAdmin.java:1473) ~[hbase-0.92.1.jar:0.92.1]
>         at org.apache.hadoop.hbase.client.HBaseAdmin.compact(HBaseAdmin.java:1235) ~[hbase-0.92.1.jar:0.92.1]
>         at org.apache.hadoop.hbase.client.HBaseAdmin.majorCompact(HBaseAdmin.java:1209) ~[hbase-0.92.1.jar:0.92.1]
>         at com.stumbleupon.hbaseadmin.HBaseCompact.compactAllServers(Unknown Source) [hbase_compact.jar:na]
> In this case it's the root region, but I get similar exceptions for other tables, like this.
> 2012-05-03 19:03:42,994 WARN  [main] HBaseCompact: Could not compact:
> org.apache.hadoop.hbase.TableNotFoundException: ad_daily,49842:2009-07-10,1269763588508.1997607018
>         at org.apache.hadoop.hbase.client.HBaseAdmin.tableNameString(HBaseAdmin.java:1473) ~[hbase-0.92.1.jar:0.92.1]
>         at org.apache.hadoop.hbase.client.HBaseAdmin.compact(HBaseAdmin.java:1235) ~[hbase-0.92.1.jar:0.92.1]
>         at org.apache.hadoop.hbase.client.HBaseAdmin.majorCompact(HBaseAdmin.java:1209) ~[hbase-0.92.1.jar:0.92.1]
>         at org.apache.hadoop.hbase.client.HBaseAdmin.majorCompact(HBaseAdmin.java:1196) ~[hbase-0.92.1.jar:0.92.1]
>         at com.stumbleupon.hbaseadmin.HBaseCompact.compactAllServers(Unknown Source) [hbase_compact.jar:na]
>         at com.stumbleupon.hbaseadmin.HBaseCompact.main(Unknown Source) [hbase_compact.jar:na]
> I see this on hbase shell as well.  However, I don't see these exceptions if I use admin.majorCompact(region.getRegionName()), so it looks like something gets lost when I use getRegionNameAsString().
> Let me know if I can provide more information.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira