[HBASE-24943] Cleanup unnecessary usages of MetaTableAccessor

• Type: Umbrella
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: meta
• Assignee: Duo Zhang
• Reporter: Duo Zhang
• Created: 24/Aug/20 13:23
• Updated: 14/Oct/20 01:42

Description

For simplify the implementation of splittable meta.

In general, MetaTableAccessor can not deal with the catalog information for meta itself, even if we introduce a general root table, we could make it also deal with the catalog information for meta, but then we still need to deal with root...

Let's change to use other APIs if possible, for example, when getting all region locations, just use RegionLocator instead of MetaTableAccessor.

Issue Links

• is related to: HBASE-24950 Another solution for Splittable Meta

Sub-Tasks

• Remove MetaTableAccessor.getTableRegionsAndLocations in hbase-rest module: Resolved
• Remove MetaTableAccessor.getRegionCount: Resolved
• Remove MetaTableAccessor.tableExists: Resolved
• Use RegionLocator instead of MetaTableAccessor's get regions and locations methods if possible: Open
• Move meta edit methods from MetaTableAccessor to RegionStateStore: In Progress
• Move ReplicationBarrier related methods to a separated class: Resolved
• Move delete region info related methods to RegionStateStore: Resolved
• Remove the usage of MetaTableAccessor in hbase-balancer: Open