cassandra-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brandon Williams <dri...@gmail.com>
Subject Re: Rollback procedure for Cassandra Upgrade.
Date Tue, 10 Jan 2017 05:03:12 GMT
However, it's good to determine *how* it failed.  If nodetool just died or
timed out, that's no big deal, it'll finish.

On Mon, Jan 9, 2017 at 11:00 PM, Jonathan Haddad <jon@jonhaddad.com> wrote:

> There's no downgrade procedure. You either upgrade or you go back to a
> snapshot from the previous version.
> On Mon, Jan 9, 2017 at 8:13 PM Prakash Chauhan <
> prakash.chauhan@ericsson.com>
> wrote:
>
> > Hi All ,
> >
> > Do we have an official procedure to rollback the upgrade of C* from 2.0.x
> > to 2.1.x ?
> >
> >
> > Description:
> > I have upgraded C* from 2.0.x to 2.1.x . As a part of upgrade procedure ,
> > I have to run nodetool upgradesstables .
> > What if the command fails in the middle ? Some of the sstables will be in
> > newer format (*-ka-*) where as other might be in older format(*-jb-*).
> >
> > Do we have a standard procedure to do rollback in such cases?
> >
> >
> >
> > Regards,
> > Prakash Chauhan.
> >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message