I wanted to know till when Cassandra 3.11.10 is supported.
Is there some place where this information is available for all currently supported versions of Cassandra?
https://cassandra.apache.org/_/download.html specifies the maintained until date only for the latest available versions.
Download the latest Apache Cassandra 3.11 release: Released on
2022-02-08 Maintained until 4.2.0 release (May-July 2023)
This section covers all 3.11.x releases. 3.11.10 should be good until mid 2023.
Related
Currently we are using Java Datastax Drivers Version 3.7.2 to connect to Open source Apache Cassandra Version 3.11.9.
We are planning on to upgrade to Open Source Apache Cassandra Version 4 , Can someone please let me know what are the recommended Java Datastax Drivers version to connect to Cassandra Version 4. I see in this article Datastax had mentioned that Datastax Drivers Version 3.11 is partially compatible with Cassandra Version 4.X and did not have much information on what they mean about partially compatible?
https://docs.datastax.com/en/driver-matrix/docs/java-drivers.html
First, Apache Cassandra® 4.1 is already released last Dec and you may want to look at upgrading to that as opposed to 4.0.x.
Next, partially compatible is also explained in the docs section as,
^4^ Limited to the Cassandra 3.x and 2.2.x API.
Also, I'm taking excerpts from the mailing list discussions here.
Neither the 4.x nor the 3.x Java drivers are in maintenance mode at the moment. It is very much true that any new Java driver features will be developed on the 4.x branch and in general will not be ported to 3.x. 3.x will continue to receive CVE and other critical bug fixes but as mentioned there are no plans for this branch to receive any new features. It's not completely impossible that a specific feature or two might make it's way to 3.x on a case-by-case basis but if you're planning for the future with 3.x you should do so with the expectation that it will receive no new features.
&
Having said that, I would strongly recommend and encourage you to upgrade to the 3.11.3 version of the java driver (released on Sep 20, 2022) which is directly binary compatible with the version that you're using today, 3.7.2 (released on Jul 10, 2019), to leverage features and fixes (including many CVE patches). In addition, I would also suggest you to sketch out a plan to upgrade your apps to 4.x driver or look into modernizing to interact with your Apache Cassandra®/DSE®/Astra DB® cluster via the Stargate® APIs.
I'm planning to upgrade my 100+ nodes cassandra baremetal cluster with current version 2.2.19.
Please let me know if I can upgrade from 2.2.19 to 3.11 directly ?
Also what is the timeline to wait to upgrade to next version i.e from 3.11 -> 4.x, can I upgrade to the latest version ( 2.2.19 -> 3.11 -> 4.x ) in single upgrade plan ?
Thank you
It isn't an issue upgrading a Cassandra 2.2.19 cluster directly to the latest 3.11 release.
There is no requirement to have a break to upgrade to C* 4.x -- upgrading the nodes isn't going to be an issue at all. What you need to be concerned with is whether you need to upgrade the driver you're using.
If you do need to upgrade the driver, you need to refactor your application if the new version of the driver is not binary-compatible with the old version. For example, upgrading from Java driver 3.x to 4.x has breaking changes (see the Java driver v4 Upgrade Guide for details).
Before upgrading your cluster, make sure you familiarise yourself with the upgrade instructions for the various releases:
Cassandra 3.11 NEWS.txt
Cassandra 4.0 NEWS.txt
Cassandra 4.1 NEWS.txt
Good day, does anyone find information about log4j involving Hazelcast 3.11?
In the official website doesn't show anything about the log4j vulnerability.
The vulnerability is addressed in Log4j2.15.0. Hazelcast team is currently working to release fixes to add this for the versions listed above. UPDATE on December 15, 2021: IMDG 4.0.4, 4.1.7 and 4.2.3 have been released. Remaining release of Hazelcast 5.0.1 and Hazelcast Jet 4.5.2 is being worked on.
Users that explicitly use a vulnerable Log4j2 library are advised to upgrade to Log4j2.15.0 as soon as possible.
For more: Security Advisory for "Log4Shell" CVE-2021-44228 and CVE-2021-45046
Is it possible to upgrade Apache Cassandra 2.1.9+ to Apache Cassandra 3.1+ directly?
The release notes for 3.0 mention direct upgrades need a minimum of Apache Cassandra 2.1.9+, but all further releases of Apache Cassandra don't mention whether an intermediate version is needed.
Yes, you can upgrade from Cassandra 2.1.9 (or higher) to Cassandra 3.1 (or higher).
As stated in the DataStax dev blog in June of 2015, Cassandra moved to a "tick-tock" release cycle with version 3. The details of which you can get from the link, but the main point is that the release structure of 3.x is not the same as it was with 2.x.
Cassandra 2.0, 2.1, and 2.2 were different enough in terms of features and storage modifications that they required a structured upgrade path. Cassandra 3.x does not. You can upgrade directly to 3.1, 3.4, or 3.10 (just released). As long as you meet the 3.0 upgrade requirements (Cassandra version >= 2.1.9) you don't need to worry about intermediate upgrades with the 3.x line.
As per my experience about upgrading Cassandra if you are doing upgrade from below 2.1.9 then you must upgrade to 2.1.9 or above then you can directly upgrade to 3.x version. There is no issue in this way and you upgrade will be successful but if you are doing it on production make sure to do rolling upgrade with all prerequisites and backup. Don't forget to run nodetool upgradesstables after Cassandra upgrade.
When upgrading from 2.2.8 to 3.11.6 , while upgrading the last node in the cluster, when last node on which the upgrade is left the client is not able to connect to cluster untill upgrade on the last node finishes. We are having a 5 node cassandra cluster running on aws ec2.
Do we have to upgrade to interim version DSE 4.6 then go for 4.8 ?
we are using DSE 4.5.1 for our Cassandra db only .
You should be able to upgrade to 4.8.x from 4.5.y.
Cassandra major release (e.g. 2.1 to 3.0) or major point release (e.g. 2.0 to 2.1), might involve sstable version change which will require running upgradeSSTables from nodetool. Cassandra sstable versions are normally backward compatible with previous version but not before that. That’s why if you want to say upgrade to 2.2 from 2.0 then you would first upgrade to 2.1. While you are doing a rolling upgrade to 2.1 from 2.0 your cluster will be in mixed mode (some nodes still on 2.0 while other upgraded to 2.1). This will be OK because Cassandra will support reading from previous sstable version. But before you can upgrade to 2.2 you need to upgrade sstables. Once that is done (nodetool upgradesstables) on all the nodes then you can upgrade to 2.2.
In above example I have talked about Apache Cassandra version, but similar logic can be applied to DSE. Here is a link of which Cassandra version is used by various DSE and other upgrade related info
upgradedDSE47or48
The usual restrictions and limitation apply while cluster is in mixed mode as mentioned here