Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
MIME-Version: 1.0
In-Reply-To: <CANJ3crViRo7g0fre65EgoBNxmbPRY8ft0hOFO4M_r_cEY-VzNw@mail.gmail.com>
References: <CANJ3crViRo7g0fre65EgoBNxmbPRY8ft0hOFO4M_r_cEY-VzNw@mail.gmail.com>
From: Fabrice Facorat <fabrice.facorat@gmail.com>
Date: Thu, 17 Nov 2016 13:50:59 +0100
Message-ID: <CAJgLgciE5TB8yGGqWhCpwD4CzeRpcco1wd2Hqtjb8rkYQXOOfQ@mail.gmail.com>
Subject: Re: Can nodes in c* cluster run different versions ?
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=94eb2c11c0803576b605417ea4e8
archived-at: Thu, 17 Nov 2016 12:51:07 -0000

--94eb2c11c0803576b605417ea4e8
Content-Type: text/plain; charset=UTF-8

As said already by Alain you should make this as short as possible:
- streaming operations won't work (repair, bootstrap)
- Hinted Handoff won't work as 2 differents major version of cassandra
can't shared the same schema version
- So no DDL operations (CREATE/ALTER) as you change won't be propagated

you don't need to wait for the end of "nodetool upgradesstable" to upgrade
next node: this can be done after you upgrade all nodes and satrt as an
asynchronous planified job.

My take on this:
- disable repairs
- backup date and especially system table on all nodes
- upgrade 1 node on DC1
- if everything is fine, rolling upgrade all nodes on DC1
- ensure that everything is working (you can still rollback at this point
by rebuild entirely DC1 if something is wrong or restore previous cassandra
version with previous backup files)
- once you are confident enough, upgrade DC2
- when done, schedule upgradesstables and try to spread upgradesstable
throughout your DC and racks if you don't want to impact your read latency
too much
- once finished, reenable repairs


2016-11-16 11:12 GMT+01:00 techpyaasa . <techpyaasa@gmail.com>:

> Hi all,
>
> We are currently running c*-2.0.17 with 2 datacenters each with 18 nodes.
>
> We like to upgrade to c*-2.1.16. Can we upgrade first all nodes(one by
> one) in one dc and then go to next data center.
>
> As it might take few days as it will have 'upgrade sstables' , so just
> wanted to know would be there any possibility during this mismatch of c*
> version among nodes in cluster during this upgrade process?
>
> Thanks
> Techpyaasa
>


-- 
Close the World, Open the Net
http://www.linux-wizard.net

--94eb2c11c0803576b605417ea4e8
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div><div><div><div><div><div><div><div><div><div>As =
said already by Alain you should make this as short as possible:<br></div>-=
 streaming operations won&#39;t work (repair, bootstrap)<br></div>- Hinted =
Handoff won&#39;t work as 2 differents major version of cassandra can&#39;t=
 shared the same schema version<br></div>- So no DDL operations (CREATE/ALT=
ER) as you change won&#39;t be propagated<br><br></div>you don&#39;t need t=
o wait for the end of &quot;nodetool upgradesstable&quot; to upgrade next n=
ode: this can be done after you upgrade all nodes and satrt as an asynchron=
ous planified job.<br><br></div>My take on this:<br></div><div>- disable re=
pairs<br></div><div>- backup date and especially system table on all nodes<=
br></div>- upgrade 1 node on DC1<br></div>- if everything is fine, rolling =
upgrade all nodes on DC1<br></div>- ensure that everything is working (you =
can still rollback at this point by rebuild entirely DC1 if something is wr=
ong or restore previous cassandra version with previous backup files)<br></=
div>- once you are confident enough, upgrade DC2<br></div>- when done, sche=
dule upgradesstables and try to spread upgradesstable throughout your DC an=
d racks if you don&#39;t want to impact your read latency too much<br></div=
><div>- once finished, reenable repairs<br></div><br><div><div><br><div><di=
v><div><div><div><div><br></div></div></div></div></div></div></div></div><=
/div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">2016-11-16 1=
1:12 GMT+01:00 techpyaasa . <span dir=3D"ltr">&lt;<a href=3D"mailto:techpya=
asa@gmail.com" target=3D"_blank">techpyaasa@gmail.com</a>&gt;</span>:<br><b=
lockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px =
#ccc solid;padding-left:1ex"><div dir=3D"ltr">Hi all,<br><br>We are current=
ly running c*-2.0.17 with 2 datacenters each with 18 nodes.<br><br>We like =
to upgrade to c*-2.1.16. Can we upgrade first all nodes(one by one) in one =
dc and then go to next data center.<br><br>As it might take few days as it =
will have &#39;upgrade sstables&#39; , so just wanted to know would be ther=
e any possibility during this mismatch of c* version among nodes in cluster=
 during this upgrade process?<br><br>Thanks<span class=3D"HOEnZb"><font col=
or=3D"#888888"><br>Techpyaasa</font></span></div>
</blockquote></div><br><br clear=3D"all"><br>-- <br><div class=3D"gmail_sig=
nature" data-smartmail=3D"gmail_signature">Close the World, Open the Net<br=
><a href=3D"http://www.linux-wizard.net" target=3D"_blank">http://www.linux=
-wizard.net</a></div>
</div>

--94eb2c11c0803576b605417ea4e8--