[
https://issues.apache.org/jira/browse/HBASE-21504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16704501#comment-16704501
]
Hudson commented on HBASE-21504:
--------------------------------
Results for branch branch-1.2
[build #571 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.2/571/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.2/571//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk7 checks{color}
-- For more information [see jdk7
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.2/571//JDK7_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.2/571//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 source release artifact{color}
-- Something went wrong with this stage, [check relevant console
output|${BUILD_URL}/console].
> 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, 1.3.3, 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)
