You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Lars Hofhansl (JIRA)" <ji...@apache.org> on 2014/09/29 20:36:34 UTC
[jira] [Resolved] (HBASE-12114) Meta table cache hashing may access
the wrong table
[ https://issues.apache.org/jira/browse/HBASE-12114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Hofhansl resolved HBASE-12114.
-----------------------------------
Resolution: Fixed
Committed to 0.94
Thanks for the patch [~heliangliang].
If you get time to think of a test, we can add one in another jira.
> Meta table cache hashing may 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)