You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Ted Yu (JIRA)" <ji...@apache.org> on 2014/09/29 16:31:34 UTC

[jira] [Commented] (HBASE-12114) meta table cache is broken and cause access the wrong table

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

Ted Yu commented on HBASE-12114:
--------------------------------

Can you add a test showing that there is no collision for the above two table names ?

> meta table cache is broken and cause access the wrong table
> -----------------------------------------------------------
>
>                 Key: HBASE-12114
>                 URL: https://issues.apache.org/jira/browse/HBASE-12114
>             Project: HBase
>          Issue Type: Bug
>          Components: Client
>            Reporter: He Liangliang
>            Assignee: He Liangliang
>             Fix For: 0.94.24
>
>         Attachments: HBASE-12114.patch
>
>
> The cache key used a hash code from a weak hash algorithm Bytes.mapKey(tableName), which can cause collisions in a quite high probability then make the client accessing a wrong region from another table.
> Example: "2fx0" and "2fvn"



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)