[HBASE-26640] Reimplement master local region initialization to better work with SFT

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.5.0, 3.0.0-alpha-3
• Component/s: master, RegionProcedureStore
• Hadoop Flags: Reviewed

Release Note

Introduced a 'hbase.master.store.region.file-tracker.impl' config to specify the store file tracker implementation for master local region.

If not present, master local region will use the cluster level store file tracker implementation.

• Assignee: Duo Zhang
• Reporter: Duo Zhang
• Created: 02/Jan/22 07:55
• Updated: 27/Jul/22 23:44
• Resolved: 24/Feb/22 03:16

Description

It is not like a normal region where we have a TableDescriptor so it can store the SFT implementation of its own. In the current implementation, if we change the global SFT configuration, the SFT implementation of the master local reigon will be changed and cause data loss.

First I think we could hard coded it to use DefaultSFT. The region is small and will not cause too much performance impact. Then we could find a way to manage the SFT implementation of it.

====== Update ======

The initialization of master local region depends on renaming, which can not work well on OSS. So we should also change it. The basic idea is to touch a '.initialized' file to indicate it is initialized. Need to consider how to migrate from the existing master local region where it does not have this file.

And we could also store the TableDescriptor on file system, so we can determine whether this is a SFT change. If so, we should do the migration before actually opening the master local region.

Issue Links

• is related to: HBASE-27251 Rolling back from 2.5.0-SNAPSHOT to 2.4.13 fails due to `File does not exist: /hbase/MasterData/data/master/store/.initialized/.regioninfo`
• links to: GitHub Pull Request #4009
• links to: GitHub Pull Request #4111