[HBASE-21217] Revisit the executeProcedure method for open/close region

• Type: Sub-task
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 3.0.0-alpha-1, 2.2.0
• Component/s: amv2, proc-v2
• Hadoop Flags: Reviewed
• Assignee: Duo Zhang
• Reporter: Duo Zhang
• Created: 21/Sep/18 02:08
• Updated: 06/Dec/18 17:59
• Resolved: 25/Sep/18 10:18

Description

Currently we just call openRegion and closeRegion directly, which is a bit buggy. For example, in order to not fail all the open region requests while there is only one failure, we will catch the exception and set a flag in the return value. But for executeProcedures call, the return value will be ignored, and we expect the openRegion method will always call reportRegionStateTransition to report the failure but in fact it does not...

And after HBASE-20881, we can confirm that the race could happen, where we send a close request to a region which is opening(HBASE-21199), and vice visa. So I think here we need to revisit the implementation of executeProcedures to make it more stable.

Issue Links

• contains: HBASE-21199 Race in region opening and load balancing can cause region stuck in RIT
• relates to: HBASE-21226 Revisit the close region related code at RS side
• relates to: HBASE-21237 Use CompatRemoteProcedureResolver to dispatch open/close region requests to RS
• relates to: HBASE-21227 Implement exponential retrying backoff for Assign/UnassignRegionHandler introduced in HBASE-21217
• links to: Review Board