Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 31 Dec 2015 02:31:49 +0000 (UTC)
From: "Ted Yu (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12924912.1451489877000.32146.1451529109560@Atlassian.JIRA>
In-Reply-To: <JIRA.12924912.1451489877000@Atlassian.JIRA>
References: <JIRA.12924912.1451489877000@Atlassian.JIRA>
 <JIRA.12924912.1451489877645@arcas>
Subject: [jira] [Commented] (HBASE-15055) Major compaction is not triggered
 when both of TTL and hbase.hstore.compaction.max.size are set
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Ted Yu commented on HBASE-15055:
--------------------------------

{code}
139	      if (cfTtl != HConstants.FOREVER && oldest > cfTtl) {
{code}
If there is only one file satisfying the above condition among all the candidates, major compaction would be performed.

Is there more effective way to make major compaction pay off ?

> 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
>            Priority: Minor
>         Attachments: HBASE-15055-v1.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)