We ran into that as well.
You need to make sure when sending List of Put that all rowkeys there are
unique, otherwise as Ted said, the for loop acquiring locks will run
multiple times for rowkey which repeats it self
On Sunday, May 12, 2013, Ted Yu wrote:
> High collision rate means high contenti
High collision rate means high contention at taking the row locks.
This results in poor write performance.
Cheers
On May 11, 2013, at 7:14 PM, Pal Konyves wrote:
> Hi,
>
> I decided not to make any tuning, because my whole project is about
> experimenting with HBase (it's a scool project). H
Hi,
I decided not to make any tuning, because my whole project is about
experimenting with HBase (it's a scool project). However it turned out that
my sample data generated lots of rowkey collisions. 4 million inserts only
resulted in about 5000 rows. The data were different though in the columns.
What I am saying is that by default, you get two mappers per node.
x4large can run HBase w more mapred slots, so you will want to tune the
defaults based on machine size. Not just mapred, but also HBase stuff too. You
need to do this on startup of EMR cluster though...
Sent from a remote device.
Principally I chose to use Amazon, because they are supposedly high
performance, and what more important is: HBase is already set up if I chose
it as an EMR Workflow. I wanted to save up the time setting up the cluster
manually on EC2 instances.
Are you saying I will reach higher performance when
With respect to EMR, you can run HBase fairly easily.
You can't run MapR w HBase on EMR stick w Amazon's release.
And you can run it but you will want to know your tuning parameters up front
when you instantiate it.
Sent from a remote device. Please excuse any typos...
Mike Segel
On May 8, 2
To add to what Andy said - the key to getting HBase running well in AWS is:
1. Choose the right instance types. I usually recommend the HPC
instances or now the high storage density instances. Those will give
you the best performance.
2. Use the latest Amzn Linux AMIs and the latest HBase and HDF
M7 is not Apache HBase, or any HBase. It is a proprietary NoSQL datastore
with (I gather) an Apache HBase compatible Java API.
As for running HBase on EC2, we recently discussed some particulars, see
the latter part of this thread: http://search-hadoop.com/m/rI1HpK90gu where
I hijack it. I wouldn'
I think that you when you are talking about RMap, you are referring to
MapR´s distribution.
I think that MapR´s team released a very good version of its Hadoop
distribution focused on HBase called M7. You can see its overview here:
http://www.mapr.com/products/mapr-editions/m7-edition
But this rel
Your EC2 instance is having EBS or instance type as the data store?
If it is EBS then the latency is bit high and this is as per Andrew's
experience.
Regards
Ram
On Wed, May 8, 2013 at 8:01 AM, Marcos Luis Ortiz Valmaseda <
marcosluis2...@gmail.com> wrote:
> I think that Andrew talked about thi
I think that Andrew talked about this some years ago and he created some
scripts for that. You can find them here:
https://github.com/apurtell/hbase-ec2
Then, you can review some links about this topic:
http://blog.cloudera.com/blog/2012/10/set-up-a-hadoophbase-cluster-on-ec2-in-about-an-hour/
htt
Hi,
Has anyone got some recommendations about running HBase on EC2? I am
testing it, and so far I am very disappointed with it. I did not change
anything about the default 'Amazon distribution' installation. It has one
MasterNode and two slave nodes, and write performance is around 2500 small
rows
12 matches
Mail list logo
