OSSEVA FOR APACHE HADOOP

Hadoop support for clusters past end of life: Apache 2.x and 3.x, CDH and HDP

Hadoop support from OSSeva covers clusters that nobody ships fixes for. Apache declared Hadoop 3.2 end of life in December 2023, 2.10 has had no release since May 2022 and 3.3 none since June 2023, and Cloudera ended support for CDH 6.3 in March 2022 and HDP 3.1 in December 2021. Send your work email and an engineer replies within 1 business day.

Who it is forTeams running Apache Hadoop 2.8 to 3.3, CDH 5 or 6, or HDP 2.6 or 3.1 with HDFS, YARN, HBase or Hive on top
What you getSigned patched builds for HDFS and YARN on the line you run, with the bundled ZooKeeper patched alongside. Assure adds a cluster audit, a costed platform plan and 24/7 reactive support.
How it is pricedPer cluster, not per node or terabyte. Ask for a quote.
What happens nextYou send your work email, we confirm your version and components, and you get a coverage plan.

Reply within 1 business day · No commitment · or book a 15-minute call

Which vendors provide patched Apache Hadoop after end of life? Patched HDFS and YARN for Hadoop 2.10 to 3.3.

Last reviewed

Only your email is required · An engineer replies within 1 business day · No commitment

Trusted globally by enterprises

NokiaSquareLittle CaesarsPanasonic ConnectPaylocity

Which ZooKeeper sits under your Hadoop

HDFS failover and YARN ResourceManager HA both run through ZooKeeper. Each Hadoop line bundles its own, and most of them bundle a ZooKeeper line that ended years ago. Hadoop and bundled versions are from OSSeva's version list; ZooKeeper dates are from endoflife.date, checked 20 October 2026.

Hadoop lineBundled ZooKeeperThat ZooKeeper line's end of life
2.8, 2.93.4.61 Jun 2020
2.103.4.141 Jun 2020
3.13.4.131 Jun 2020
3.23.4.141 Jun 2020
3.33.6.330 Dec 2022
3.43.8.3 to 3.8.4Supported
3.53.8.6Supported
CDH 5 and 63.4.5 (Cloudera build)1 Jun 2020
HDP 2.6 and 3.13.4.6 (HDP build)1 Jun 2020

Write access to the ensemble is write access to cluster configuration: CVE-2021-25642 showed YARN's ZKConfigurationStore deserialising ZooKeeper data without checks.

ZooKeeper support →ZooKeeper end-of-life chart →

Hadoop and Cloudera end-of-life dates, checked 20 October 2026

Apache dates are from endoflife.date and the project's announcements (2.8 on 9 Mar 2020, 2.9 on 7 Sep 2020 and 3.2 on 22 Dec 2023 are the announcement dates; endoflife.date uses each line's last release day). Cloudera dates are from its support lifecycle policy.

LineEnd of life or supportStatus
Apache 2.89 Mar 2020End of life
Apache 2.97 Sep 2020End of life
Apache 3.222 Dec 2023End of life
Apache 2.10No end date set; last release 2.10.2, May 2022No release since
Apache 3.3No end date set; last release 3.3.6, June 2023No release since
CDH 5.14 to 5.16December 2020Cloudera support ended
CDH 6.2 and 6.3March 2022Cloudera support ended
HDP 2.6December 2020Cloudera support ended
HDP 3.1December 2021Cloudera support ended

Hadoop end-of-life chart →Hadoop extended support: patched HDFS and YARN →CDH extended support →

Advisories published since Hadoop 3.2 ended

Two entries in OSSeva's CVE directory were published after 22 December 2023 and name 3.2.4, the final 3.2 release. Both are fixed upstream only on 3.4.

CVEPublishedCVSSAffected range (NVD)Fixed upstream in
CVE-2024-234542024-09-256.2before 3.4.03.4.0
CVE-2025-278212026-01-267.33.2.0 to 3.4.13.4.2

OSSeva's directory holds ten Hadoop entries in total, so a short list here is not evidence the line is safe. Confirm any entry at nvd.nist.gov.

Why now

Most production Hadoop lines are past community support

The Hadoop community declared 2.8 end of life in March 2020, 2.9 in September 2020, 3.1 in June 2021 and 3.2 on 22 December 2023. The 2.10 line was never formally retired, but its last release, 2.10.2, shipped on 31 May 2022, and 3.3 has had nothing since 3.3.6 on 23 June 2023. Only 3.4 and 3.5 are moving, and Hadoop 3.5 servers require JDK 17.

CDH and HDP left vendor support years ago

Cloudera's lifecycle policy ended support for CDH 5.14 to 5.16 in December 2020, CDH 6.2 and 6.3 in March 2022, HDP 2.6 in December 2020 and HDP 3.1 in December 2021. The vendor path forward is CDP, which is a platform migration rather than an upgrade. Many clusters stayed where they were, running HDFS, YARN, HBase and Hive with no one shipping fixes for them.

The hidden ZooKeeper time bomb

HDFS automatic failover and YARN ResourceManager HA both run through ZooKeeper. CDH 5 and 6 ship ZooKeeper 3.4.5, HDP ships 3.4.6, and upstream Hadoop 3.3.6 bundles 3.6.3, all from lines past community end of life. Write access to that ensemble is worth more than it looks: CVE-2021-25642 showed YARN's ZKConfigurationStore deserialising ZooKeeper data without checks, so anyone who could write to ZooKeeper could run commands as the YARN user.

Versions covered

All versions below receive active CVE patches from OSSeva. Version numbers in monospace are exact release identifiers.

VersionStatusActive CVEs
2.8.x(Community EOL 9 Mar 2020 — OSSeva patched)EOLClean
2.9.x(Community EOL 7 Sep 2020 — OSSeva patched)EOLClean
2.10.x(No release since 31 May 2022 — OSSeva patched)ExtendedClean
3.1.x(Community EOL Jun 2021 — OSSeva patched)EOLClean
3.2.x(Community EOL 22 Dec 2023 — OSSeva patched)EOLClean
3.3.x(No release since 23 Jun 2023 — OSSeva patched)ExtendedClean
3.4.x(Upstream maintained, latest 3.4.3)ExtendedClean
3.5.x(Released 2 Apr 2026)CurrentClean
CDH 5.14 to 5.16(Cloudera EoS Dec 2020 — OSSeva patched)EOLClean
CDH 6.2 and 6.3(Cloudera EoS Mar 2022 — OSSeva patched)EOLClean
HDP 2.6(Cloudera EoS Dec 2020 — OSSeva patched)EOLClean
HDP 3.1(Cloudera EoS Dec 2021 — OSSeva patched)EOLClean
Apache Hadoop end of life dates for every version →

Running a Apache Hadoop version or build not listed here?

What you get

Three tiers — pick the level of engagement that matches your team's operational needs and compliance requirements.

OSSeva Patch

Patched, signed builds for Hadoop 2.8 to 3.3, CDH 5 and 6, and HDP 2.6 and 3.1.

  • Security backports for HDFS, YARN and MapReduce on end-of-life lines
  • CDH and HDP component builds, including HBase, Hive and ZooKeeper
  • Transitive dependency patching (Jetty, Netty, Jackson, log4j)
  • Tarball, RPM and parcel delivery
  • Signed artifacts (GPG) and VEX statements for scanner findings
  • Cluster security audit
  • 24/7 managed operations
Most popular

OSSeva Assure

Patch plus a full cluster audit and a costed platform plan.

  • Everything in Patch
  • NameNode, ResourceManager and ZooKeeper HA review
  • Kerberos, Ranger or Sentry policy and exposure audit
  • Component version map across every service on the cluster
  • SOC 2 / HIPAA attestation package with VEX for auditors
  • Migration plan to Hadoop 3.4 or 3.5, CDP, or a cloud platform
  • 24/7 reactive support

OSSeva Operate

Full MSP: 24/7 cluster monitoring, 15-min SLA, named engineers.

  • Everything in Assure
  • 24/7 HDFS capacity, NameNode and YARN queue monitoring
  • 15-minute P1 incident response SLA
  • Named senior Hadoop engineer
  • Failover testing and ZooKeeper quorum management
  • Rolling upgrade and migration execution
  • Quarterly capacity and cost reviews

All tiers priced per cluster/application — not per core.

How it installs

OSSeva artifacts arrive via your existing package infrastructure. Pull the patched version the same way you pull upstream today — just from the OSSeva registry.

Find the Hadoop, CDH or HDP version and its ZooKeeperbash
# The build string names the distribution (cdh, or an HDP stack number)
hadoop version | head -1

# HDP: installed stack versions
hdp-select versions

# CDH: parcels on this host
ls /opt/cloudera/parcels/

# The quorum NameNode failover and ResourceManager HA depend on
hdfs getconf -confKey ha.zookeeper.quorum
hdfs haadmin -getAllServiceState
yarn rmadmin -getAllServiceState

# Version the ensemble is actually running
echo srvr | nc zk1.internal 2181 | head -1
Maven: OSSeva Hadoop clientxml
<dependency>
  <groupId>io.osseva.hadoop</groupId>
  <artifactId>hadoop-client</artifactId>
  <version>3.3.6-osseva-1</version>
</dependency>

Migrate from Cloudera CDH and HDP past end of support

OSSeva ships patched builds for the CDH and HDP releases still in production, and for the upstream Hadoop lines the community has stopped releasing. HDFS, YARN, HBase, Hive and the shared ZooKeeper are patched together, so the cluster keeps running while the move to Hadoop 3.4 or 3.5, CDP, or a cloud platform is planned and carried out.

↗

Pricing model

OSSeva for Apache Hadoop is priced per cluster, not per node or per terabyte stored.

Learn about full migration →

Compliance library

📄SOC 2 compliance evidence package
Request →
📄Sample Audit Narrative
Request →
📄Pen-Test Report Summary
Request →
📄HIPAA Technical Safeguard Matrix
Request →

Questions

Frequently asked questions

Book a 15-minute call

Which Apache Hadoop versions are end of life?

The Hadoop community has declared 1.x, 2.0 to 2.9, and 3.0 to 3.2 end of life. The most recent were 2.9 in September 2020, 3.1 in June 2021 and 3.2 on 22 December 2023. Hadoop 3.4 and 3.5 are the lines still getting releases: 3.4.3 on 24 February 2026 and 3.5.0 on 2 April 2026.

Is Hadoop 2.10 end of life?

Not formally, but in practice there are no fixes. The last 2.10 release, 2.10.2, shipped on 31 May 2022, and the HBase reference guide notes that the Hadoop community has not officially retired 2.x even though no 2.x release has followed. OSSeva ships patched 2.10 builds today.

When did Cloudera support for CDH and HDP end?

Under Cloudera's lifecycle policy, CDH 5.14 to 5.16 reached end of support in December 2020, CDH 6.2 and 6.3 in March 2022, HDP 2.6 in December 2020 and HDP 3.1 in December 2021. A limited support period for eligible customers ended in September 2022 for CDH 6.2 and 6.3, and in June 2022 for HDP 3.1.

Can OSSeva support a CDH or HDP cluster that Cloudera no longer supports?

Yes. OSSeva is independent of Cloudera and ships patched builds for CDH 5 and 6 and HDP 2.6 and 3.1 components, including HDFS, YARN, HBase, Hive and ZooKeeper. The cluster keeps its layout and its data. Book a discovery call to map the components you run.

Why does Hadoop depend on ZooKeeper?

For high availability. HDFS automatic failover adds a ZooKeeper quorum and the ZKFailoverController, which uses a ZooKeeper lock to decide the active NameNode. YARN ResourceManager HA uses a ZooKeeper-based elector and, by recommendation, the ZooKeeper state store. Almost every production cluster runs both, so the ensemble is as critical as the NameNode.

Who provides Hadoop support besides the Apache Hadoop community?

Cloudera is the commercial vendor behind CDH, HDP and the CDP platform, and cloud providers offer managed Hadoop services on their own platforms. Third-party support companies are a third option. OSSeva fits where the cluster has to stay as it is: one contract across the stack, end-of-life Hadoop, CDH and HDP versions included, and support that runs wherever you run the cluster.

Does OSSeva support current Hadoop versions or only end-of-life ones?

Both. The versions list runs from Hadoop 2.8 to the current 3.5, plus CDH 5 and 6 and HDP 2.6 and 3.1, with patches active on every line. Patch ships signed builds for Hadoop 2.8 to 3.3, CDH and HDP, and Assure plans the move to Hadoop 3.4 or 3.5, CDP or a cloud platform. OSSeva Operate patches Critical CVEs (CVSS ≥ 9.0) within 48 hours and High within 7 days.

How is OSSeva Hadoop support priced?

OSSeva for Apache Hadoop is priced per cluster, not per node or per terabyte stored. Patch covers signed patched builds, Assure adds the cluster audit and migration plan with 24/7 reactive support, and Operate adds proactive 24/7 monitoring and end-to-end managed operations with a 15-minute P1 SLA. Book a discovery call for a quote.

Get a quote

Ready to get Apache Hadoop patched and supported?

Tell us your Apache Hadoop versions and an engineer replies within 1 business day with coverage and a price. Prefer a call? It takes 15 minutes.

Only your email is required · An engineer replies within 1 business day · No commitment

Prefer to talk or read more first?

Book a call