hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-877) HCM is unable to find table with multiple regions which contains binary
Date Mon, 08 Sep 2008 17:01:44 GMT

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

stack commented on HBASE-877:

Patch needs to fix test failed compile.

Trying to replicate, ran doctered PerformanceEvalution that makes binary keys.... Then shutdown
cluster and brought it back up.    Trying to scan table, it just looped and looped over whole
table.  Applied patch after hacking in fix for tests and looping stopped.  Retrying.

> HCM is unable to find table with multiple regions which contains binary
> -----------------------------------------------------------------------
>                 Key: HBASE-877
>                 URL: https://issues.apache.org/jira/browse/HBASE-877
>             Project: Hadoop HBase
>          Issue Type: Bug
>    Affects Versions: 0.2.1, 0.18.0
>            Reporter: Jonathan Gray
>            Assignee: Jonathan Gray
>            Priority: Blocker
>             Fix For: 0.2.1, 0.18.0
>         Attachments: hbase-877-v1.patch, hbase-877-v2.patch
> HCM can not find the table with exception:
> org.apache.hadoop.hbase.TableNotFoundException: items
>         at org.apache.hadoop.hbase.client.HConnectionManager$TableServers.locateRegionInMeta(HConnectionManager.java:508)
>         at org.apache.hadoop.hbase.client.HConnectionManager$TableServers.locateRegion(HConnectionManager.java:460)
>         at org.apache.hadoop.hbase.client.HConnectionManager$TableServers.locateRegion(HConnectionManager.java:420)
>         at org.apache.hadoop.hbase.client.HTable.<init>(HTable.java:130)
>         at HBaseRef.<init>(HBaseRef.java:29)
>         at Import.<init>(Import.java:20)
>         at Import.main(Import.java:26)
> I have a fix already for this.  But the problem re-appeared after some time.  I have
no recreated it yet, but will post results in the morning.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message