[
https://issues.apache.org/jira/browse/HBASE-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12578540#action_12578540
]
Bryan Duxbury commented on HBASE-514:
-------------------------------------
So perhaps the most palatable solution is to clearly specify that
getClosestRowBefore is only meant to be used on the .META. table, since it has
very simple characteristics.
In particular, writes in .META. (or -ROOT-, used interchangeably) will always
be written with the latest timestamp, meaning that older map files will never
have future-dated information. Then, we can start with the memcache, then begin
with the oldest map file and advance forward searching for better qualified
rows and excluding rows that have been deleted in later map files.
> 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
> Attachments: 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.
