[HBASE-16008] A robust way deal with early termination of HBCK

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.4.0, 0.98.24, 2.0.0
• Component/s: hbck
• Hadoop Flags: Reviewed
• Assignee: Stephen Yuan Jiang
• Reporter: Stephen Yuan Jiang
• Created: 10/Jun/16 19:05
• Updated: 21/Dec/16 17:20
• Resolved: 24/Jul/16 03:22

Description

When HBCK is running, we want to disable Catalog Janitor, Balancer and Split/Merge. Today, the implementation is not robust. If HBCK is terminated earlier by Control-C, the changed state would not be reset to original.

HBASE-15406 was trying to solve this problem for Split/Merge switch. The implementation is complicated, and it did not solve CJ and Balancer.

The proposal to solve the problem is to use a znode to indicate that the HBCK is running. CJ, balancer, and Split/Merge switch all look for this znode before doing it operation.

Issue Links

• is duplicated by: HBASE-17342 HBCK should always try to restore balancer and catalogjanitor state
• is related to: HBASE-15406 Split / merge switch left disabled after early termination of hbck