You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Zheng Hu (JIRA)" <ji...@apache.org> on 2018/11/21 13:44:00 UTC

[jira] [Commented] (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.

    [ https://issues.apache.org/jira/browse/HBASE-21504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16694717#comment-16694717 ] 

Zheng Hu commented on HBASE-21504:
----------------------------------

Interesting, Could you please provide some UT for the bug fix ?  I think it won't be too hard.  Thanks

> If enable FIFOCompactionPolicy, a compaction may write a "empty" hfile whose maxTimeStamp is long max. This kind of hfile will never be archived.
> -------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-21504
>                 URL: https://issues.apache.org/jira/browse/HBASE-21504
>             Project: HBase
>          Issue Type: Bug
>          Components: Compaction
>    Affects Versions: 2.1.0
>            Reporter: xuming
>            Priority: Critical
>         Attachments: 1.patch
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)