Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
Received-SPF: pass (athena.apache.org: domain of yongyong313@gmail.com
 designates 209.85.220.54 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAPBuyHRLEb0oAQOcARhgpqUZ60vTzMW2kLkBrFLMoZP5rUyGLA@mail.gmail.com>
References: 
 <CAPBuyHRLEb0oAQOcARhgpqUZ60vTzMW2kLkBrFLMoZP5rUyGLA@mail.gmail.com>
Date: Fri, 21 Feb 2014 11:38:07 +0100
Message-ID: 
 <CABALG=QokZZn10r_t8vre1iWmtx7kROHcqKxVm_55H9fP7KafQ@mail.gmail.com>
Subject: Re: When should we trigger a major compaction?
From: yonghu <yongyong313@gmail.com>
To: user@hbase.apache.org
Content-Type: multipart/alternative; boundary=047d7b15a9a5b1182804f2e8371a

--047d7b15a9a5b1182804f2e8371a
Content-Type: text/plain; charset=ISO-8859-1

Before you want to trigger major compaction, let's first explain why do we
need major compaction. The major compaction will cause
1. delete the data which is masked by tombstone;
2. delete the data which has expired ttl;
3. compact several small hfiles into a single larger one.

I didn't quite understand what do you mean by "use num of storefiles", why
this?


On Fri, Feb 21, 2014 at 10:50 AM, Ramon Wang <ramon@appannie.com> wrote:

> Hi Guys
>
> We disabled the automatically major compaction setting in our HBase
> cluster, so we want to something which can tell us when should we do major
> compaction, we were thinking to use "num of storefiles", but we cannot find
> any APIs or any JMX settings which can be used for it, please share us some
> ideas on how to do it, thanks in advance.
>
> Cheers
> Ramon
>

--047d7b15a9a5b1182804f2e8371a--