Upgrade instructions don't make sense

[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 cassandra.yaml 
before doing the rolling restart.
In Cassandra 2.0.x, virtual nodes (vnodes) are enabled by default. Disable 
vnodes in the 2.0.x version before upgrading.

  1.  In the 
cassandra.yaml
 file, set num_tokens to 1.
  2.  Uncomment the initial_token property and set it to 1 or to the value of a 
generated 
token
 for a multi-node cluster.

It seems strange that vnodes has to be disabled to upgrade, but whatever. If I 
use an initial token generator to set the initial_token property of each node, 
then I assume that my token ranges are all going to change, and that there’s 
going to be a whole bunch of streaming as the data is shuffled around. The docs 
don’t mention that. Should I wait until the streaming is done before proceeding 
with the upgrade?

The docs don’t talk about vnodes and initial_tokens post-upgrade. Can I turn 
vnodes back on? Am I forever after stuck with having to have manually generated 
initial tokens (and needing to have a unique cassandra.yaml for every node)? 
Can I just set num_tokens = 256 and comment out initial_token and do a rolling 
restart?

Thanks in advance

Robert

Re: Upgrade instructions don't make sense

[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.com

[image: linkedin.png]  [image:
facebook.png]  [image: twitter.png]
 [image: g+.png]







DataStax is the fastest, most scalable distributed database technology,
delivering Apache Cassandra to the world’s most innovative enterprises.
Datastax is built to be agile, always-on, and predictably scalable to any
size. With more than 500 customers in 45 countries, DataStax is the
database technology and transactional backbone of choice for the worlds
most innovative companies such as Netflix, Adobe, Intuit, and eBay.

On Mon, Nov 23, 2015 at 5: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 following, which leaves me with more questions than it answers:
>
> If your cluster does not use vnodes, disable vnodes in each new
> cassandra.yaml before doing the rolling restart.
> In Cassandra 2.0.x, virtual nodes (vnodes) are enabled by default. Disable
> vnodes in the 2.0.x version before upgrading.
>
>1. In the cassandra.yaml
>
> 
>  file,
>set num_tokens to 1.
>2. Uncomment the initial_token property and set it to 1 or to the
>value of a generated token
>
> 
>  for
>a multi-node cluster.
>
>
> It seems strange that vnodes has to be disabled to upgrade, but whatever.
> If I use an initial token generator to set the initial_token property of
> each node, then I assume that my token ranges are all going to change, and
> that there’s going to be a whole bunch of streaming as the data is shuffled
> around. The docs don’t mention that. Should I wait until the streaming is
> done before proceeding with the upgrade?
>
> The docs don’t talk about vnodes and initial_tokens post-upgrade. Can I
> turn vnodes back on? Am I forever after stuck with having to have manually
> generated initial tokens (and needing to have a unique cassandra.yaml for
> every node)? Can I just set num_tokens = 256 and comment out initial_token
> and do a rolling restart?
>
> Thanks in advance
>
> Robert
>
>

Re: Upgrade instructions don't make sense

[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 following, which leaves me with more questions than it answers:
>
> If your cluster does not use vnodes, disable vnodes in each new
> cassandra.yaml before doing the rolling restart.
> In Cassandra 2.0.x, virtual nodes (vnodes) are enabled by default. Disable
> vnodes in the 2.0.x version before upgrading.
>
>1. In the cassandra.yaml
>
> 
>  file,
>set num_tokens to 1.
>2. Uncomment the initial_token property and set it to 1 or to the
>value of a generated token
>
> 
>  for
>a multi-node cluster.
>
>
> It seems strange that vnodes has to be disabled to upgrade, but whatever.
> If I use an initial token generator to set the initial_token property of
> each node, then I assume that my token ranges are all going to change, and
> that there’s going to be a whole bunch of streaming as the data is shuffled
> around. The docs don’t mention that. Should I wait until the streaming is
> done before proceeding with the upgrade?
>
> The docs don’t talk about vnodes and initial_tokens post-upgrade. Can I
> turn vnodes back on? Am I forever after stuck with having to have manually
> generated initial tokens (and needing to have a unique cassandra.yaml for
> every node)? Can I just set num_tokens = 256 and comment out initial_token
> and do a rolling restart?
>
> Thanks in advance
>
> Robert
>
>

Re: Upgrade instructions don't make sense

[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.

These transition instructions are leftovers from 1.2 to 2.0 upgrade, when
vnodes became the default, and are indeed a bit confusing now from the 2.0
to 2.1 upgrade, so I'm copying the docs team to make that a bit more clear
(I believe this excerpt is a bit confusing: "In Cassandra 2.0.x, virtual
nodes (vnodes) are enabled by default. Disable vnodes in the 2.0.x version
before upgrading").

2015-11-23 21:22 GMT-02:00 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.com
>
> [image: linkedin.png]  [image:
> facebook.png]  [image: twitter.png]
>  [image: g+.png]
> 
> 
> 
>
>
> 
>
> DataStax is the fastest, most scalable distributed database technology,
> delivering Apache Cassandra to the world’s most innovative enterprises.
> Datastax is built to be agile, always-on, and predictably scalable to any
> size. With more than 500 customers in 45 countries, DataStax is the
> database technology and transactional backbone of choice for the worlds
> most innovative companies such as Netflix, Adobe, Intuit, and eBay.
>
> On Mon, Nov 23, 2015 at 5: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 following, which leaves me with more questions than it answers:
>>
>> If your cluster does not use vnodes, disable vnodes in each new
>> cassandra.yaml before doing the rolling restart.
>> In Cassandra 2.0.x, virtual nodes (vnodes) are enabled by default.
>> Disable vnodes in the 2.0.x version before upgrading.
>>
>>1. In the cassandra.yaml
>>
>> 
>>  file,
>>set num_tokens to 1.
>>2. Uncomment the initial_token property and set it to 1 or to the
>>value of a generated token
>>
>> 
>>  for
>>a multi-node cluster.
>>
>>
>> It seems strange that vnodes has to be disabled to upgrade, but whatever.
>> If I use an initial token generator to set the initial_token property of
>> each node, then I assume that my token ranges are all going to change, and
>> that there’s going to be a whole bunch of streaming as the data is shuffled
>> around. The docs don’t mention that. Should I wait until the streaming is
>> done before proceeding with the upgrade?
>>
>> The docs don’t talk about vnodes and initial_tokens post-upgrade. Can I
>> turn vnodes back on? Am I forever after stuck with having to have manually
>> generated initial tokens (and needing to have a unique cassandra.yaml for
>> every node)? Can I just set num_tokens = 256 and comment out initial_token
>> and do a rolling restart?
>>
>> Thanks in advance
>>
>> Robert
>>
>>
>

Re: Upgrade instructions don't make sense

[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
point so I'd appreciate if people could confirm that.
On 23 Nov 2015 11:23 pm, "Sebastian Estevez" 
wrote:

> 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.com
>
> [image: linkedin.png]  [image:
> facebook.png]  [image: twitter.png]
>  [image: g+.png]
> 
> 
> 
>
>
> 
>
> DataStax is the fastest, most scalable distributed database technology,
> delivering Apache Cassandra to the world’s most innovative enterprises.
> Datastax is built to be agile, always-on, and predictably scalable to any
> size. With more than 500 customers in 45 countries, DataStax is the
> database technology and transactional backbone of choice for the worlds
> most innovative companies such as Netflix, Adobe, Intuit, and eBay.
>
> On Mon, Nov 23, 2015 at 5: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 following, which leaves me with more questions than it answers:
>>
>> If your cluster does not use vnodes, disable vnodes in each new
>> cassandra.yaml before doing the rolling restart.
>> In Cassandra 2.0.x, virtual nodes (vnodes) are enabled by default.
>> Disable vnodes in the 2.0.x version before upgrading.
>>
>>1. In the cassandra.yaml
>>
>> 
>>  file,
>>set num_tokens to 1.
>>2. Uncomment the initial_token property and set it to 1 or to the
>>value of a generated token
>>
>> 
>>  for
>>a multi-node cluster.
>>
>>
>> It seems strange that vnodes has to be disabled to upgrade, but whatever.
>> If I use an initial token generator to set the initial_token property of
>> each node, then I assume that my token ranges are all going to change, and
>> that there’s going to be a whole bunch of streaming as the data is shuffled
>> around. The docs don’t mention that. Should I wait until the streaming is
>> done before proceeding with the upgrade?
>>
>> The docs don’t talk about vnodes and initial_tokens post-upgrade. Can I
>> turn vnodes back on? Am I forever after stuck with having to have manually
>> generated initial tokens (and needing to have a unique cassandra.yaml for
>> every node)? Can I just set num_tokens = 256 and comment out initial_token
>> and do a rolling restart?
>>
>> Thanks in advance
>>
>> Robert
>>
>>
>

Re: Upgrade instructions don't make sense

[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
> is.
>
> That's how I understand it personally.  We are going to upgrade at some
> point so I'd appreciate if people could confirm that.
> On 23 Nov 2015 11:23 pm, "Sebastian Estevez" <
> sebastian.este...@datastax.com> wrote:
>
>> 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.com
>>
>> [image: linkedin.png]  [image:
>> facebook.png]  [image: twitter.png]
>>  [image: g+.png]
>> 
>> 
>> 
>>
>>
>> 
>>
>> DataStax is the fastest, most scalable distributed database technology,
>> delivering Apache Cassandra to the world’s most innovative enterprises.
>> Datastax is built to be agile, always-on, and predictably scalable to any
>> size. With more than 500 customers in 45 countries, DataStax is the
>> database technology and transactional backbone of choice for the worlds
>> most innovative companies such as Netflix, Adobe, Intuit, and eBay.
>>
>> On Mon, Nov 23, 2015 at 5: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 following, which leaves me with more questions than it answers:
>>>
>>> If your cluster does not use vnodes, disable vnodes in each new
>>> cassandra.yaml before doing the rolling restart.
>>> In Cassandra 2.0.x, virtual nodes (vnodes) are enabled by default.
>>> Disable vnodes in the 2.0.x version before upgrading.
>>>
>>>1. In the cassandra.yaml
>>>
>>> 
>>>  file,
>>>set num_tokens to 1.
>>>2. Uncomment the initial_token property and set it to 1 or to the
>>>value of a generated token
>>>
>>> 
>>>  for
>>>a multi-node cluster.
>>>
>>>
>>> It seems strange that vnodes has to be disabled to upgrade, but
>>> whatever. If I use an initial token generator to set the initial_token
>>> property of each node, then I assume that my token ranges are all going to
>>> change, and that there’s going to be a whole bunch of streaming as the data
>>> is shuffled around. The docs don’t mention that. Should I wait until the
>>> streaming is done before proceeding with the upgrade?
>>>
>>> The docs don’t talk about vnodes and initial_tokens post-upgrade. Can I
>>> turn vnodes back on? Am I forever after stuck with having to have manually
>>> generated initial tokens (and needing to have a unique cassandra.yaml for
>>> every node)? Can I just set num_tokens = 256 and comment out initial_token
>>> and do a rolling restart?
>>>
>>> Thanks in advance
>>>
>>> Robert
>>>
>>>
>>

Re: Upgrade instructions don't make sense

[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 would suggest 2 things. First, more 
comprehensive in the instructions, especially for upgrades. Second, fixing 
little things like broken links, etc, etc.

Thanks
Jake Hathaway
Cassandra Beginner


On Nov 23, 2015, at 4:22 PM, Sebastian Estevez 
> wrote:

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,

[datastax_logo.png]
Sebastián Estévez
Solutions Architect | 954 905 8615 | 
sebastian.este...@datastax.com
[linkedin.png] [facebook.png] 
  [twitter.png] 
  [g+.png] 
  
[https://lh6.googleusercontent.com/24_538J0j5M0NHQx-jkRiV_IHrhsh-98hpi--Qz9b0-I4llvWuYI6LgiVJsul0AhxL0gMTOHgw3G0SvIXaT2C7fsKKa_DdQ2uOJ-bQ6h_mQ7k7iMybcR1dr1VhWgLMxcmg]
 


[http://learn.datastax.com/rs/059-YLZ-577/images/Gartner_728x90_Sig4.png]

DataStax is the fastest, most scalable distributed database technology, 
delivering Apache Cassandra to the world’s most innovative enterprises. 
Datastax is built to be agile, always-on, and predictably scalable to any size. 
With more than 500 customers in 45 countries, DataStax is the database 
technology and transactional backbone of choice for the worlds most innovative 
companies such as Netflix, Adobe, Intuit, and eBay.

On Mon, Nov 23, 2015 at 5: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 following, which leaves me with more questions than it answers:

If your cluster does not use vnodes, disable vnodes in each new cassandra.yaml 
before doing the rolling restart.
In Cassandra 2.0.x, virtual nodes (vnodes) are enabled by default. Disable 
vnodes in the 2.0.x version before upgrading.

  1.  In the 
cassandra.yaml
 file, set num_tokens to 1.
  2.  Uncomment the initial_token property and set it to 1 or to the value of a 
generated 
token
 for a multi-node cluster.

It seems strange that vnodes has to be disabled to upgrade, but whatever. If I 
use an initial token generator to set the initial_token property of each node, 
then I assume that my token ranges are all going to change, and that there’s 
going to be a whole bunch of streaming as the data is shuffled around. The docs 
don’t mention that. Should I wait until the streaming is done before proceeding 
with the upgrade?

The docs don’t talk about vnodes and initial_tokens post-upgrade. Can I turn 
vnodes back on? Am I forever after stuck with having to have manually generated 
initial tokens (and needing to have a unique cassandra.yaml for every node)? 
Can I just set num_tokens = 256 and comment out initial_token and do a rolling 
restart?

Thanks in advance

Robert

Re: Upgrade instructions don't make sense

[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 
> wrote:

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,

[datastax_logo.png]
Sebastián Estévez
Solutions Architect | 954 905 8615 | 
sebastian.este...@datastax.com
[linkedin.png] [facebook.png] 
  [twitter.png] 
  [g+.png] 
  
[https://lh6.googleusercontent.com/24_538J0j5M0NHQx-jkRiV_IHrhsh-98hpi--Qz9b0-I4llvWuYI6LgiVJsul0AhxL0gMTOHgw3G0SvIXaT2C7fsKKa_DdQ2uOJ-bQ6h_mQ7k7iMybcR1dr1VhWgLMxcmg]
 


[http://learn.datastax.com/rs/059-YLZ-577/images/Gartner_728x90_Sig4.png]

DataStax is the fastest, most scalable distributed database technology, 
delivering Apache Cassandra to the world’s most innovative enterprises. 
Datastax is built to be agile, always-on, and predictably scalable to any size. 
With more than 500 customers in 45 countries, DataStax is the database 
technology and transactional backbone of choice for the worlds most innovative 
companies such as Netflix, Adobe, Intuit, and eBay.

On Mon, Nov 23, 2015 at 5: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 following, which leaves me with more questions than it answers:

If your cluster does not use vnodes, disable vnodes in each new cassandra.yaml 
before doing the rolling restart.
In Cassandra 2.0.x, virtual nodes (vnodes) are enabled by default. Disable 
vnodes in the 2.0.x version before upgrading.

  1.  In the 
cassandra.yaml
 file, set num_tokens to 1.
  2.  Uncomment the initial_token property and set it to 1 or to the value of a 
generated 
token
 for a multi-node cluster.

It seems strange that vnodes has to be disabled to upgrade, but whatever. If I 
use an initial token generator to set the initial_token property of each node, 
then I assume that my token ranges are all going to change, and that there’s 
going to be a whole bunch of streaming as the data is shuffled around. The docs 
don’t mention that. Should I wait until the streaming is done before proceeding 
with the upgrade?

The docs don’t talk about vnodes and initial_tokens post-upgrade. Can I turn 
vnodes back on? Am I forever after stuck with having to have manually generated 
initial tokens (and needing to have a unique cassandra.yaml for every node)? 
Can I just set num_tokens = 256 and comment out initial_token and do a rolling 
restart?

Thanks in advance

Robert

Re: Upgrade instructions don't make sense

[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 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 would suggest 2 things. First, more
> comprehensive in the instructions, especially for upgrades. Second, fixing
> little things like broken links, etc, etc.
>
> Thanks
> Jake Hathaway
> Cassandra Beginner
>
>
> On Nov 23, 2015, at 4:22 PM, Sebastian Estevez <
> sebastian.este...@datastax.com> wrote:
>
> 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.com
> [image: linkedin.png]  [image:
> facebook.png]  [image: twitter.png]
>  [image: g+.png]
> 
> 
> 
>
> 
>
> DataStax is the fastest, most scalable distributed database technology,
> delivering Apache Cassandra to the world’s most innovative enterprises.
> Datastax is built to be agile, always-on, and predictably scalable to any
> size. With more than 500 customers in 45 countries, DataStax is the
> database technology and transactional backbone of choice for the worlds
> most innovative companies such as Netflix, Adobe, Intuit, and eBay.
>
> On Mon, Nov 23, 2015 at 5: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 following, which leaves me with more questions than it answers:
>>
>> If your cluster does not use vnodes, disable vnodes in each new
>> cassandra.yaml before doing the rolling restart.
>> In Cassandra 2.0.x, virtual nodes (vnodes) are enabled by default.
>> Disable vnodes in the 2.0.x version before upgrading.
>>
>>1. In the cassandra.yaml
>>
>> 
>>  file,
>>set num_tokens to 1.
>>2. Uncomment the initial_token property and set it to 1 or to the
>>value of a generated token
>>
>> 
>>  for
>>a multi-node cluster.
>>
>>
>> It seems strange that vnodes has to be disabled to upgrade, but whatever.
>> If I use an initial token generator to set the initial_token property of
>> each node, then I assume that my token ranges are all going to change, and
>> that there’s going to be a whole bunch of streaming as the data is shuffled
>> around. The docs don’t mention that. Should I wait until the streaming is
>> done before proceeding with the upgrade?
>>
>> The docs don’t talk about vnodes and initial_tokens post-upgrade. Can I
>> turn vnodes back on? Am I forever after stuck with having to have manually
>> generated initial tokens (and needing to have a unique cassandra.yaml for
>> every node)? Can I just set num_tokens = 256 and comment out initial_token
>> and do a rolling restart?
>>
>> Thanks in advance
>>
>> Robert
>>
>>
>
>