Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id EB5BF17918 for ; Mon, 29 Sep 2014 10:13:36 +0000 (UTC) Received: (qmail 52012 invoked by uid 500); 29 Sep 2014 10:13:34 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 51900 invoked by uid 500); 29 Sep 2014 10:13:33 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 51628 invoked by uid 99); 29 Sep 2014 10:13:33 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 Sep 2014 10:13:33 +0000 Date: Mon, 29 Sep 2014 10:13:33 +0000 (UTC) From: "He Liangliang (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HBASE-12114) meta table cache is broken and cause access the wrong table MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 He Liangliang created HBASE-12114: ------------------------------------- Summary: 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 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)