-Re: Hbase Compression
Jean-Daniel Cryans 2013-09-24, 17:19
On flushing we do some cleanup, like removing deleted data that was already
in the MemStore or extra versions. Could it be that you are overwriting
recently written data?
48MB is the size of the Memstore that accumulated while the flushing
On Tue, Sep 24, 2013 at 3:50 AM, aiyoh79 <[EMAIL PROTECTED]> wrote:
> I am using hbase 0.94.11 and i feel a bit confuse when looking at the log
> file below:
> 13/09/24 13:11:00 INFO regionserver.Store: Flushed , sequenceid=687077,
> memsize> 122.1m, into tmp file
> 13/09/24 13:11:00 INFO regionserver.Store: Added
> e05d3, entries=432620, sequenceid=687077, filesize=64.4m
> 13/09/24 13:11:00 INFO regionserver.HRegion: Finished memstore flush of
> 134402240, currentsize=48.0m/50366240 for region
> 895119.b19289cf9b1400c6daddc347337bac03. in 1163ms, sequenceid=687077,
> n requested=false
> It seems like it will first flush into a tmp file and the memsize is
> but when it finally added, the size is 64.4m. Lastly, there are 2 more
> parameters which is 128.2m and 48.0m for currentsize.
> I never specify hbase.regionserver.codecs preperty in my hbase-site.xml
> file, so is the size difference still because of compression?
> View this message in context:
> Sent from the HBase User mailing list archive at Nabble.com.