Re: Upgrade instructions don't make sense

2015-11-23 Thread Sebastian Estevez
We are happy to clarify the docs. I'm ccing docs@datastax. Thanks! all the best, Sebastián On Nov 23, 2015 6:48 PM, "Jacob Hathaway" wrote: > Actually Sebastian, saying one, does not always imply the other. And when > it says this: > > In Cassandra 2.0.x, virtual nodes (vnodes) are enabled by

Re: Upgrade instructions don't make sense

2015-11-23 Thread Robert Wille
I guess I need to learn to read. Yes, I’m using vnodes, and yes, the instructions say to disable them if you aren’t using them, not if you are. Sorry about cluttering up the mailing list. Rboert On Nov 23, 2015, at 4:22 PM, Sebastian Estevez mailto:sebastian.este...@datastax.com>> wrote: If y

Re: Upgrade instructions don't make sense

2015-11-23 Thread Jacob Hathaway
Actually Sebastian, saying one, does not always imply the other. And when it says this: In Cassandra 2.0.x, virtual nodes (vnodes) are enabled by default. Disable vnodes in the 2.0.x version before upgrading. That implies to me to disable vnodes no matter what. How do we get the docs fixed? I

Re: Upgrade instructions don't make sense

2015-11-23 Thread Vasileios Vlachos
Exactly, thanks! On 23 Nov 2015 11:26 pm, "Vasileios Vlachos" wrote: > If you want to go from 2.0 to 2.1 and you are NOT using vnodes on your > current cluster (that is version 2.0), then make sure you disable them on > the new 2.1 config during the upgrade. Otherwise just leave the setting as >

Re: Upgrade instructions don't make sense

2015-11-23 Thread Vasileios Vlachos
If you want to go from 2.0 to 2.1 and you are NOT using vnodes on your current cluster (that is version 2.0), then make sure you disable them on the new 2.1 config during the upgrade. Otherwise just leave the setting as is. That's how I understand it personally. We are going to upgrade at some po

Re: Upgrade instructions don't make sense

2015-11-23 Thread Paulo Motta
This actually means if you *DON'T* use vnodes, you should be careful to set num_tokens in the cassandra.yaml when upgrading, since the default cassandra.yaml is to have vnodes enabled. You should ignore these instructions if you already have a vnodes-enabled cluster, and set num_tokens accordingly.

Re: Upgrade instructions don't make sense

2015-11-23 Thread Sebastian Estevez
> > If your cluster does not use vnodes, disable vnodes in each new > cassandra.yaml If your cluster *does* use vnodes do *not* disable them. All the best, [image: datastax_logo.png] Sebastián Estévez Solutions Architect | 954 905 8615 | sebastian.este...@datastax.

Re: Upgrade instructions don't make sense

2015-11-23 Thread Prem Yadav
*If your cluster does not use vnodes* Are you using vnodes now? On Mon, Nov 23, 2015 at 10:55 PM, Robert Wille wrote: > I’m wanting to upgrade from 2.0 to 2.1. The upgrade instructions at > http://docs.datastax.com/en/upgrade/doc/upgrade/cassandra/upgradeCassandraDetails.html > has > the follo

Upgrade instructions don't make sense

2015-11-23 Thread Robert Wille
I’m wanting to upgrade from 2.0 to 2.1. The upgrade instructions at http://docs.datastax.com/en/upgrade/doc/upgrade/cassandra/upgradeCassandraDetails.html has the following, which leaves me with more questions than it answers: If your cluster does not use vnodes, disable vnodes in each new cassa