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 jdcryans@gmail.com designates
 209.85.216.41 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:content-type
         :content-transfer-encoding;
        b=eDE6jU0Uuhppqmdj+kkTdeuXz/XY3KwxfxIWKmh6Di33SKBfAeAoRcdKI8wmW7/tdd
         m+nzqNysRxgHp8lCvukZWMo0cnMkSq1d5cIZd99J2MR7dJ+iM+ZTFDLEHl84oR5+stL6
         btSR2PXjE8n35oXuN6sRP4L3kUZhcFh0Gsr4Y=
MIME-Version: 1.0
Sender: jdcryans@gmail.com
In-Reply-To: <95CC9FDB-2489-4A81-9091-63868E4FE05F@ucsfcti.org>
References: <FD6B30C3-5868-439A-BFC0-88F8E9FCD307@ucsfcti.org>
	<AANLkTinDU58607AjECP_rgf0ZLM=ryswQaEDnq0+8RJC@mail.gmail.com>
	<1D93502E-0A41-44DC-B5A5-43A74FE30497@ucsfcti.org>
	<AANLkTimjODhtZapPMv1g+xy=iq6h-2eno9_5z7KonPFe@mail.gmail.com>
	<95CC9FDB-2489-4A81-9091-63868E4FE05F@ucsfcti.org>
Date: Wed, 28 Jul 2010 08:36:22 -0700
Message-ID: <AANLkTi=ka-MRfqJM=3QiHHSBzdVXZ7oUQt7OxpcLhPri@mail.gmail.com>
Subject: Re: HBase minimum block size for sequential access
From: Jean-Daniel Cryans <jdcryans@apache.org>
To: user@hbase.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Forced actions are currently async, and there's no feedback (this is
currently being worked on for 0.90). I personnally look at the region
servers' web UI metrics, when the compaction queue is at 0 on most
machines then you know it's done. Ganglia makes this very easy as you
can graph that for all the machines at the same time.

Compacting files involves rewriting them (into new files), so it is
expected that the DFS usage grows during that time. Also files on HDFS
are put in a "garbage can" and are only really deleted later.

J-D

On Wed, Jul 28, 2010 at 8:22 AM, Andrew Nguyen
<andrew-lists-hbase@ucsfcti.org> wrote:
> So, I ran the following command in the shells:
>
> alter 'tablename', {NAME=3D>'cfname', BLOCKSIZE=3D>1045876}
> major_compact 'tablename'
>
> How do I know the major compact completed successfully? =A0I saw that the=
 number of regions has grown quite a bit but I'm not quite sure to know whe=
n it's all finished so that I can start the benchmarking. =A0Another thing =
that I noticed is after initiating the above, my DFS usage has continued to=
 grow. =A0I had 800g total, and 300g used. =A0After initiating the compacti=
on, I am now at 614M free... =A0Is this expected?
>
> Thanks!
>
> On Jul 27, 2010, at 10:13 AM, Jean-Daniel Cryans wrote:
>
>> After altering the table, issue a major compaction on it and
>> everything will be re-written with the new block size.
>
>
>
>