// Hortonworks HDP extended support

Still running Hortonworks HDP?
HDP 3.1 left support in 2021. Patched builds are available now.

Hortonworks Data Platform 2.6 reached end of support in December 2020 and HDP 3.1 in December 2021, and limited support for eligible HDP 3.1 customers ended in June 2022. HDP 2.6.5, 3.1.0 and 3.1.5 all bundle ZooKeeper 3.4.6, from an upstream line that has been end of life since June 2020. OSSeva ships patched builds of the HDP components and the ZooKeeper under them, so the cluster keeps running on supported software while you plan what comes next.

HDP 3.13.0HDP 2.62.5 and earlierZooKeeper 3.4.6HDFS, YARN, HBase, Hive

Trusted globally by enterprises

Henry ScheinEnbridgeGojekMicrosoft

Why HDP clusters are still running

HDP has no next version to upgrade to, so every option is a migration.

Nothing comes after HDP 3.1

The support lifecycle policy lists no HDP release after 3.1. Moving on means a different distribution or a different platform, and each of those is a migration rather than an upgrade.

ZooKeeper 3.4.6 under HA, HBase and Hive

NameNode HA, ResourceManager HA, HBase and HiveServer2 share one ensemble. The upstream 3.4 line never received a fix for CVE-2023-44981 and ships log4j 1.2.17, so check the vendor build's fixed-CVE list before assuming either way.

Findings keep arriving

Scanners match the HDP component versions against public advisories every week. Without patched builds, each finding needs a written exception.

The dates that matter

  1. 2019-08

    End of support for HDP 2.5.

  2. 2020-06-01

    ZooKeeper 3.4 end of life upstream. HDP 2.6 and 3.1 bundle 3.4.6.

  3. 2020-12

    End of support for HDP 2.6.

  4. 2021-07

    End of support for HDP 3.0.

  5. 2021-12

    End of support for HDP 3.1.

  6. 2022-06-30

    Limited support for eligible HDP 3.1 customers ends.

What OSSeva delivers

1

Patched HDP components

Signed builds with backported security fixes for HDFS, YARN, HBase and Hive on HDP 2.6 and 3.1, matched to the HDP release you run so the cluster keeps its version and configuration.

HDP 2.6 and 3.1HDFS, YARN, HBase, HiveSigned builds
2

Patched ZooKeeper 3.4.6

The bundled ensemble, patched and dropped in with configuration and data unchanged, plus VEX statements for the findings your scanner raises against it.

ZooKeeper 3.4.6Drop-inVEX
3

Migration off HDP

A migration plan per workload to a current distribution, upstream Apache releases or a cloud platform, carried out with your team while the patched cluster keeps running.

Upstream ApacheCloud platformsCut-over plan

Your options, compared

OptionWhat you getTrade-off
Move to a current commercial distributionVendor support for current Hadoop componentsA platform migration, since there is no in-place path from HDP, and a new subscription.
Migrate to a cloud data platformManaged storage and computeData movement and job rewrites across several quarters.
OSSeva extended supportPatched HDP components and ZooKeeper today, and help with the moveA subscription while HDP stays in production.
Stay on unsupported HDPNothingFindings accumulate on the cluster that holds the most data.

End-of-support dates from Cloudera's support lifecycle policy, which covers HDP. Bundled ZooKeeper versions from the HDP 2.6.5, 3.1.0 and 3.1.5 component version lists. ZooKeeper advisories from zookeeper.apache.org/security.

Frequently asked questions

When did HDP reach end of life?

HDP 2.6 support ended in December 2020, HDP 3.0 in July 2021 and HDP 3.1 in December 2021. Limited support for eligible HDP 3.1 customers ran to 30 June 2022.

Who provides Hortonworks support now?

HDP falls under Cloudera's support lifecycle policy, and every HDP line is past its end-of-support date. OSSeva supports HDP 2.6 and 3.1 clusters as they are, with patched components and ZooKeeper builds shipping now.

Which ZooKeeper version does HDP ship?

ZooKeeper 3.4.6 with vendor patches, in HDP 2.6.5, 3.1.0 and 3.1.5. The upstream 3.4 line reached end of life on 1 June 2020.

Can we upgrade HDP in place?

Not to a newer HDP, because the lifecycle policy lists nothing after 3.1. Any move is a migration, which is why patched builds matter while it is planned.

Which support tier fits an HDP cluster?

Patch covers signed builds with backported fixes. Assure adds an ensemble audit and an attestation package for auditors. Operate adds 24/7 monitoring and named engineers.

Keep HDP patched while the migration is planned.

Start with Patch today. Add Assure or Operate when the cluster needs them.