[HBASE-15941] HBCK repair should not unsplit healthy splitted region

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0.0
• Fix Version/s: 1.4.0, 1.3.1, 1.2.6, 2.0.0
• Component/s: hbck

Release Note

A new option -removeParents is now available that will remove an old parent when two valid daughters for that parent exist and -fixHdfsOverlaps is used. If there is an issue trying to remove the parent from META or sidelining the parent from HDFS we will fallback to do a regular merge. For now this option only works when the overlap group consists only of 3 regions (a parent, daughter A and daughter B)

• Assignee: Esteban Gutierrez
• Reporter: Stephen Yuan Jiang
• Created: 02/Jun/16 03:26
• Updated: 09/Nov/17 19:11
• Resolved: 09/Mar/17 06:06

Description

Currently HBCK design in branch-1 has a flaw when repair option (the -fixHdfsOverlaps option specifically) is specified: it would wrongly merge split region (by looking at HDFS, it thinks that there exists overlapped regions - parent region and daughter regions covers the same key range, of course). See HBASE-15940 for details.

This JIRA tracks the improvement not-to-merge split region in HBCK repair.

Issue Links

• relates to: HBASE-15940 HBCK unnecessary moves reference files when a table has split region to fix non-existing overlap regions