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: Alain RODRIGUEZ <arodrime@gmail.com>
Date: Wed, 16 Nov 2016 16:43:58 +0100
Message-ID: <CA+VSrLo+FXfcSsNnV65wR4272acxiDFKRm3CH+G1x0Dpre+sZQ@mail.gmail.com>
Subject: Re: Can nodes in c* cluster run different versions ?
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=001a114e52f026732405416cf20a
archived-at: Wed, 16 Nov 2016 15:44:25 -0000

--001a114e52f026732405416cf20a
Content-Type: text/plain; charset=UTF-8

Hey Techpyaasa,

Are you aware of this documentation?

https://docs.datastax.com/en/upgrade/doc/upgrade/cassandra/upgrdCassandraDetails.html

Basically yes, you can have multiple versions, but you want to make this
multi-version time it as short as possible.

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?


To make the upgrade as short as possible I use to migrate the whole cluster
and only after upgrade sstables. This minimises the time you're running
multiple version.

The only (soft) limitation, is that you shouldn't be streaming data around
(do not bootstrap, repair or remove a node). It might work, that's why I
say "soft limitation" but it might not work, there is no guarantee, it
mainly depends on changes that were made between versions I believe.

C*heers,
-----------------------
Alain Rodriguez - @arodream - alain@thelastpickle.com
France

The Last Pickle - Apache Cassandra Consulting
http://www.thelastpickle.com


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
>

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

<div dir=3D"ltr">Hey Techpyaasa,=C2=A0<div><br></div><div>Are you aware of =
this documentation?</div><div><br></div><div><a href=3D"https://docs.datast=
ax.com/en/upgrade/doc/upgrade/cassandra/upgrdCassandraDetails.html">https:/=
/docs.datastax.com/en/upgrade/doc/upgrade/cassandra/upgrdCassandraDetails.h=
tml</a><br></div><div><br></div><div>Basically yes, you can have multiple v=
ersions, but you want to make this multi-version time it as short as possib=
le.</div><div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0=
px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><=
span style=3D"font-size:12.8px">As it might take few days as it will have &=
#39;upgrade sstables&#39; , so just wanted to know would be there any possi=
bility during this mismatch of c* version among nodes in cluster during thi=
s upgrade process?</span></blockquote><div><br></div><div>To make the upgra=
de as short as possible I use to migrate the whole cluster and only after u=
pgrade sstables. This minimises the time you&#39;re running multiple versio=
n.</div><div><br></div><div>The only (soft) limitation, is that you shouldn=
&#39;t be streaming data around (do not bootstrap, repair or remove a node)=
. It might work, that&#39;s why I say &quot;soft limitation&quot; but it mi=
ght not work, there is no guarantee, it mainly depends on changes that were=
 made between versions I believe.</div><div><br></div><div>C*heers,</div><d=
iv><div>-----------------------</div><div>Alain Rodriguez - @arodream - <a =
href=3D"mailto:alain@thelastpickle.com">alain@thelastpickle.com</a></div><d=
iv>France</div><div><br></div><div>The Last Pickle - Apache Cassandra Consu=
lting</div><div><a href=3D"http://www.thelastpickle.com">http://www.thelast=
pickle.com</a></div></div><div><br></div><div><br></div></div><div class=3D=
"gmail_extra"><br><div class=3D"gmail_quote">2016-11-16 11:12 GMT+01:00 tec=
hpyaasa . <span dir=3D"ltr">&lt;<a href=3D"mailto:techpyaasa@gmail.com" tar=
get=3D"_blank">techpyaasa@gmail.com</a>&gt;</span>:<br><blockquote 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 currently 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;upg=
rade sstables&#39; , so just wanted to know would be there any possibility =
during this mismatch of c* version among nodes in cluster during this upgra=
de process?<br><br>Thanks<span class=3D"HOEnZb"><font color=3D"#888888"><br=
>Techpyaasa</font></span></div>
</blockquote></div><br></div>

--001a114e52f026732405416cf20a--