On 01/06/2014 01:56 PM, Arindam Barua wrote:
Thanks for your responses. We are on 1.2.12 currently.
The fixes in 1.2.13 seem to help for clusters in the 500+ node range (like
CASSANDRA-6409). Ours is below 50 now, so we plan to go ahead and enable vnodes
with the 'add a new DC' procedure. We wi
ay, January 06, 2014 10:00 AM
> To: user@cassandra.apache.org
> Subject: Re: vnode in production
>
> On 01/02/2014 01:51 PM, Arindam Barua wrote:
> > 1. the stability of vnodes in production
>
> I'm happily using vnodes in production now, but I would have trouble
&
or 1.2.14
subsequently.
-Original Message-
From: Chris Burroughs [mailto:chris.burrou...@gmail.com]
Sent: Monday, January 06, 2014 10:00 AM
To: user@cassandra.apache.org
Subject: Re: vnode in production
On 01/02/2014 01:51 PM, Arindam Barua wrote:
> 1. the stability of vnodes in pr
On 01/02/2014 01:51 PM, Arindam Barua wrote:
1. the stability of vnodes in production
I'm happily using vnodes in production now, but I would have trouble
calling them stable for more than small clusters until very recently
(1.2.13). CASSANDRA-6127 served as a master ticket for most of
VNodes in production are pretty stable. That being said, I have never heard of
anyone doing a successful "nodetool shuffle”. A few people have skirted the
issue by creating a new data center with VNodes enabled and replicating the
data over.
On January 2, 2014 at 1:52:20 PM, Arindam Barua (a
Hello all,
Just wanted to check if anyone has any experiences to share regarding
1. the stability of vnodes in production
2. upgrading to vnodes in production
We recently upgraded to 1.2.12 in production and were planning to turn on
vnodes using the "adding a new datacenter" metho
