Aerospike Database versioning and releases
For the complete documentation index see: llms.txt
All documentation pages available in markdown.
This page describes the Aerospike Database versioning scheme, Linux OS compatibility by release, and support and end-of-life (EOL) schedules for current and past versions.
Aerospike Database uses a clear versioning scheme to help you plan upgrades with confidence. Each version comes with standard support, which you can read about on our Aerospike Support Policy page.
Version format
We use a four-part release number:
epoch.major.minor.patchFor example: release 8.0.0.1
| Part | Meaning | Breaking changes? |
|---|---|---|
| Epoch | Major architecture or protocol changes | yes |
| Major | New features, such as metrics, configuration, or log changes | yes |
| Minor | New features and improvements | no |
| Patch | Bug fixes and hotfixes | no |
We refer to the version as the first three parts. For example: version 8.0.0.
We recommend always running the most recent patch release for your version.
Breaking changes
Performing an upgrade without auditing breaking changes can cause production downtime.
A breaking change occurs when:
- metrics, configuration parameters, or info commands are renamed, removed, or changed.
- developer APIs are removed or significantly altered.
- ticker or audit logs change incompatibly.
Not considered breaking:
- Debugging info commands (
partition-info,dump-*,debug-*). - Debug-level log messages.
Deprecation and guarantees
- No breaking changes in minor or patch releases.
- Aerospike announces and logs deprecated features before removing them.
- Aerospike removes deprecated features only in a future epoch.
- The last major or minor release of an epoch provides an upgrade bridge to the next epoch.
Client compatibility
For information about client compatibility and support periods, see the Client Matrix.
Linux artifact policy
Aerospike provides build artifacts for operating system (OS) versions that are under active vendor security support. This includes Red Hat Enterprise Linux (RHEL) derivatives that maintain bug-for-bug binary compatibility with RHEL.
The following table lists the OS versions that support each Aerospike Database release. Aerospike provides patch releases to address security vulnerabilities in the underlying OS, as long as the OS itself is still actively supported. Distributions not included in the table, such as CentOS Stream, are not officially supported.
| Version | 8.1.2 | 8.1.1 | 8.1.0 | 8.0.0 | 7.2.0 |
|---|---|---|---|---|---|
| RHEL | 10, 91, 8 | 10, 91, 8 | 91, 8 | 91, 8 | 91, 8 |
| Rocky Linux | 10, 9, 8 | 10, 9, 8 | 9, 8 | 9, 8 | 9, 8 |
| AlmaLinux | 10, 9 | - | - | - | - |
| Ubuntu | 24.04, 22.04 | 24.04, 22.04, | 24.04, 22.04, | 24.04, 22.04, | 24.04, 22.04, |
| Debian | 13, 12 | 13, 12 | 12, 11 | 12, 11 | 12, 11 |
| Amazon Linux | AL2023 | AL2023 | AL2023 | AL2023 | AL2023 |
- Must have a kernel supporting 4K memory pages.
- Ubuntu 20.04 LTS reached end of standard support in April 2025.
Supported Aerospike Database versions
The support period for a major version begins on the GA date of its first release. Aerospike provides bug fixes and security patches only on the latest minor release of each supported major version.
| Version | General availability | Support EOL |
|---|---|---|
| 8.1.x | August 4, 2027 1 or August 4, 2028 2 | |
| 8.1.2 | April 16, 2026 | Latest |
| 8.1.1 | February 9, 2026 | Superseded |
| 8.1.0 | August 5, 2025 | Superseded |
| 8.0.0 | January 22, 2025 | January 21, 2027 |
| 7.2.0 | October 7, 2024 | October 6, 2026 |
- Two-year major version support end-of-life for Premium/Enhanced Support.
- Three-year major version support end-of-life for Silver/Gold/Platinum Support (starting with version 8.1).
End-of-life Aerospike Database releases
See Aerospike Support Policy for an explanation of GA and EOL.
| Version | Release date | End-of-life date |
|---|---|---|
| 7.1.0 | May 15, 2024 | May 14, 2026 |
| 7.0.0 | November 15, 2023 | November 14, 2025 |
| 6.4.0 | August 3, 2023 | August 2, 2025 |
| 6.3.0 | March 30, 2023 | March 29, 2025 |
| 6.2.0 | November 17, 2022 | March 30, 2024 |
| 6.1.0 | August 30, 2022 | February 28, 2025 |
| 6.0.0 | April 27, 2022 | August 30, 2023 |
| 5.7.0 | September 27, 2021 | April 27, 2023 |
| 5.6.0 | May 10, 2021 | September 27, 2022 |
| 5.5.0 | February 5, 2021 | May 10, 2022 |
| 5.4.0 | January 13, 2021 | February 5, 2022 |
| 5.3.0 | December 10, 2020 | January 13, 2022 |
| 5.2.0 | October 1, 2020 | December 10, 2021 |
| 5.1.0 | July 31, 2020 | October 1, 2021 |
| 5.0.0 | May 14, 2020 | July 31, 2021 |
| 4.9.0 | April 8, 2020 | May 14, 2021 |
| 4.8.0 | December 12, 2019 | April 8, 2021 |
| 4.7.0 | September 30, 2019 | December 12, 2020 |
| 4.6.0 | August 9, 2019 | September 30, 2020 |
| 4.5.3 | May 14, 2019 | August 9, 2020 |
| 4.5.2 | April 1, 2019 | May 14, 2020 |
| 4.5.1 | February 26, 2019 | April 1, 2020 |
| 4.5.0 | December 12, 2018 | February 26, 2020 |
| 4.4.0 | November 19, 2018 | December 12, 2019 |
| 4.3.1 | October 18, 2018 | November 19, 2019 |
| 4.3.0 | August 1, 2018 | October 18, 2019 |
| 4.2.0 | May 31, 2018 | August 1, 2019 |
| 4.1.0 | May 10, 2018 | May 31, 2019 |
| 4.0.0 | March 7, 2018 | May 10, 2019 |