[
https://issues.apache.org/jira/browse/HBASE-18005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16039407#comment-16039407
]
Hudson commented on HBASE-18005:
--------------------------------
FAILURE: Integrated in Jenkins build HBase-1.4 #761 (See
[https://builds.apache.org/job/HBase-1.4/761/])
HBASE-18005 read replica: handle the case that region server hosting (tedyu:
rev 39e8e2fb5898847ef41068cdf46a660e66389541)
* (edit)
hbase-client/src/main/java/org/apache/hadoop/hbase/client/MetaCache.java
* (edit)
hbase-client/src/main/java/org/apache/hadoop/hbase/client/RpcRetryingCallerWithReadReplicas.java
* (edit)
hbase-client/src/main/java/org/apache/hadoop/hbase/client/ConnectionManager.java
* (edit)
hbase-client/src/main/java/org/apache/hadoop/hbase/client/ScannerCallableWithReplicas.java
* (edit)
hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestReplicaWithCluster.java
> read replica: handle the case that region server hosting both primary replica
> and meta region is down
> -----------------------------------------------------------------------------------------------------
>
> Key: HBASE-18005
> URL: https://issues.apache.org/jira/browse/HBASE-18005
> Project: HBase
> Issue Type: Bug
> Reporter: huaxiang sun
> Assignee: huaxiang sun
> Fix For: 2.0.0, 1.4.0
>
> Attachments: HBASE-18005-branch-1-v001.patch,
> HBASE-18005-master-001.patch, HBASE-18005-master-002.patch,
> HBASE-18005-master-003.patch, HBASE-18005-master-004.patch,
> HBASE-18005-master-005.patch, HBASE-18005-master-006.patch
>
>
> Identified one corner case in testing that when the region server hosting
> both primary replica and the meta region is down, the client tries to reload
> the primary replica location from meta table, it is supposed to clean up only
> the cached location for specific replicaId, but it clears caches for all
> replicas. Please see
> https://github.com/apache/hbase/blob/master/hbase-client/src/main/java/org/apache/hadoop/hbase/client/ConnectionImplementation.java#L813
> Since it takes some time for regions to be reassigned (including meta
> region), the following may throw exception
> https://github.com/apache/hbase/blob/master/hbase-client/src/main/java/org/apache/hadoop/hbase/client/RpcRetryingCallerWithReadReplicas.java#L173
> This exception needs to be caught and it needs to get cached location (in
> this case, the primary replica's location is not available). If there are
> cached locations for other replicas, it can still go ahead to get stale
> values from secondary replicas.
> With meta replica, it still helps to not clean up the caches for all replicas
> as the info from primary meta replica is up-to-date.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
