[
https://issues.apache.org/jira/browse/HBASE-18035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
huaxiang sun updated HBASE-18035:
---------------------------------
Release Note: When a client is configured to use meta replica, it sends
scan request to all meta replicas almost at the same time. Since meta replica
contains stale data, if result from one of replica comes back first, the client
may get wrong region locations. To fix this,
"hbase.client.meta.replica.scan.timeout" is introduced, a client will always
send to primary meta region first, wait the configured timeout for reply. If no
result is received, it will send request to replica meta regions. The unit for
"hbase.client.meta.replica.scan.timeout" is microsecond, the default value is
1000000 (1 second).
> Meta replica does not give any primaryOperationTimeout to primary meta region
> -----------------------------------------------------------------------------
>
> Key: HBASE-18035
> URL: https://issues.apache.org/jira/browse/HBASE-18035
> Project: HBase
> Issue Type: Bug
> Reporter: huaxiang sun
> Assignee: huaxiang sun
> Priority: Critical
> Fix For: 2.0.0, 1.4.0
>
> Attachments: 18035-branch-1-v001.patch, 18035.branch-1.v001.patch,
> 18035-unittest.patch, HBASE-18035-branch-1-v001.patch,
> HBASE-18035-master-v001.patch, HBASE-18035-master-v001.patch,
> HBASE-18035-master-v002.patch
>
>
> I was working on my unittest and it failed with TableNotFoundException. I
> debugged a bit and found out that for meta scan, it does not give any
> primaryOperationTimeout to primary meta region. This will be an issue as the
> meta replica will contain stale data and it is possible that the meta replica
> will return back first than primary.
> https://github.com/apache/hbase/blob/master/hbase-client/src/main/java/org/apache/hadoop/hbase/client/ConnectionImplementation.java#L823
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
