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 <aba...@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.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 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. >
