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

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

[jira] [Updated] (HBASE-21504) When Using FIFOCompactionPolicy, in some case, doing a compaction will write a initial hfile which will never be TTL expired

     [ https://issues.apache.org/jira/browse/HBASE-21504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

xuming updated HBASE-21504:
---------------------------
    Summary: When Using FIFOCompactionPolicy, in some case, doing a compaction will write a initial hfile which will never be TTL expired  (was: Using FIFOCompactionPolicy, a compact my write a empty HFile. And the HFile will never be  expired )

> When Using FIFOCompactionPolicy, in some case, doing a compaction will write a initial hfile which will never be TTL expired
> ----------------------------------------------------------------------------------------------------------------------------
>
>                 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 hfile is already TTL expired, compactor will write a new hfile(whose entry counter is 0 and maxTimeStamp is Long.MAX_VALUE). The new hfile will never be TTL expired, so we can never remove it by FIFOCompactionPolicy.



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