On Tuesday, January 10, 2017, Romain Hardouin <romainh...@yahoo.fr.invalid> wrote:
> To be able to downgrade we should be able to pin both commitlog and > sstables versions, e.g. -Dcassandra.commitlog_version=3 > -Dcassandra.sstable_version=jb > That would be awesome because it would decorrelate binaries version and > data version. Upgrades would be much less risky so I guess that adoption of > new C* versions would increase. > Best, > Romain > > Le Mardi 10 janvier 2017 6h03, Brandon Williams <dri...@gmail.com > <javascript:;>> a écrit : > > > 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 <j...@jonhaddad.com > <javascript:;>> 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.chau...@ericsson.com <javascript:;>> > > 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. > > > > > > > > > > > It would be amazing if the version could output commitlog and sstables at a specific version so roll backs are possible. -- Sorry this was sent from mobile. Will do less grammar and spell check than usual.
