Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
MIME-Version: 1.0
In-Reply-To: <867548231.2580606.1459784159946.JavaMail.yahoo@mail.yahoo.com>
References: 
 <867548231.2580606.1459784159946.JavaMail.yahoo.ref@mail.yahoo.com>
 <867548231.2580606.1459784159946.JavaMail.yahoo@mail.yahoo.com>
From: Esteban Gutierrez <esteban@cloudera.com>
Date: Mon, 4 Apr 2016 08:55:01 -0700
Message-ID: 
 <CALPvCiAMfT+mMY8oTGwkHF6vR-gMWPBB4Gd0TkFsVH18hiRmcA@mail.gmail.com>
Subject: Re: Major compaction
To: "user@hbase.apache.org" <user@hbase.apache.org>,
 Sumit Nigam <sumit_only@yahoo.com>
Content-Type: multipart/alternative; boundary=001a11401ba83e2393052faac153

--001a11401ba83e2393052faac153
Content-Type: text/plain; charset=UTF-8

Hello Sumit,

Ideally you shouldn't be triggering major compactions that frequently since
minor compactions should be taking care of reducing the number of store
files. The caveat of doing it more frequently is the additional
disk/network I/O.

Can you please elaborate more on "reduce stress by spreading the load." Is
there anything else you are seeing in your cluster that is suggesting to
you to lower the period for major compactions?

esteban.

--
Cloudera, Inc.


On Mon, Apr 4, 2016 at 8:35 AM, Sumit Nigam <sumit_only@yahoo.com.invalid>
wrote:

> Hi,
> Are there major overheads to running major compaction frequently? As much
> as I know, it produces one Hfile for a region and processes delete markers
> and version related drops. So, if this process has happened once say. a few
> mins back then another major compaction should ideally not cause much harm.
> Why I am trying to understand this is because Hbase also sets it to 24
> hour default (for time based compaction) and I am looking to lower it to
> say 20 mins to reduce stress by spreading the load.
> Or am I completely off-track?
> Thanks,Sumit

--001a11401ba83e2393052faac153--