[HBASE-21395] Abort split/merge procedure if there is a table procedure of the same table going on

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.1.0, 2.0.2
• Fix Version/s: 2.0.3, 2.1.2
• Assignee: Allan Yang
• Reporter: Allan Yang
• Created: 26/Oct/18 15:32
• Updated: 12/Nov/18 03:04
• Resolved: 05/Nov/18 12:12

Description

In my ITBLL, I often see that if split/merge procedure and table procedure(like ModifyTableProcedure) happen at the same time, and since there some race conditions between these two kind of procedures, causing some serious problems. e.g. the split/merged parent is bought on line by the table procedure or the split merged region making the whole table procedure rollback.
Talked with Apache9 offline today, this kind of problem was solved in branch-2+ since There is a fence that only one RTSP can agianst a single region at the same time.
To keep out of the mess in branch-2.0 and branch-2.1, I added a simple safe fence in the split/merge procedure: If there is a table procedure going on against the same table, then abort the split/merge procedure. Aborting the split/merge procedure at the beginning of the execution is no big deal, compared with the mess it will cause...

Issue Links

• relates to: HBASE-20671 Merged region brought back to life causing RS to be killed by Master