Hi anand,
Try increasing your rowBatchSize() using hbaseString() function.This
will increase the no.of rows fetched during a single RPC call. This might
improve the speed of retrieval.
Cheers,
Manoj.P
On Mon, Jul 2, 2012 at 10:53 AM, AnandaVelMurugan Chandra Mohan <
ananthu2...@gmail.com> w
Thanks for the suggestions. I will fix my cluster set up.
On Fri, Jun 29, 2012 at 8:01 PM, Alex Baranau wrote:
> 1. Theoretically, scanning on each regionserver with cps might help you, I
> think. But this is not a good way to go with anyways...
>
> 2. Table is created on the cluster, not on indi
1. Theoretically, scanning on each regionserver with cps might help you, I
think. But this is not a good way to go with anyways...
2. Table is created on the cluster, not on individual RSs. Though table
Regions are assigned to specific RSs. While creating the table you will be
talking to master no
Hi,
Thanks for the suggestions. I too observed that scan in hbase shell takes
almost same time.
I would try to fix my HBase cluster set up.
Meanwhile, I have two questions
- Will endpoint coprocessors help my cause? (In case cluster
modification is beyond my control, I would lean on this
I'd agree that HBase is not designed to be run in such "inter-continental"
single cluster setup. Latency in communication between nodes (slaves) is
vital for the health of the cluster.
So, the short answer: just don't do it that way.
What is the reason to have nodes in these locations?
Alex Bara
Hi Anand,
Using HBase/Hadoop for some tests for weeks now, I figure that it's
very network consuming. Using it with a wireless computer was VERY
slow. I moved to a 1000BASE-T network and it's now WAY better. I'm not
sure having the nodes shared that way on internet will be efficient.
Have you tri
