I'm trying to understand restrictions of upgrade from/to different versions of cassandra.
On the one hand, Cassandra docs
http://docs.datastax.com/en/upgrade/doc/upgrade/cassandra/upgradeC_c.html
are saying "Cassandra 3.0.x restrictions: Upgrade from Cassandra 2.1 versions greater or equal to 2.1.9...", and I understand that as 'you couldn't upgrade to 3.0 from 2.1.8 and prior 2.1.* versions'.
On the other hand, there are no any restrictions on upgrading from, say, 2.1.8 (version prior to 2.1.9) to 2.1.11 (version grater then 2.1.9), in particular, 2.1.8->2.1.11 upgrade don't require upgrade of sstables.
So, could someone explain, why it's possible to upgrade from 2.1.9 to 3.0 but not from 2.1.8 to 3.0?
The docs restrict you from upgrading from early 2.1 versions to 3.0 because there are bug fixes and stability improvements in the later 2.1 releases that affect upgrades.
The best practice is to go to the latest patch on your branch before upgrading a major release. I.E. go to the latest 2.1.x and then go to 3.0.
Note: 3.0.0 dropped last night and it is very early in its release cycle. Make sure you test thoroughly in a qa environment before upgrading your production instance and follow the upgrade docs carefully.
Related
[Question posted by a user on YugabyteDB Community Slack]
The YugabyteDB core documentation for upgrades doesn't seem to address compatibility between versions. Can you upgrade from 2.8 to 2.13? Or is there a less direct path available?
The last upgrade attempted from 2.7 to 2.8 only worked for us building a 2.8 cluster and doing a snapshot restore with replication and then an application cutover. Is that the best method for moving from 2.8 to 2.13?
https://docs.yugabyte.com/latest/manage/upgrade-deployment/
In v2.8 we announced 'Seamlessly upgrade to major releases without stopping the database' see this release blog.
Also, just one upgrade could work, but we don’t officially support going from stable to latest releases or the reverse (latest to stable). There could be subtle issues because of backports status. So 2.8 to 2.12 is fine, the same 2.8 to 2.14(in future), or 2.9 to 2.13 — but 2.8 to 2.13 could face issues.
We do not officially support downgrades though.
We are trying to upgrade Rundeck version from 3.0.27 to the latest version (3.4.7)
We got below questions,
What is the approach to upgrade from 3.0.xxxx to 3.4.7? Could we do a direct upgrade or otherwise, if we have to run through multiple intermediary versions, what are those?
Does upgrading from 3.0.xxx to 3.4.7 fix the log4j vulnerability?
Please help to clarify above.
Thanks
Due to the big gap between 3.0.X and 3.4.X (and the upcoming 4.0.X) the best way to upgrade your instance is to create a fresh 3.4/4.0 instance and then import your projects and keys (exported previously), as a tip, try this on a non-prod environment first.
Rundeck 3.0.x uses log4j 1, so, even if the vulnerability doesn't affect explicitly the log4j 1.x EOL was in 2015 and isn't supported anymore, so, it's important to move to the latest version (Rundeck 3.4.10 at this moment).
As I have checked Scylla DB documentation and not found clearly where we can upgrade directly from Scylla version 2.1.x to 3.x.x directly.Is there any middle version upgrade required between 2.1.x to 3.x.x? Please help
The process is not documented, because it was not tested
You can follow the 2.1 to 2.2 instructions using 3.0, and everything should work, but the safest path will be 2.1 --> 2.2 --> 2.3 --> 3.0.2
Tzach
(ScyllaDB Product Manager)
we have a cassandra node with 3.9 version.
Is it possible to migrate to last stable version (3.0.11)?
(we dont use any special feature of 3.9.)
Please read downgrade session of this guide:
https://wiki.apache.org/cassandra/CompatibilityGuarantees
The main part:
Downgrading is only guaranteed within minor releases and only to the previous bug-fix release
Theoretically you can try downgrading 3.9 -> 3.7 -> 3.5... etc, but there is no grantees that this will work and will not do problems in the future. Test in some dev environment if you have to do it, or stay with 3.9...
What is the correct procedure of upgrading Datastax enterprise server. We have the datastax 3.0.2 running and we need to upgrade it to 4.0.1.
Can it be done using the Opscenter UI? Or do I need to manually upgrade the package on each machine.
Thanks.
There are pretty good upgrade instructions in the docs: http://www.datastax.com/documentation/upgrade/doc/upgrade/datastax_enterprise/upgradeTo4_0.html
You will need to manually upgrade each node, and it will take two upgrades, as you have to first upgrade to the latest DSE 3.2 release (3.2.6 right now), then upgrade to DSE 4.0 (and you should go to the latest which is 4.0.3 right now)