I think splitting doesnt distribute your read load.

With read load distribution i mean you can access same data on let say 3
different nodes (RS) - if the dfs replication is set to 3. What Hbase doesnt
handle, am i right?





2011/5/6 Todd Lipcon <[email protected]>

> On Fri, May 6, 2011 at 11:19 AM, pob <[email protected]> wrote:
>
> >
> >
> > The data for those regions is replicated, but only 1 region server
> > > does the management of that data.
> > >
> > >
> > So does it mean, there isnt "scalling for reads"? {mean higher replica ->
> > better read throughput}
> >
>
> Reads are scaled by splitting regions and distributing them around multiple
> servers. If you have one super-hot row, it should fit in cache and give you
> some >20k reads/second. If you need more reads/sec on a single row than
> that, you'll need to add your own caching layer in front.
>
> -Todd
> --
> Todd Lipcon
> Software Engineer, Cloudera
>

Reply via email to