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 mikael.sitruk@gmail.com
 designates 209.85.215.41 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAGpTDNdGy=UZvMDrzveBgi6dQ7DdOBsMsen7AOmv7ZwXHD+y3Q@mail.gmail.com>
References: <1D3249C5-D35F-4A5E-BA64-D9D02F987268@langisch.ch>
	<CAGpTDNdGy=UZvMDrzveBgi6dQ7DdOBsMsen7AOmv7ZwXHD+y3Q@mail.gmail.com>
Date: Tue, 24 Jan 2012 15:34:16 +0200
Message-ID: 
 <CAPpvZ9ChZiEny__Kf643-8pAHPmeUtcgzgQctdJDyhvjr0SC5w@mail.gmail.com>
Subject: Re: early memstore flushings
From: Mikael Sitruk <mikael.sitruk@gmail.com>
To: user@hbase.apache.org
Content-Type: multipart/alternative; boundary=f46d04016a691a2eac04b74634ca

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

Your memstore may be flushed also in case the number of HLog reach its
maximum, in this case your memstore may not reach the max size allocated
for it.

Mikael.S

On Tue, Jan 24, 2012 at 1:00 AM, Jean-Daniel Cryans <jdcryans@apache.org>wrote:

> It flushes when it reaches the memstore size, not plus the global max
> memstore size.
>
> J-D
>
> On Mon, Jan 23, 2012 at 2:50 PM, Yves Langisch <yves@langisch.ch> wrote:
> > Hi,
> >
> > I'm currently looking through all the metrics hbase provides and I don't
> understand the memstore flushing behavior I see. I thought the memstore is
> not flushed until it reaches the maximum memstore size plus the flush size.
> In my case this would be 1.6GB+128MB. But I see the following graph:
> >
> > http://dl.dropbox.com/u/395716/memstore.gif
> >
> > What's the reason for such early flushes?
> >
> > -
> > Yves
>


-- 
Mikael.S

--f46d04016a691a2eac04b74634ca--