On Mon, Dec 30, 2013 at 6:45 AM, Tupshin Harper wrote:
> OK. Given the correction of my unfortunate partitioner error, you can,
> and probably should, upgrade in place to 1.2, but with num_tokens=1 so it
> will initially behave like 1.1 non vnodes would. Then you can do a rolling
> conversion to
OK. Given the correction of my unfortunate partitioner error, you can, and
probably should, upgrade in place to 1.2, but with num_tokens=1 so it will
initially behave like 1.1 non vnodes would. Then you can do a rolling
conversion to more than one vnode per node, and once complete, shuffle your
vn
Sorry for the misinformation. Totally forgot about that being supported
since I've never seen the combination actually used. Correct that it
should work, though.
On Dec 30, 2013 2:18 PM, "Hannu Kröger" wrote:
> Hi,
>
> Random Partitioner + VNodes are a supported combo based on DataStax
> docume
Hi,
Random Partitioner + VNodes are a supported combo based on DataStax
documentation:
http://www.datastax.com/documentation/cassandra/1.2/webhelp/cassandra/architecture/architecturePartitionerAbout_c.html
How else would you even migrate from 1.1 to Vnodes since migration from one
partitioner to
What is the technical limitation that vnodes need murmer? That seems uncool
for long time users?
On Monday, December 30, 2013, Jean-Armel Luce wrote:
> Hi,
>
> I don't know how your application works, but I explained during the last
Cassandra Summit Europe how we did the migration from relational
Hi,
I don't know how your application works, but I explained during the last
Cassandra Summit Europe how we did the migration from relational database
to Cassandra without any interruption of service.
You can have a look at the video http://www.youtube.com/watch?v=mefOE9K7sLI
And use the mod-dup
No. This is not going to work. The vnodes feature requires the murmur3
partitioner which was introduced with Cassandra 1.2.
Since you are currently using 1.1, you must be using the random
partitioner, which is not compatible with vnodes.
Because the partitioner determines the physical layout of
Hello list,
I have a 2 DC set up with DC1:3, DC2:3 replication factor. DC1 has 6 nodes,
DC2 has 3. This whole setup runs on AWS, running cassandra 1.1.
Here's my nodetool ring:
1.1.1.1 eu-west 1a Up Normal 55.07 GB50.00%
0
2.2.2.1 us-east 1b Up
