[HBASE-21504] If enable FIFOCompactionPolicy, a compaction may write a "empty" hfile whose maxTimeStamp is long max. This kind of hfile will never be archived.

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.1.0
• Fix Version/s: 3.0.0-alpha-1, 2.2.0, 1.4.9, 2.1.2, 1.2.10, 2.0.4
• Component/s: Compaction
• Hadoop Flags: Reviewed
• Assignee: Zheng Hu
• Reporter: xuming
• Created: 21/Nov/18 12:54
• Updated: 01/Feb/19 20:15
• Resolved: 30/Nov/18 02:30

Description

When i use FIFOCompactionPolicy, and if all hfiles(>1) are TTL expired in a region, once we do a compaction on the region, the compaction policy will select the latest hfile to do compaction.But beacuse the latest hfile is already TTL expired, compactor only write a "empty" hfile(whose entry counter is 0 and maxTimeStamp is Long.MAX_VALUE) finally. Because maxTimeStamp is long max, so the "empty" hfile will never be TTL expired, more seriously we can not archive it by FIFOCompactionPolicy forever.

Issue Links

• links to: Review board