Apache Spark End of Life Dates

other

Developers working with large-scale data processing rely on a unified analytics engine to streamline their workflow, and Apache Spark has been a go-to solution since its inception. Created to provide an interface for programming clusters with implicit data parallelism and fault tolerance, Apache Spark has become an essential tool for many. The Apache Software Foundation maintains this open-source project, ensuring it remains a viable option for developers. With its ability to handle massive amounts of data, Spark has become a staple in the industry, and its widespread adoption is a testament to its effectiveness.

The end-of-life landscape for Apache Spark is characterized by a significant number of versions that are no longer supported, with 17 out of 20 versions having reached their end-of-life. Currently, only three versions remain active, with the latest stable version being 3.5.8. Looking ahead, the next version slated to reach its end-of-life is version 4.0, which is set to expire on November 23, 2026. This gives developers ample time to plan and prepare for the transition to a newer version. The most recent end-of-life date was October 21, 2024, for version 3.4, marking the end of support for that particular iteration.

From a security standpoint, Apache Spark has a spotless record, with no known CVEs tracked to date. This means that there are no critical vulnerabilities to speak of, and as a result, there is no most affected version. With no CVEs to contend with, developers can focus on utilizing Spark's capabilities without worrying about potential security risks. Given its clean security record and the fact that only a few versions are still supported, developers should take this opportunity to review their current Spark setup and plan for any necessary upgrades to ensure continued support and optimal performance.

Last updated: Jul 24, 2026

VersionReleasedActive supportEOL dateUntil EOLLatestCVEsStatusAlert me
4.2 Jul 14, 2026Jan 11, 2028in 536d4.2.0Active
4.1 Dec 11, 2025Jun 11, 2027in 322d4.1.3Active
4.0 May 19, 2025Nov 23, 2026in 122d4.0.4Active
3.5 LTSSep 9, 2023Nov 30, 2027in 494d3.5.9Active
3.4 Apr 7, 2023Oct 21, 2024641d ago3.4.4EOL
3.3 Jun 9, 2022Dec 9, 2023958d ago3.3.4EOL
3.2 Oct 6, 2021Apr 9, 20231202d ago3.2.4EOL
3.1 Feb 22, 2021Aug 22, 20221432d ago3.1.3EOL
3.0 Jun 6, 2020Dec 6, 20211691d ago3.0.3EOL
2.4 LTSOct 29, 2018May 9, 20211902d ago2.4.8EOL
2.3 Feb 22, 2018Aug 25, 20192525d ago2.3.4EOL
2.2 Jun 30, 2017Jan 30, 20192732d ago2.2.3EOL
2.1 Dec 15, 2016Jun 26, 20182950d ago2.1.3EOL
2.0 Jul 19, 2016Dec 15, 20163508d ago2.0.2EOL
1.6 Dec 21, 2015Jul 19, 20163657d ago1.6.3EOL
1.5 Sep 8, 2015Dec 21, 20153868d ago1.5.2EOL
1.4 Jun 2, 2015Sep 8, 20153972d ago1.4.1EOL
1.3 Mar 5, 2015Jun 2, 20154070d ago1.3.1EOL
1.2 Dec 10, 2014Apr 5, 20154128d ago1.2.2EOL
1.1 Sep 3, 2014Dec 10, 20144244d ago1.1.1EOL
1.0 May 26, 2014Sep 3, 20144342d ago1.0.2EOL

Data sourced from endoflife.date · CVE data from NVD

Related technologies

Frequently Asked Questions