hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mohit Anchlia <mohitanch...@gmail.com>
Subject Re: HBase tunning
Date Sat, 06 Oct 2012 02:16:24 GMT
I have a timeseries data and each row has upto 1000 cols. I just started
with defaults and I have not tuned any parameters on client or server. My
reads are reading all the cols in a row. But request for a given row is
completely random.

On Fri, Oct 5, 2012 at 6:05 PM, Kevin O'dell <kevin.odell@cloudera.com>wrote:

> Mohit,
>
>  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
>
> etc.
>
> On Fri, Oct 5, 2012 at 8:54 PM, Michael Segel <michael_segel@hotmail.com
> >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 <mohitanchlia@gmail.com>
> 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
>

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