Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id CB691D830 for ; Wed, 29 Aug 2012 18:36:09 +0000 (UTC) Received: (qmail 30442 invoked by uid 500); 29 Aug 2012 18:36:09 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 30400 invoked by uid 500); 29 Aug 2012 18:36:09 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 30385 invoked by uid 99); 29 Aug 2012 18:36:09 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 Aug 2012 18:36:09 +0000 Date: Thu, 30 Aug 2012 05:36:09 +1100 (NCT) From: "Ted Yu (JIRA)" To: issues@hbase.apache.org Message-ID: <1312423081.13160.1346265369561.JavaMail.jiratomcat@arcas> In-Reply-To: <4027823.34685.1342004614722.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Updated] (HBASE-6371) [89-fb] Level based compaction MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-6371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HBASE-6371: -------------------------- Summary: [89-fb] Level based compaction (was: Level based compaction) > [89-fb] Level based compaction > ------------------------------ > > Key: HBASE-6371 > URL: https://issues.apache.org/jira/browse/HBASE-6371 > Project: HBase > Issue Type: Improvement > Reporter: Akashnil > Assignee: Akashnil > > Currently, the compaction selection is not very flexible and is not sensitive to the hotness of the data. Very old data is likely to be accessed less, and very recent data is likely to be in the block cache. Both of these considerations make it inefficient to compact these files as aggressively as other files. In some use-cases, the access-pattern is particularly obvious even though there is no way to control the compaction algorithm in those cases. > In the new compaction selection algorithm, we plan to divide the candidate files into different levels according to oldness of the data that is present in those files. For each level, parameters like compaction ratio, minimum number of store-files in each compaction may be different. Number of levels, time-ranges, and parameters for each level will be configurable online on a per-column family basis. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira