[
https://issues.apache.org/jira/browse/HBASE-514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Duxbury updated HBASE-514:
--------------------------------
Fix Version/s: 0.1.0
Status: Patch Available (was: Open)
Please review the 0.1 patch. I will put together a trunk patch when I am
convinced the 0.1 is sufficient.
> table 'does not exist' when it does
> -----------------------------------
>
> Key: HBASE-514
> URL: https://issues.apache.org/jira/browse/HBASE-514
> Project: Hadoop HBase
> Issue Type: Bug
> Components: client
> Affects Versions: 0.16.0
> Reporter: stack
> Fix For: 0.1.0
>
> Attachments: 514-0.1.patch, region-v2.patch
>
>
> This one I've seen a few times. In hql, I do show tables and it shows my
> table. I then try to do a select against the table and hql reports table
> does not exist. Digging, whats happening is that the getClosest facility is
> failing to find the first table region in the .META. table. I hacked up a
> region reading tool -- attached (for 0.1 branch) -- and tried it against but
> a copy and the actual instance of the region and it could do the getClosest
> fine. I'm pretty sure I restarted the HRS and when it came up again, the
> master had given it again the .META. and again was failing to find the first
> region in the table (Looked around in server logs and it seemed 'healthy').
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
