[
https://issues.apache.org/jira/browse/HBASE-877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12629055#action_12629055
]
Jonathan Gray commented on HBASE-877:
-------------------------------------
Just confirmed the reappearance.
Following a memcache flush of META, the identical exception is thrown:
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 HBaseRef.main(HBaseRef.java:15)
Either something is wrong with the flush itself, or someting is wrong when
reading from the flushed store. I imagine this will be another one or two line
fix adding the comparator to some SortedMaps.
> 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
>
>
> 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.
