[
https://issues.apache.org/jira/browse/HBASE-29191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang resolved HBASE-29191.
-------------------------------
Fix Version/s: 2.7.0
3.0.0-beta-2
2.6.3
2.5.12
Hadoop Flags: Reviewed
Resolution: Fixed
I think it's no harm to use metaReadRpcTimeout here, although this is for
reading connection registry, not reading meta.
So I commit the change to all active branches.
Thanks [~yiran]!
> Use MetaRpcReadTimeout when accessing Meta replicas
> ---------------------------------------------------
>
> Key: HBASE-29191
> URL: https://issues.apache.org/jira/browse/HBASE-29191
> Project: HBase
> Issue Type: Improvement
> Affects Versions: 2.4.0
> Reporter: YR
> Assignee: YR
> Priority: Trivial
> Labels: pull-request-available
> Fix For: 2.7.0, 3.0.0-beta-2, 2.6.3, 2.5.12
>
>
> We should use dedicated timeout settings when accessing the Meta table
> replicas
> {code:java}
> // conn.connConf.getReadRpcTimeoutNs() in AsyncNonMetaRegionLocator &
> ConnectionImplementation
> try {
> RegionLocations metaLocations =
> conn.registry.getMetaRegionLocations()
> .get(conn.connConf.getMetaReadRpcTimeoutNs(),
> TimeUnit.NANOSECONDS);
> numOfReplicas = metaLocations.size();
> } catch (Exception e) {
> LOG.error("Failed to get table {}'s region replication, ",
> META_TABLE_NAME, e);
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
