[HBASE-19529] Handle null states in AM

• Type: Sub-task
• Status: Resolved
• Priority: Critical
• Resolution: Won't Fix
• Assignee: Unassigned
• Reporter: Apekshit Sharma
• Created: 15/Dec/17 22:37
• Updated: 16/Dec/23 09:40
• Resolved: 16/Dec/23 09:40

Description

From debugging in HBASE-19457, found some questions that need concrete answers:
1) What does a region state of null in meta means? Currently AM treats it as OFFLINE
2) What does a table state of null in meta means? Currently TSM treats it as ENABLED.

More importantly, we need to fix holes in AM so that our state machine is well defined and doesn't end up in these uncertainties.
Figuring out answers to above questions will help in that direction.

Issue Links

• relates to: HBASE-19915 From split/ merge procedures daughter/ merged regions get created in OFFLINE state