Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
Date: Mon, 4 Apr 2016 15:35:59 +0000 (UTC)
From: Sumit Nigam <sumit_only@yahoo.com.INVALID>
Reply-To: Sumit Nigam <sumit_only@yahoo.com>
To: User <user@hbase.apache.org>
Message-ID: <867548231.2580606.1459784159946.JavaMail.yahoo@mail.yahoo.com>
Subject: Major compaction
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_2580605_298901188.1459784159937"
References: 
 <867548231.2580606.1459784159946.JavaMail.yahoo.ref@mail.yahoo.com>

------=_Part_2580605_298901188.1459784159937
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi,
Are there major overheads to running major compaction frequently? As much a=
s I know, it produces one Hfile for a region and processes delete markers a=
nd 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.=
=C2=A0
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
------=_Part_2580605_298901188.1459784159937--