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
These are really good directions. Thanks a lot everyone!
@Kenneth - The cluster is comprised of 44 nodes, version 2.0.14, ~2.5TB of
data per node. It's gonna be a major version upgrade (or upgrades to be
exact... version 3.x is the target).
@Jeff, I have a passive DC. What if I upgrade the passiv
MOST minor versions support rollback - the exceptions are those where internode
protocol changes (3.0.14 being the only one in recent memory), or where sstable
format changes (again rare). No major versions support rollback - the only way
to do it is to upgrade in a way that you can effectively
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
My speculation is that IF (bigif) the sstable formats are compatible
between the versions, which probably isn't the case for major versions,
then you could drop back.
If the sstables changed format, then you'll probably need to figure out how
to rewrite the sstables in the older format and then ss
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* cluster t
