Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (nike.apache.org: domain of rcoli@eventbrite.com designates
 209.85.217.181 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <52CD17A4.3030207@avast.com>
References: <52CD17A4.3030207@avast.com>
Date: Wed, 8 Jan 2014 10:24:04 -0800
Message-ID: 
 <CAEDUwd2PPo+L-rKJS2g_oTXgHB4MdJ7KzRAZSB26BoQuU4vr3w@mail.gmail.com>
Subject: Re: upgrade from cassandra 1.2.3 -> 1.2.13 + start using SSL
From: Robert Coli <rcoli@eventbrite.com>
To: "user@cassandra.apache.org" <user@cassandra.apache.org>
Content-Type: multipart/alternative; boundary=089e0158c40e12d8b904ef7999f8

--089e0158c40e12d8b904ef7999f8
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Jan 8, 2014 at 1:17 AM, Jiri Horky <horky@avast.com> wrote:

> I am specifically interested whether is possible to upgrade just one
> node and keep it running like that for some time, i.e. if the gossip
> protocol is compatible in both directions. We are a bit afraid to
> upgrade all nodes to 1.2.13 at once in a case we would need to rollback.
>

This not not officially supported. It will probably work for these
particular versions, but it is not recommended.

The most serious potential issue is an inability to replace the new node if
it fails. There's also the problem of not being able to repair until you're
back on the same versions. And other, similar, undocumented edge cases...

=Rob

--089e0158c40e12d8b904ef7999f8
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On W=
ed, Jan 8, 2014 at 1:17 AM, Jiri Horky <span dir=3D"ltr">&lt;<a href=3D"mai=
lto:horky@avast.com" target=3D"_blank">horky@avast.com</a>&gt;</span> wrote=
:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-le=
ft:1px #ccc solid;padding-left:1ex">
I am specifically interested whether is possible to upgrade just one<br>
node and keep it running like that for some time, i.e. if the gossip<br>
protocol is compatible in both directions. We are a bit afraid to<br>
upgrade all nodes to 1.2.13 at once in a case we would need to rollback.<br=
></blockquote><div><br></div><div>This not not officially supported. It wil=
l probably work for these particular versions, but it is not recommended.</=
div>
<div><br></div><div>The most serious potential issue is an inability to rep=
lace the new node if it fails. There&#39;s also the problem of not being ab=
le to repair until you&#39;re back on the same versions. And other, similar=
, undocumented edge cases...</div>
<div><br></div><div>=3DRob</div><div><br></div></div></div></div>

--089e0158c40e12d8b904ef7999f8--