You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2018/12/14 23:56: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=16721892#comment-16721892 ]
Hudson commented on HBASE-21504:
--------------------------------
SUCCESS: Integrated in Jenkins build HBase-1.3-IT #512 (See [https://builds.apache.org/job/HBase-1.3-IT/512/])
Revert "HBASE-21504 If enable FIFOCompactionPolicy, a compaction may (apurtell: rev d2c1deef1c1dd858fcf0b110753e57be466e676f)
* (edit) hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/compactions/TestFIFOCompactionPolicy.java
* (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/compactions/FIFOCompactionPolicy.java
> 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
> Assignee: Zheng Hu
> Priority: Critical
> Fix For: 3.0.0, 1.5.0, 2.2.0, 1.4.9, 2.1.2, 2.0.4
>
> Attachments: 1.patch, HBASE-21504.v1.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)