[HBASE-24723] Distributing ROOT Region load

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Assignee: Unassigned
• Reporter: Michael Stack
• Created: 13/Jul/20 15:51
• Updated: 21/Jul/20 02:10

Description

HBASE-11288 'Splittable Meta' progress keeps getting hung up on how to cache the 'root' table – the first table in the hierarchy of lookups locating user-data in a Table Region. The 'root' table is not splittable by design so its load can not be spread about the cluster by splitting the hot Region as we would usually do.

This issue is about listing out requirements, sketching possible approaches, and then getting agreement ahead of implementation as subtasks.

In particular, an approach that would work whether the Region to be cached is master-based or hosted by a RegionServer (see design attached to HBASE-11288 for elaboration) would be preferred since then we can separate discussion of cache from the HBASE-11288 'split meta' discussion.

Issue Links

• is related to: HBASE-24459 Move the locateMeta logic from AsyncMetaRegionTableLocator to ConnectionRegistry
• is related to: HBASE-11288 Splittable Meta
• links to: ROOT Region and 'hotspotting'