[HBASE-17712] Remove/Simplify the logic of RegionScannerImpl.handleFileNotFound

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.4.0, 2.0.0
• Fix Version/s: 1.4.0, 2.0.0
• Component/s: regionserver
• Hadoop Flags: Reviewed
• Release Note: Add a config named 'hbase.hregion.unassign.for.fnfe'. It is used to control whether to reopen a region when hitting FileNotFoundException. The default value is true.
• Assignee: Duo Zhang
• Reporter: Duo Zhang
• Created: 01/Mar/17 07:20
• Updated: 13/Sep/17 07:38
• Resolved: 10/Mar/17 08:43

Description

It is introduced in HBASE-13651 and the logic became much more complicated after HBASE-16304 due to a dead lock issue. It is really tough as sequence id is involved in and the method we called is used to serve secondary replica originally which does not handle write.

In fact, in 1.x release, the problem described in HBASE-13651 is gone. Now we will write a compaction marker to WAL before deleting the compacted files. We can only consider a RS as dead after its WAL files are all closed so if the region has already been reassigned the compaction will fail as we can not write out the compaction marker.

So theoretically, if we still hit FileNotFound exception, it should be a critical bug which means we may loss data. I do not think it is a good idea to just eat the exception and refresh store files. Or even if we want to do this, we can just refresh store files without dropping memstore contents. This will also simplify the logic a lot.

Suggestions are welcomed.

Issue Links

• relates to: HBASE-18786 FileNotFoundException should not be silently handled for primary region replicas
• relates to: HBASE-18353 Enable TestCorruptedRegionStoreFile that were disabled by Proc-V2 AM in HBASE-14614
• links to: reviewboard