Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
HBase >> mail # user >> HBase tunning

Copy link to this message
Re: HBase tunning

 Michael is right most parameters usually go one way or the other depending
on what you are trying to accomplish.

Memstore - raise for high write

Blockcache - raise for high reads

hbase blocksize - higher for sequential workload lower for random

client caching - lower for really wide rows/large cells and higher for tall
tables/small cells


On Fri, Oct 5, 2012 at 8:54 PM, Michael Segel <[EMAIL PROTECTED]>wrote:

> Depends.
> What sort of system are you tuning?
> Sorry, but we have to start somewhere and if we don't know what you have
> in terms of hardware, we don't have a good starting point.
> On Oct 5, 2012, at 7:47 PM, Mohit Anchlia <[EMAIL PROTECTED]> wrote:
> > Do most people start out with default values and then tune HBase? Or are
> > there some important configuration parameter that should always be
> changed
> > on client and the server?
Kevin O'Dell
Customer Operations Engineer, Cloudera