cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sasha Dolgy <sdo...@gmail.com>
Subject Re: upgrading to cassandra 0.8
Date Tue, 07 Jun 2011 15:50:48 GMT
Thanks everyone ... upgrade to 0.8 on all nodes is a first priority then
...

On Tue, Jun 7, 2011 at 5:28 PM, Jonathan Ellis <jbellis@gmail.com> wrote:

> Even schema changes *should* work, although to be safe, the less
> "unusual" stuff you do with a mixed-version cluster, the better.
>
> However, any kind of streaming (bootstrap, node movement,
> decommission, nodetool repair) will not work.
>
> On Tue, Jun 7, 2011 at 10:07 AM, Edward Capriolo <edlinuxguru@gmail.com>
> wrote:
> >
> >
> > On Tue, Jun 7, 2011 at 10:54 AM, Sasha Dolgy <sdolgy@gmail.com> wrote:
> >>
> >> Hi,
> >>
> >> Good news on the 0.8 release.  So ... if I upgrade one node out of four,
> >> and let it run for a bit ... I should have no issues, correct?  If I
> make
> >> schema changes, specifically, adding a new column family for counters,
> how
> >> will this behave with the other three nodes that aren't upgraded?  Or
> ...
> >> should schema changes not be done until all nodes are upgraded?
> >>
> >> --
> >> Sasha Dolgy
> >> sasha.dolgy@gmail.com
> >
> > Do not make schema changes until the upgrade is complete. It will behave
> > very poorly I suspect, and you will be sad.
> >
>
>
>
> --
> Jonathan Ellis
> Project Chair, Apache Cassandra
> co-founder of DataStax, the source for professional Cassandra support
> http://www.datastax.com
>



-- 
Sasha Dolgy
sasha.dolgy@gmail.com

Mime
View raw message