[jira] [Resolved] (HBASE-26618) Involving primary meta region in meta scan with CatalogReplicaLoadBalanceSimpleSelector

["Huaxiang Sun (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HBASE-26618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Huaxiang Sun resolved HBASE-26618.
----------------------------------
    Fix Version/s: 2.5.0
                   3.0.0-alpha-3
                   2.4.12
     Release Note: When META replica LoadBalance mode is enabled at client-side, clients will try to read from one META region first. If META location is from any non-primary META regions, in case of errors, it will fall back to the primary META region.
       Resolution: Fixed

> Involving primary meta region in meta scan with CatalogReplicaLoadBalanceSimpleSelector
> ---------------------------------------------------------------------------------------
>
>                 Key: HBASE-26618
>                 URL: https://issues.apache.org/jira/browse/HBASE-26618
>             Project: HBase
>          Issue Type: Improvement
>          Components: meta replicas
>    Affects Versions: 2.4.9
>            Reporter: Huaxiang Sun
>            Assignee: Huaxiang Sun
>            Priority: Minor
>             Fix For: 2.5.0, 3.0.0-alpha-3, 2.4.12
>
>
> In the current release with Meta replica LoadBalance mode, the primary meta region is not serving the meta scan (only meta replica region serves the read). When the result from meta replica region is stale, it will go to primary meta region for up-to-date location. 
> From our experience, the primary meta region serves very less read traffic, so it will be better to load balance read traffic across the primary meta region as well.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)