EOL.WikiEOL.Wiki
← ← Back to all products

Apache HBase

Active
DatabasesLatest Version: 2.6.6Latest Release: Jun 9, 2026

Apache HBase is a distributed, scalable big data store modeled after Google's Bigtable.

Support summary

Apache HBase currently has supported cycles. Track the next EOL date and validate upgrades before your change window.

What do EOL and support statuses mean?

Next EOL

No announced EOL date is currently listed.

Supported cycles

2

0 lts

Versions

6

Latest Version

2.6.6

Active Support

2

EOL

4

Lifecycle Timeline

Today
2.6
2.6
2.5
2.5
2.4
2.4
2.3
2.3
1.7
1.7
2.2
2.2
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
2.6May 17, 2024YesNo2.6.6No
Active
2.5Aug 31, 2022YesNo2.5.15No
Active
2.4Dec 15, 2020NoMay 25, 20252.4.18No
EOL
2.3Jul 13, 2020NoOct 19, 20212.3.7No
EOL
1.7Jun 12, 2021NoAug 9, 20221.7.2No
EOL
2.2Jul 25, 2019NoApr 19, 20212.2.7No
EOL

Data sources

Frequently Asked Questions

Which versions of Apache HBase have reached end of life?
The following Apache HBase versions have reached end of life and no longer receive security updates: 2.4, 2.3, 1.7, 2.2. It is recommended to upgrade to a supported version.
Is it safe to continue using Apache HBase 2.4?
Apache HBase 2.4 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of Apache HBase?
The latest version of Apache HBase is 2.6.6, released in the 2.6 release cycle.
How many versions of Apache HBase are currently supported?
Apache HBase currently has 2 actively supported version(s): 2.6, 2.5.
When does Apache HBase 2.6 reach end of life?
Apache HBase 2.6 does not have a specific end-of-life date announced yet.
What should I do when Apache HBase reaches end of life?
When a Apache HBase version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.