Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
Received-SPF: pass (nike.apache.org: domain of kevin.odell@cloudera.com
 designates 209.85.220.169 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CANNBgPK5NNkiMRuZhUPCx9iXdtqyX5BAq7xLHqUe8Q7pTrjZxw@mail.gmail.com>
References: 
 <CANNBgPK5NNkiMRuZhUPCx9iXdtqyX5BAq7xLHqUe8Q7pTrjZxw@mail.gmail.com>
Date: Wed, 12 Dec 2012 15:19:10 -0500
Message-ID: 
 <CAGngS9d+xDnaYMvMEm7QVv_2sfaenvzJ__JtJ6PABn3O2iTEAQ@mail.gmail.com>
Subject: Re: How to know it's time for a major compaction?
From: "Kevin O'dell" <kevin.odell@cloudera.com>
To: user@hbase.apache.org
Content-Type: multipart/alternative; boundary=f46d043893b3dddadf04d0ad8248

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

Otis,

I think it depends on your use case.  Some use cases are extremely
dependent on locality and latency, so they will major compact any region
the balancer has moved.  Some people follow the HFile count and will
trigger a major when there are x amount of files.  Others will just follow
best practices and do it daily.  Some do very little writes and only
compact once a week.

On Wed, Dec 12, 2012 at 3:15 PM, Otis Gospodnetic <
otis.gospodnetic@gmail.com> wrote:

> Hello,
>
> What are the main metrics/signals people use/look at to say "OK, I really
> need to do a major compaction now", other than "hm, performance is not
> good, let's try major compaction tonight"?
>
> Thanks,
> Otis
> --
> HBASE Performance Monitoring - http://sematext.com/spm/index.html
> Search Analytics - http://sematext.com/search-analytics/index.html
>


-- 
Kevin O'Dell
Customer Operations Engineer, Cloudera

--f46d043893b3dddadf04d0ad8248--