[
https://issues.apache.org/jira/browse/HBASE-877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12629825#action_12629825
]
stack commented on HBASE-877:
-----------------------------
The change passing a comparator to Mapfile broke the BeforeThisStoreKey trick.
BeforeThisStoreKey is an HStoreKey instance that has no equal; it returns -1
when compared to an "equal" instance. Its passed to Mapfile.next when we want
to find the closest before. Without this trick, the call to get closest before
always returned same result -- the infinite looping that we were seeing.
My overnight tests all completed (The amended PE to make binary keys, an
optional flush set to ten minutes, doing sequential write followed by random
read suite; previous we'd fail after second optional flush about 20 minutes in).
> 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-v10.patch,
> hbase-877-v2.patch, hbase-877-v3.patch, hbase-877-v4.patch,
> hbase-877-v5.patch, hbase-877-v6.patch, hbase-877-v8.patch, hbase-877-v9.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.
