hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Duo Zhang (Jira)" <j...@apache.org>
Subject [jira] [Resolved] (HBASE-26235) We could start RegionServerTracker before becoming active master
Date Mon, 30 Aug 2021 04:24:00 GMT

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

Duo Zhang resolved HBASE-26235.
-------------------------------
    Fix Version/s: 3.0.0-alpha-2
                   2.5.0
     Hadoop Flags: Reviewed
       Resolution: Fixed

Pushed to master and branch-2.

Thanks [~niuyulin] for reviewing.

> We could start RegionServerTracker before becoming active master
> ----------------------------------------------------------------
>
>                 Key: HBASE-26235
>                 URL: https://issues.apache.org/jira/browse/HBASE-26235
>             Project: HBase
>          Issue Type: Sub-task
>          Components: master, Zookeeper
>            Reporter: Duo Zhang
>            Assignee: Duo Zhang
>            Priority: Major
>             Fix For: 2.5.0, 3.0.0-alpha-2
>
>
> The direct reason is that, after decoupling, HMaster does not extends HRegionServer,
so we do not have RegionServerAddressTracker now, so for backup masters we do not have a way
to get all the region server which means it can not serve as connection registry any more,
so we need to find a way to let backup masters to also have a way to get the region server
list.
> But in general, since we already have a class in HMaster which is used to track region
servers, we'd better reuse it. And after this change, the backup masters could also be used
as the fallback servers for getting region server list in HBASE-26220, which could also reduce
the load of active master.
> And this could also speed up the active master start process as we could save one zookeeper
scan when becoming active master.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message