You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cassandra.apache.org by Arindam Barua <ab...@247-inc.com> on 2014/01/02 19:51:34 UTC
vnode in production
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" method vs using shuffle which seems to be not recommended. It helps that we were planning to add capacity to our Cassandra ring anyway. Our tests in QA so far have been good. If we do not upgrade now however, we will have to add the new hosts normally to the ring, and may not be able to add a new data center at a later point of time.
Thanks,
Arindam
Re: vnode in production
Posted by Chris Burroughs <ch...@gmail.com>.
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 will try to upgrade to 1.2.13 or 1.2.14 subsequently.
Your plan seems reasonable but in the interest of full disclosure
CASSANDRA-6345 has been observed as a significant issue for clusters in
the 50-75 node range.
Re: vnode in production
Posted by Tupshin Harper <tu...@tupshin.com>.
This is a generally good interpretation of the state of vnodes with respect
to Cassandra versions 1.2.12 and 1.2.13.
Adding a new datacenter to a 1.2.12 cluster at your scale should be fine. I
consider vnodes fit for production at almost any scale after 1.2.13, or 50
nodes or less (ballpark) for 1.2.12. For reference, I filed the main
tracking issue (CASSANDRA-6127).
-Tupshin
On Mon, Jan 6, 2014 at 1:56 PM, Arindam Barua <ab...@247-inc.com> 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 will try to upgrade to 1.2.13
> or 1.2.14 subsequently.
>
> -----Original Message-----
> From: Chris Burroughs [mailto:chris.burroughs@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 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 the issues
> if you are interested in the details.
>
> > 2. upgrading to vnodes in production
>
> I am not aware of anyone who has succeeded with shuffle in production, but
> the 'add a new DC' procedure works.
>
RE: vnode in production
Posted by Arindam Barua <ab...@247-inc.com>.
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 will try to upgrade to 1.2.13 or 1.2.14 subsequently.
-----Original Message-----
From: Chris Burroughs [mailto:chris.burroughs@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 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 the issues if you are interested in the details.
> 2. upgrading to vnodes in production
I am not aware of anyone who has succeeded with shuffle in production, but the 'add a new DC' procedure works.
Re: vnode in production
Posted by Chris Burroughs <ch...@gmail.com>.
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 the
issues if you are interested in the details.
> 2. upgrading to vnodes in production
I am not aware of anyone who has succeeded with shuffle in production,
but the 'add a new DC' procedure works.
Re: vnode in production
Posted by Russell Bradberry <rb...@gmail.com>.
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 (abarua@247-inc.com) wrote:
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” method vs using shuffle which seems to be not recommended. It helps that we were planning to add capacity to our Cassandra ring anyway. Our tests in QA so far have been good. If we do not upgrade now however, we will have to add the new hosts normally to the ring, and may not be able to add a new data center at a later point of time.
Thanks,
Arindam