Key facts
- Cassandra 3.0 and 3.11 reached end of life when 5.0 became generally available on Sep 5, 2024.
- The project maintains about three releases: today 5.0, 4.1 and 4.0. 4.0 is maintained until the 6.0 release.
- Online, rolling upgrades are supported between adjacent major versions; skipping a major is not supported.
- CVE fixes may still be applied to unmaintained versions case by case, but there is no commitment.
Where support stands
The Apache Cassandra project announced in 2023 that 3.0 and 3.11 would reach end of life when 5.0 went GA. That happened on September 5, 2024. The project's download page now lists 5.0 as the latest release, 4.1 as the previous stable release (maintained until 7.0) and 4.0 as the older stable release (maintained until 6.0).
The project's release policy aims to keep three releases supported at any time, and its wiki states that support for 4.0 drops when 6.0 ships. If you are on 4.0 today, you have time, but not unlimited time.
Why you cannot jump straight to 5.0
Cassandra keeps compatibility between adjacent major versions so that clusters can be upgraded node by node while serving traffic. Upgrades that skip a major version are not supported. From 3.11 the supported route is to 4.0 or 4.1 first, then to 5.0.
A practical rolling upgrade
- Get healthy first. Run a full repair, clear pending compactions and confirm schema agreement across the ring.
- Check clients. Upgrade drivers to versions that support both the old and new protocol before touching servers.
- Review configuration changes. 4.x renamed and removed settings; 5.0 adds new features such as storage-attached indexes and trie-based memtables and SSTables that you can adopt later.
- Snapshot each node, then upgrade one node at a time: drain, stop, upgrade, start, verify.
- Upgrade SSTables once all nodes run the new version, then repeat for the next major.
- Rehearse the whole sequence on a staging ring with production-like data and traffic.
Managed alternatives
Some teams use the upgrade as a moment to move to a managed service such as DataStax Astra DB, Amazon Keyspaces, Azure Managed Instance for Apache Cassandra or a managed Cassandra provider. That removes upgrade work but changes cost, features and control, so compare them on your workload before deciding.
Sources
- Apache Cassandra blog: 3.0.x and 3.11.x end of life at the 5.0 release
- Apache Cassandra downloads and maintained versions
- Apache Cassandra wiki: Patching, release versioning and LTS releases
- endoflife.date: Apache Cassandra
Checked on November 15, 2026. Vendors can change dates and terms, so confirm against the source before you rely on them.



