Apache Hadoop End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Apache Hadoop versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
Apache Hadoop 3.5 is supported, with no end-of-life or end-of-support date announced yet. 14 of 18 tracked Apache Hadoop versions are past end of life; the most recent to reach it, 3.2, did so on December 21, 2023. The full Apache Hadoop lifecycle, with every version's release and end-of-support date, is in the table below.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1.0 | 1.0.4 | Dec 27, 2011 | Oct 12, 2012 | 5095 days past EOL | EOL |
| 1.1 | 1.1.2 | Oct 15, 2012 | Mar 6, 2013 | 4950 days past EOL | EOL |
| 1.2 | 1.2.1 | May 14, 2013 | Aug 4, 2013 | 4799 days past EOL | EOL |
| 2.2 | 2.2.0 | Oct 16, 2013 | Oct 16, 2013 | 4726 days past EOL | EOL |
| 2.3 | 2.3.0 | Feb 24, 2014 | Feb 24, 2014 | 4595 days past EOL | EOL |
| 2.4 | 2.4.1 | Apr 10, 2014 | Jun 30, 2014 | 4469 days past EOL | EOL |
| 2.5 | 2.5.2 | Sep 11, 2014 | Nov 19, 2015 | 3962 days past EOL | EOL |
| 2.6 | 2.6.5 | Nov 30, 2014 | Oct 10, 2016 | 3636 days past EOL | EOL |
| 2.7 | 2.7.7 | Jul 6, 2015 | Jul 18, 2018 | 2990 days past EOL | EOL |
| 2.8 | 2.8.5 | Mar 24, 2017 | Sep 18, 2018 | 2928 days past EOL | EOL |
| 2.9 | 2.9.2 | Nov 17, 2017 | Nov 20, 2018 | 2865 days past EOL | EOL |
| 3.0 | 3.0.3 | Dec 18, 2017 | Jun 10, 2018 | 3028 days past EOL | EOL |
| 3.1 | 3.1.4 | Apr 5, 2018 | Aug 18, 2020 | 2228 days past EOL | EOL |
| 3.2 | 3.2.4 | Jan 21, 2019 | Dec 21, 2023 | 1008 days past EOL | EOL |
| 2.10 | 2.10.2 | Oct 29, 2019 | TBD | Supported | Active |
| 3.3 | 3.3.6 | Jul 15, 2020 | TBD | Supported | Active |
| 3.4 | 3.4.3 | Mar 17, 2024 | TBD | Supported | Active |
| 3.5 | 3.5.0 | Apr 2, 2026 | TBD | Supported | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/apache-hadoop)
Apache Hadoop lifecycle status — the real story
Apache Hadoop's release page is explicit about where fixes go: the 3.3.x line is the sole branch receiving fixes for anything other than critical security or data-integrity issues, and users of Hadoop 2.x and 3.2 are told to upgrade to it. Newer 3.4.x releases (3.4.1 on October 18, 2024) are the current feature line. There is no published end-of-life date per line — the end-of-life dates above mark when a line stopped receiving releases.
A 2.x cluster is therefore outside all routine maintenance, and has been since the project's guidance changed.
Verified against the vendor's lifecycle documentation on August 22, 2026.
Apache Hadoop release and support pattern
Across the 18 release lines with a published release date, Apache Hadoop has shipped a new line roughly every 7 months (median interval). A line typically stays supported for about 1.1 years from its release to its end-of-life date (measured on the 12 lines with both dates published).
Of the 18 release lines tracked, 14 are past end of life and 4 are still within support. The newest line, 3.5, was released April 2, 2026. No end-of-life date is currently published for the 4 supported lines.
Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.
What does Apache Hadoop end of life mean for your organization?
When a version of Apache Hadoop reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no vendor patch is coming. This is one of the most dangerous gaps in enterprise security posture.
Organizations running EOL Apache Hadoop should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Your options when Apache Hadoop reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Formalizing decisions like this across your estate? Our free EOL policy template is a ready-to-adopt policy with risk tiers, remediation SLAs, and audit mapping — no signup, free to use and share.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Apache Hadoop versions. This is a bridge, not a permanent solution — plan your migration in parallel.
Apache Hadoop has 14 versions past end of life — security patches have stopped, but CVE disclosures haven't. Extended support past the official date exists for many products in this position — whether it exists for Apache Hadoop is exactly what we check. Tell us where to reach you and we'll reply with matched options and pricing guidance — or an honest "no vendor covers this."