Re: Rollback procedure for Cassandra Upgrade.

2017-01-10 Thread Edward Capriolo
On Tuesday, January 10, 2017, Romain Hardouin 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

Re: Rollback procedure for Cassandra Upgrade.

2017-01-10 Thread Jeremy Hanna
See the comment thread on https://issues.apache.org/jira/browse/CASSANDRA-8928 (add downgradesstables) > On Jan 10, 2017, at 5:00 AM, Jonathan Haddad wrote: > > There's no downgrade procedure. You either upgrade or you

Re: Rollback procedure for Cassandra Upgrade.

2017-01-10 Thread Romain Hardouin
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

Re: Rollback procedure for Cassandra Upgrade.

2017-01-09 Thread Brandon Williams
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 wrote: > There's no downgrade procedure. You either upgrade or you go back to a > snapshot from the

Re: Rollback procedure for Cassandra Upgrade.

2017-01-09 Thread Jonathan Haddad
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 wrote: > Hi All , > > Do we have an official procedure to rollback the upgrade of C* from 2.0.x > to 2.1.x ? > >