[HBASE-23633] Find a way to handle the corrupt recovered hfiles

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 3.0.0-alpha-1, 2.3.0
• Fix Version/s: 3.0.0-alpha-1, 2.3.0
• Component/s: MTTR, wal
• Assignee: Pankaj Kumar
• Reporter: Guanghao Zhang
• Created: 03/Jan/20 09:08
• Updated: 08/Apr/20 22:43
• Resolved: 22/Mar/20 15:07

Description

Copy the comment from PR review.

 

If the file is a corrupt HFile, an exception will be thrown here, which will cause the region to fail to open.
Maybe we can add a new parameter to control whether to skip the exception, similar to recover edits which has a parameter "hbase.hregion.edits.replay.skip.errors";

 

Regions that can't be opened because of detached References or corrupt hfiles are a fact-of-life. We need work on this issue. This will be a new variant on the problem – i.e. bad recovered hfiles.

On adding a config to ignore bad files and just open, thats a bit dangerous as per @infraio .... as it could mean silent data loss.

Issue Links

• relates to: HBASE-23286 Improve MTTR: Split WAL to HFile
• links to: GitHub Pull Request #1233

Sub-Tasks

• Add ut for loading the corrupt recovered hfiles: Resolved