hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matt Corgan <mcor...@hotpads.com>
Subject Re: Enable Compression on a Table
Date Wed, 19 Jan 2011 01:20:44 GMT
Another issue is that hbase doesn't currently merge small regions together.
 After doing something similar, my regions shrank from 125mb to 5mb (large
prefixes), and since it's time series data they will never grow again... not
technically a problem, but they're a little annoying to look at.

There is a Merge tool, but it requires hbase to be shutdown, and I think can
only merge 2 regions at a time which could take a while.

On Tue, Jan 18, 2011 at 8:10 PM, Stack <stack@duboce.net> wrote:

> Just offline the table, enable compression and all subsequent data
> flushed or compressed will be compressed.  It should just work.
> Things to look out for are making sure the lzo libs are installed on
> each node:
> http://people.apache.org/~stack/hbase-0.90.0-candidate-3/docs/important_configurations.html#lzo
> .
>  If running w/ 0.90.0, see a recent thread on memory issues to pick up
> a patch that seems to have quelled lzo issues when running hbase
> 0.90.0.
> St.Ack
> On Tue, Jan 18, 2011 at 4:57 PM, Peter Haidinyak <phaidinyak@local.com>
> wrote:
> > Ahoy Hoy,
> >        I have several tables I setup when I first learned HBase and I
> didn't enable compression. These tables are in use. I was wondering if it is
> possible to enable LZO compression 'on the fly'. I read you can disable the
> table and then alter it and I tried that on a test table and it seemed to
> work. If I enable compression on a large table what sort of issues should I
> look for? What are the recommended steps?
> >
> > Thanks
> >
> > -Pete
> >

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message