Repair and bootstrap will be limited by the node doing repair or bootstrap,
since it has to do the same amount of work whatever num_tokens is.
That's what I was thinking.
I normally assume repair has very little data to stream, and most of the time
is taken creating the merkle trees. In
@Aaron
Streaming from all the physical nodes in the cluster should make repair
faster, for the same reason it makes bootstrap faster. Shouldn't it ?
2013/8/12 Aaron Morton aa...@thelastpickle.com
Aaron - I read about the virtual nodes at
On 13 August 2013 10:15, Alain RODRIGUEZ arodr...@gmail.com wrote:
Streaming from all the physical nodes in the cluster should make repair
faster, for the same reason it makes bootstrap faster. Shouldn't it ?
Virtual nodes doesn't speed up either very much. Repair and bootstrap will
be
Aaron - I read about the virtual nodes at
http://www.datastax.com/dev/blog/virtual-nodes-in-cassandra-1-2
On Tue, Aug 6, 2013 at 4:49 AM, Richard Low rich...@wentnet.com wrote:
On 6 August 2013 08:40, Aaron Morton aa...@thelastpickle.com wrote:
The reason for me looking at virtual
...@gmail.com
A : user@cassandra.apache.org,
Date : 25/07/2013 23:25
Objet : cassandra 1.2.5- virtual nodes (num_token) pros/cons?
Hi,
I am upgrading my cassandra cluster from 0.8 to 1.2.5.
In cassandra 1.2.5 the 'num_token' attribute confuses me.
I understand
On 6 August 2013 08:40, Aaron Morton aa...@thelastpickle.com wrote:
The reason for me looking at virtual nodes is because of terrible
experiences we had with 0.8 repairs and as per documentation (an logically)
the virtual nodes seems like it will help repairs being smoother. Is this
true?
Objet : cassandra 1.2.5- virtual nodes (num_token) pros/cons?
Hi,
I am upgrading my cassandra cluster from 0.8 to 1.2.5.
In cassandra 1.2.5 the 'num_token' attribute confuses me.
I understand that it distributes multiple tokens per node but I am
not clear how that is helpful
a écrit sur 25/07/2013 23:25:11 :
De : rash aroskar rashmi.aros...@gmail.com
A : user@cassandra.apache.org,
Date : 25/07/2013 23:25
Objet : cassandra 1.2.5- virtual nodes (num_token) pros/cons?
Hi,
I am upgrading my cassandra cluster from 0.8 to 1.2.5.
In cassandra 1.2.5
Disadvantage, hadoop support is based on the token range, so maps may equals
numtokens per node * nodes number.
Best Regards,Andy Hu（胡 珊）
Date: Thu, 25 Jul 2013 17:25:11 -0400
Subject: cassandra 1.2.5- virtual nodes (num_token) pros/cons?
From: rashmi.aros...@gmail.com
To: user
: rash aroskar rashmi.aros...@gmail.com
A : user@cassandra.apache.org,
Date : 25/07/2013 23:25
Objet : cassandra 1.2.5- virtual nodes (num_token) pros/cons?
Hi,
I am upgrading my cassandra cluster from 0.8 to 1.2.5.
In cassandra 1.2.5 the 'num_token' attribute confuses me.
I
Hi,
I am upgrading my cassandra cluster from 0.8 to 1.2.5.
In cassandra 1.2.5 the 'num_token' attribute confuses me.
I understand that it distributes multiple tokens per node but I am not
clear how that is helpful for performance or load balancing. Can anyone
elaborate? has anyone used this
It is very useful to upgrade the apps perfomance.
For example, if you have a machine with X capacity, you can put the
num_token=256. If you add a machine in your cluster with (X*2) capacity you
can put the num_token=512.
So, this new machine will receive twice the load automatically.
Moreover, you
12 matches
Mail list logo
