[
https://issues.apache.org/jira/browse/HBASE-15055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15089327#comment-15089327
]
Ted Yu commented on HBASE-15055:
--------------------------------
Without the floating point fix, I got:
{code}
testMajorCompactionWithTtlAndCompactionMaxSize2(org.apache.hadoop.hbase.regionserver.TestMajorCompaction)
Time elapsed: 11.038 sec <<< FAILURE!
java.lang.AssertionError: expected:<1> but was:<2>
...
testMajorCompactionWithTtlAndCompactionMaxSize3(org.apache.hadoop.hbase.regionserver.TestMajorCompaction)
Time elapsed: 11.354 sec <<< FAILURE!
java.lang.AssertionError: expected:<1> but was:<3>
{code}
Do we need two subtests shown above ?
I wonder if one of them suffices.
Thanks for the persistence, Eungsop.
> Major compaction is not triggered when both of TTL and
> hbase.hstore.compaction.max.size are set
> -----------------------------------------------------------------------------------------------
>
> Key: HBASE-15055
> URL: https://issues.apache.org/jira/browse/HBASE-15055
> Project: HBase
> Issue Type: Bug
> Reporter: Eungsop Yoo
> Assignee: Eungsop Yoo
> Priority: Minor
> Attachments: HBASE-15055-v1.patch, HBASE-15055-v2.patch,
> HBASE-15055-v3.patch, HBASE-15055-v4.patch, HBASE-15055-v5.patch,
> HBASE-15055-v6.patch, HBASE-15055-v7.patch, HBASE-15055-v8.patch,
> HBASE-15055.patch
>
>
> Some large files may be skipped by hbase.hstore.compaction.max.size in
> candidate selection. It causes skipping of major compaction. So the TTL
> expired records are still remained in the disks and keep consuming disks.
> To resolve this issue, I suggest that to skip large files only if there is no
> TTL expired record.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
