---
title: "Aerospike Database 7.2.0 Release Notes"
description: "Aerospike Database 7.2.0 Release Notes featuring XDR version shipping controls and active rack configuration."
---

# Aerospike Database 7.2.0 Release Notes

> For the complete documentation index see: [llms.txt](https://aerospike.com/docs/llms.txt)
> 
> All documentation pages available in markdown.

October 7, 2024  |  **[Download](https://aerospike.com/download/)**

## New in this version

This version implements a variety of new features and improvements to enhance performance, usability, and reliability.

### New features

-   XDR version shipping controls: Database 7.2.0 introduces a dynamically configurable mechanism to control how XDR ships versions of modified records, through two new configuration parameters: [`ship-versions-policy`](https://aerospike.com/docs/database/reference/config#xdr__ship-versions-policy) and [`ship-versions-interval`](https://aerospike.com/docs/database/reference/config#xdr__ship-versions-interval)
-   Active rack - with the [`active-rack`](https://aerospike.com/docs/database/reference/config#namespace__active-rack) namespace configuration parameter, you can designate a particular [`rack-id`](https://aerospike.com/docs/database/reference/config#namespace__rack-id) to hold all master partition copies. See [Designate an active rack](https://aerospike.com/docs/database/manage/namespace/rack-aware#designate-an-active-rack).
-   See the detailed [complete list](#complete-list-of-changes) of all new features.

### Updates

-   Aerospike Tools 11.1.0.
-   See [Platform support and compatibility](https://aerospike.com/docs/database/reference/platform-support) for all currently supported platforms.

## Improvements and enhancements

-   The `active-rack` configuration allows one availability zone (AZ), represented by a distinct `rack-id`, to own all partition masters.
-   When quiescing nodes in AP namespaces where the replication factor (RF) is greater than or equal to the number of nodes in the subcluster, the effective RF is automatically decremented so that the quiesced node gives up partition ownership (becomes a non-replica), equivalent to the node leaving the cluster.
-   New best practice checks at startup:
    -   `rmem-max` (which comes from /proc/sys/net/core/rmem\_max) must be greater than 15MiB
    -   `wmem-max` (which comes from /proc/sys/net/core/wmem\_max) must be greater than 5MiB
    -   The `asd-systemd-helper` script used to set rmem\_max and wmem\_max, and also potentially raised shmmax to 1GiB (less useful now that data may also use shmem). This script has been removed.

### Breaking changes

-   Removed support for using `yes` or `no` for boolean parameters. All boolean parameters must use `true` or `false`.
    -   Affects the `ignore-migrations` field in the [`cluster-stable`](https://aerospike.com/docs/database/reference/info?search=cluster-stable#cluster-stable) command.

## Configuration item changes

| Item | Action | Notes |
| --- | --- | --- |
| [`active-rack`](https://aerospike.com/docs/database/reference/config#namespace__active-rack) | added | The rack that owns all of the masters in AP and SC namespaces. |
| [`ship-versions-policy`](https://aerospike.com/docs/database/reference/config#xdr__ship-versions-policy) | added | Stops XDR from skipping record versions. |
| [`ship-versions-interval`](https://aerospike.com/docs/database/reference/config#xdr__ship-versions-interval) | added | Relevant only if `ship-versions-policy` is true. With value 0, every version is shipped. |

## Metrics changes

| Item | Action | Description |
| --- | --- | --- |
| [`early_tsvc_batch_sub_error`](https://aerospike.com/docs/database/reference/metrics#node_stats__early_tsvc_batch_sub_error) | removed |  |
| [`early_tsvc_udf_sub_error`](https://aerospike.com/docs/database/reference/metrics#node_stats__early_tsvc_udf_sub_error) | removed |  |
| [`early_tsvc_ops_sub_error`](https://aerospike.com/docs/database/reference/metrics#node_stats__early_tsvc_ops_sub_error) | removed |  |
| [`effective_active_rack`](https://aerospike.com/docs/database/reference/metrics#namespace__effective_active_rack) | added | Roster’s current active-rack for SC namespaces. |
| [`fail_xdr_key_busy`](https://aerospike.com/docs/database/reference/metrics#namespace__fail_xdr_key_busy) | added | Counts how many XDR key busy errors have occurred. |
| [`nsup_xdr_key_busy`](https://aerospike.com/docs/database/reference/metrics#namespace__nsup_xdr_key_busy) | added | Counts how many NSUP deletes (expirations and evictions) had to wait for a previous version to ship. |

## Info command updates

::: note
-   Make sure you are not passing invalid parameters as inputs are now checked more strictly. The reason for an info command failure is often articulated more clearly.
-   Most parameter check failures either result in error code 4 `AS_ERR_PARAMETER` or error code 20 `AS_ERR_NAMESPACE` - the latter only when parsing a namespace parameter.
:::

| Item | Action | Description |
| --- | --- | --- |
| [`get-config`](https://aerospike.com/docs/database/reference/info#get-config) | modified | `id` parameter is now deprecated and `namespace` is accepted in its place. |
| [`set-config`](https://aerospike.com/docs/database/reference/info#set-config) | modified | `id` parameter is now deprecated and `namespace` is accepted in its place. |
| [`sindex-create`](https://aerospike.com/docs/database/reference/info#sindex-create) | modified | `ns` parameter is now deprecated and `namespace` is accepted in its place. |
| [`sindex-delete`](https://aerospike.com/docs/database/reference/info#sindex-delete) | modified | `ns` parameter is now deprecated and `namespace` is accepted in its place. |
| `sindex-exists` | modified | `ns` parameter is now deprecated and `namespace` is accepted in its place. |
| [`sindex-list`](https://aerospike.com/docs/database/reference/info#sindex-list) | modified | `ns` parameter is now deprecated and `namespace` is accepted in its place. |
| [`sindex-stat`](https://aerospike.com/docs/database/reference/info#sindex-stat) | modified | `ns` parameter is now deprecated and `namespace` is accepted in its place. |
| `xdr-dc-state` | modified | `ns` parameter is now deprecated and `namespace` is accepted in its place. |
| [`xdr-get-filter`](https://aerospike.com/docs/database/reference/info#xdr-get-filter) | modified | `ns` parameter is now deprecated and `namespace` is accepted in its place. |
| [`get-config:context=xdr;dc=DC-NAME;`](https://aerospike.com/docs/database/reference/info#get-config) | modified | `ns` parameter is now deprecated and `namespace` is accepted in its place. |
| [`get-stats:context=xdr;dc=DC-NAME;`](https://aerospike.com/docs/database/reference/info#get-stats) | modified | `ns` parameter is now deprecated and `namespace` is accepted in its place. |

Error responses to info commands have been standardized to the format `ERROR:<code>:<msg>`

-   `dump-cluster`, `dump-fabric`, `dump-hb`, `dump-hlc`, `dump-migrates`, and `dump-wb-summary` used to return an `error` response format.
-   `histogram` used to return `error-this-is-a-message`.
-   `recluster` used to return `ERROR` when the clustering layer responded with anything other than success or ignored.
-   `tip` and `tip-clear` used to return an `error` response format.

The following minor changes were also made to the info command cleanup:

-   `sindex-create` and `sindex-delete` now return `ok` instead of `OK` on success.
-   Fixed various error codes and error messages to be more appropriate and clear.

## Server log changes

| Item | Action | Notes |
| --- | --- | --- |
| [`special-errors: key-busy` 123 …](https://aerospike.com/docs/database/reference/logs#info__994802748) | enhanced | Now reads `special-errors: key-busy` (1234, 40) where the second number in the parentheses is the XDR key busy count. |
| [`early-fail:`](https://aerospike.com/docs/database/reference/logs#info__1251367823) | modified | Now reads `early-fail: demarshal 0 tsvc-client 1 tsvc-from-proxy 0 tsvc-from-proxy-batch-sub 0` |

## Error code changes

| Item | Action | Notes |
| --- | --- | --- |
| [AS\_ERR\_XDR\_KEY\_BUSY](https://aerospike.com/docs/database/reference/error-codes) | added | Error code 32. Occurs when a write must wait on a previous version to ship and either the write times out or there are too many writes waiting. |

## Tools changes

### Changes in Tools 11.1.0

See [Tools 11.1.0 Release Notes](https://aerospike.com/docs/database/tools/release-notes#tools-1110).

## Client/server feature compatibility

For a complete list of client features and the Aerospike Database versions that support them, see the [Client Matrix](https://aerospike.com/docs/develop/client-matrix).

### Minimum compatible client versions

For full feature access in Database 7.2.0:

-   Java client 8.1.0
-   Python client 15.0
-   C# client 7.2.0
-   C client 6.6.0
-   Go client 7.2.0
-   Node.js client 5.12
-   PHP 1.0

## Ecosystem compatibility

### Compatible connector versions

-   Trino connector 1.7 or later
-   Spark connector 3.2.2 or later

## Prerequisites and notes

For upgrade instructions, see [Upgrade or Repair Server](https://aerospike.com/docs/database/install/upgrade).

## Complete list of changes

| ID | Description |
| --- | --- |
| AER-6749 | (BALANCE) For AP namespaces, exclude quiesced nodes when calculating effective replication factor. |
| AER-6753 | (DEPLOYMENT) Added some new best practices and removed `asd-systemd-helper`. |
| AER-6754 | (BALANCE) Added namespace context configuration item `active-rack` to specify a rack to own all partition masters. |
| AER-6762 | (XDR) Added configuration to restrict or prevent skipping record versions when shipping. |
| AER-6763 | (STATS) Removed some meaningless stats, and improved some cluster related logging. |
| AER-6764 | (INFO) Standardized error responses to info commands. |

## Product lifecycle updates

Aerospike provides Maintenance and Support for 2 years (24 months) from its generally available (GA) release. See [Platform support](https://aerospike.com/docs/database/reference/platform-support) for details.

## Known issues

See [Database known issues reference](https://aerospike.com/docs/database/reference/issues?search=7.2.0.1).