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.128.41 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CALeHUF-wjuuOe_7ytQKxdd+bvxHukLUccJnnEc4kPbMoxs8vMQ@mail.gmail.com>
References: 
 <CALeHUF-wjuuOe_7ytQKxdd+bvxHukLUccJnnEc4kPbMoxs8vMQ@mail.gmail.com>
Date: Tue, 13 Aug 2013 11:41:34 -0700
Message-ID: 
 <CAEDUwd3Tqnk0-yxGrMAWrHNkXCfJF7uuE73uLqyeA_0qqRUOHQ@mail.gmail.com>
Subject: Re: Upgrade path to 2.0
From: Robert Coli <rcoli@eventbrite.com>
To: "user@cassandra.apache.org" <user@cassandra.apache.org>
Content-Type: multipart/alternative; boundary=001a11c2e3921bf63404e3d897d7

--001a11c2e3921bf63404e3d897d7
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Aug 13, 2013 at 11:25 AM, Randy Fradin <randy.fradin@gmail.com>wrote:

> According to the upgrade notes from NEWS.txt, under 2.0.0 it says:
>
>     - Upgrading is ONLY supported from Cassandra 1.2.9 or later. This
>       goes for sstable compatibility as well as network.  When
>       upgrading from an earlier release, upgrade to 1.2.9 first and
>       run upgradesstables before proceeding to 2.0.
>
> Can someone tell me what specifically makes 2.0.0 incompatible with
> versions before 1.2.9? I have a 1.0.* cluster which I am looking to
> upgrade to 1.2.*. Since it appears 1.2.9 is not even released yet
> should I be waiting to upgrade?
>

This is not the first time that NEWS.txt tells you something that raises
more questions than it answers. I continue to maintain that it would be
useful to link to JIRA ticket(s) which are the reason for instructions in
NEWS.txt.

That said, per driftx these are the two ~1.2.8 era tickets which mean you
should upgrade from 1.2.9 or later.

https://issues.apache.org/jira/browse/CASSANDRA-5696 : Upgrading to
cassandra-1.2 with a dead LEFT state from 1.1 causes problems
https://issues.apache.org/jira/browse/CASSANDRA-5845 : Don't pull schema
from higher major nodes; don't push schema to lower major nodes

Disclaimer : You probably don't want to upgrade a real cluster to 2.0
anytime in the next 5 or so months.

=Rob

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

<div dir=3D"ltr">On Tue, Aug 13, 2013 at 11:25 AM, Randy Fradin <span dir=
=3D"ltr">&lt;<a href=3D"mailto:randy.fradin@gmail.com" target=3D"_blank">ra=
ndy.fradin@gmail.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><d=
iv class=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">According to the upgrade notes from NEWS.txt, under 2.0.0 =
it says:<br>

<br>
=A0 =A0 - Upgrading is ONLY supported from Cassandra 1.2.9 or later. This<b=
r>
=A0 =A0 =A0 goes for sstable compatibility as well as network. =A0When<br>
=A0 =A0 =A0 upgrading from an earlier release, upgrade to 1.2.9 first and<b=
r>
=A0 =A0 =A0 run upgradesstables before proceeding to 2.0.<br>
<br>
Can someone tell me what specifically makes 2.0.0 incompatible with<br>
versions before 1.2.9? I have a 1.0.* cluster which I am looking to<br>
upgrade to 1.2.*. Since it appears 1.2.9 is not even released yet<br>
should I be waiting to upgrade?<br>
</blockquote></div><br></div><div class=3D"gmail_extra">This is not the fir=
st time that NEWS.txt tells you something that raises more questions than i=
t answers. I continue to maintain that it would be useful to link to JIRA t=
icket(s) which are the reason for instructions in NEWS.txt.</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">That said, =
per driftx these are the two ~1.2.8 era tickets which mean you should upgra=
de from 1.2.9 or later.</div><div class=3D"gmail_extra"><br></div><div clas=
s=3D"gmail_extra">
<div class=3D"gmail_extra"><a href=3D"https://issues.apache.org/jira/browse=
/CASSANDRA-5696">https://issues.apache.org/jira/browse/CASSANDRA-5696</a> :=
 Upgrading to cassandra-1.2 with a dead LEFT state from 1.1 causes problems=
</div>
</div><div class=3D"gmail_extra"><div class=3D"gmail_extra"><a href=3D"http=
s://issues.apache.org/jira/browse/CASSANDRA-5845">https://issues.apache.org=
/jira/browse/CASSANDRA-5845</a> : Don&#39;t pull schema from higher major n=
odes; don&#39;t push schema to lower major nodes</div>
</div><div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">Discl=
aimer : You probably don&#39;t want to upgrade a real cluster to 2.0 anytim=
e in the next 5 or so months.</div><div class=3D"gmail_extra"><br></div><di=
v class=3D"gmail_extra">
=3DRob</div><div class=3D"gmail_extra"><br></div></div>

--001a11c2e3921bf63404e3d897d7--