minor version upgrades).
Sean Durity
From: shalom sagges [mailto:shalomsag...@gmail.com]
Sent: Wednesday, February 28, 2018 3:54 AM
To: user@cassandra.apache.org
Subject: [EXTERNAL] Re: Version Rollback
These are really good directions. Thanks a lot everyone!
@Kenneth - The cluster is comprised
rewrite the sstables in the older format and then sstableloader them
> in the older-version cluster if need be. Alas, while there is an sstable
> upgrader, there isn't a downgrader AFAIK.
>
> And I don't have an intimate view of version-by-version sstable format
> changes a
rmat
> changes and compatibilities. You'd probably need to check the upgrade
> instructions (which you presumably did if you're upgrading versions) to tell.
>
> Basically, version rollback is pretty unlikely to be done.
>
> The OTHER option:
>
> 1) build a new
I wonder if you could use Apache Spark to do it?
Kenneth Brotman
From: Carl Mueller [mailto:carl.muel...@smartthings.com]
Sent: Tuesday, February 27, 2018 9:22 AM
To: user@cassandra.apache.org
Subject: Re: Version Rollback
My speculation is that IF (bigif) the sstable formats are
e
instructions (which you presumably did if you're upgrading versions) to
tell.
Basically, version rollback is pretty unlikely to be done.
The OTHER option:
1) build a new cluster with the new version, no new data.
2) code your driver interfaces to interface with both clusters. Write to
both
Could you tell us the size and configuration of your Cassandra cluster?
Kenneth Brotman
From: shalom sagges [mailto:shalomsag...@gmail.com]
Sent: Tuesday, February 27, 2018 6:19 AM
To: user@cassandra.apache.org
Subject: Version Rollback
Hi All,
I'm planning to upgrade my C* cl
Hi All,
I'm planning to upgrade my C* cluster to version 3.x and was wondering
what's the best way to perform a rollback if need be.
If I used snapshot restoration, I would be facing data loss, depends when I
took the snapshot (i.e. a rollback might be required after upgrading half
the cluster fo
