[
https://issues.apache.org/jira/browse/HBASE-16512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15449581#comment-15449581
]
Hudson commented on HBASE-16512:
--------------------------------
FAILURE: Integrated in Jenkins build HBase-0.98-on-Hadoop-1.1 #1266 (See
[https://builds.apache.org/job/HBase-0.98-on-Hadoop-1.1/1266/])
HBASE-16512 when locate meta region, we should respect the param (apurtell: rev
381fcdcfdfd3bac274090cacfeea7c132ba8dd1e)
* (edit)
hbase-client/src/main/java/org/apache/hadoop/hbase/client/HConnectionManager.java
> when locate meta region, we should respect the param "useCache" passed in on
> 0.98
> ---------------------------------------------------------------------------------
>
> Key: HBASE-16512
> URL: https://issues.apache.org/jira/browse/HBASE-16512
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.98.21
> Reporter: Heng Chen
> Assignee: Heng Chen
> Fix For: 0.98.22
>
> Attachments: HBASE-16512.0.98.patch, HBASE-16512_0.98.patch
>
>
> we found that when RS with meta crash, client will retry the same request,
> but it still use the original meta location in cache, so all request retried
> will failed.
> Notice the code in HConnectionMananger#locateRegionInMeta, the "useCache"
> passed in is not used when try to found the meta region.
> {code}
> private HRegionLocation locateRegionInMeta(final TableName parentTable,
> final TableName tableName, final byte [] row, boolean useCache,
> Object regionLockObject, boolean retry)
> throws IOException {
> ......
> for (int tries = 0; true; tries++) {
> .....
> HRegionLocation metaLocation = null;
> try {
> // locate the meta region
> metaLocation = locateRegion(parentTable, metaKey, true, false);
> //NOTICE: we should honor the "useCache" passed in when locate the meta
> region.
> ....
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
