[jira] [Commented] (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:comment-tabpanelfocusedCommentId=14153265#comment-14153265 ] He Liangliang commented on HBASE-12114: --- I will have a look and add a test case for this when back from vacation. 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)
[jira] [Commented] (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:comment-tabpanelfocusedCommentId=14152202#comment-14152202 ] Hudson commented on HBASE-12114: SUCCESS: Integrated in HBase-0.94 #1426 (See [https://builds.apache.org/job/HBase-0.94/1426/]) HBASE-12114 Meta table cache hashing may access the wrong table. (He Liangliang) (larsh: rev ffd3c383abb863c29b00b2e016d8116d7f9c2c1a) * src/main/java/org/apache/hadoop/hbase/client/HConnectionManager.java 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)
[jira] [Commented] (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:comment-tabpanelfocusedCommentId=14152210#comment-14152210 ] Hudson commented on HBASE-12114: SUCCESS: Integrated in HBase-0.94-JDK7 #195 (See [https://builds.apache.org/job/HBase-0.94-JDK7/195/]) HBASE-12114 Meta table cache hashing may access the wrong table. (He Liangliang) (larsh: rev ffd3c383abb863c29b00b2e016d8116d7f9c2c1a) * src/main/java/org/apache/hadoop/hbase/client/HConnectionManager.java 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)
[jira] [Commented] (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:comment-tabpanelfocusedCommentId=14152325#comment-14152325 ] Hudson commented on HBASE-12114: SUCCESS: Integrated in HBase-0.94-security #541 (See [https://builds.apache.org/job/HBase-0.94-security/541/]) HBASE-12114 Meta table cache hashing may access the wrong table. (He Liangliang) (larsh: rev ffd3c383abb863c29b00b2e016d8116d7f9c2c1a) * src/main/java/org/apache/hadoop/hbase/client/HConnectionManager.java 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)
