[HBASE-24950] Another solution for Splittable Meta

• Type: Umbrella
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Component/s: meta, Region Assignment
• Assignee: Duo Zhang
• Reporter: Duo Zhang
• Created: 25/Aug/20 11:24
• Updated: 10/Jan/21 03:54
• Resolved: 08/Jan/21 13:26

Description

For implementing splittable meta with a master local region to store the 'root table'.

Issue Links

• is part of: HBASE-25382 Super Split Meta
• is related to: HBASE-11288 Splittable Meta
• relates to: HBASE-24753 HA masters based on raft
• relates to: HBASE-24943 Cleanup unnecessary usages of MetaTableAccessor
• links to: Design Doc
• links to: GitHub Pull Request #2385

Sub-Tasks

• Make sure we can rollingupgrade from a non-splittable meta to splittable meta: Open
• Remove RegionInfoBuilder.FIRST_META_REGIONINFO: Resolved
• Implement meta merge: Resolved
• Introduce a CatalogAccessor: Resolved
• Store the locations of meta regions in master local store: Resolved
• Implement meta split: Resolved
• Implement CatalogJanitor for 'root table': Resolved
• Move the locateMeta logic from AsyncMetaRegionTableLocator to ConnectionRegistry: Resolved
• Introduce new master rpc methods to locate meta region through root region: Resolved
• Introduce a special CellComparator for master local region: Resolved
• Make HBCK2 work for 'root table': In Progress
• Avoid reset the backup master root cache every time when syncing: Resolved
• Attach a design doc to code base: Open
• Fan out the edits to root to backup masters: In Progress
• Mark all meta znode related methods as deprecated: Open