Skip to content

Releases: aerospike/aerospike-server

7.2.0.3

01 Nov 22:14
@pvinh-spike pvinh-spike
7.2.0.3
e777b29
Compare
Choose a tag to compare
7.2.0.3 Latest
Latest

Aerospike Server Community Edition 7.2.0.3

Aerospike Database software version 7.2.0.3 is now available.

This release is a hotfix for Aerospike server 7.2.

Bug fixes

The following issues are resolved with this hotfix.

AER-6759

(KVS) All nodes can now accurately choose the correct proxy destination in an unstable cluster.

Editions affected: Enterprise, Federal & Community

AER-6772

(BALANCE) Changed strong-consistency namespace context configuration item auto-revive to not revive partitions at startup if any device was erased.

Editions affected: Enterprise, Federal & Community

AER-6773

(MIGRATION) Added namespace context configuration item migrate-skip-unreadable to ignore unreadable records during migration.

Editions affected: Enterprise, Federal & Community

AER-6774

(NETWORK) DNS names starting with a digit are mistaken as IP addresses.

Editions affected: Enterprise, Federal & Community

AER-6775

(STORAGE) For strong-consistency namespaces, don't flag a node as untrusted when devices are added.

Editions affected: Enterprise & Federal Only

Known issues

Known issues for 7.2.0.3

Assets 50

7.1.0.9

01 Nov 22:13
@pvinh-spike pvinh-spike
7.1.0.9
fb84692
Compare
Choose a tag to compare
7.1.0.9

Aerospike Server Community Edition 7.1.0.9

Aerospike Database software version 7.1.0.9 is now available.

This release is a hotfix for Aerospike server 7.1.

Bug fixes

The following issues are resolved with this hotfix.

AER-6759

(KVS) All nodes can now accurately choose the correct proxy destination in an unstable cluster.

Editions affected: Enterprise, Federal & Community

AER-6772

(BALANCE) Changed strong-consistency namespace context configuration item auto-revive to not revive partitions at startup if any device was erased.

Editions affected: Enterprise, Federal & Community

AER-6773

(MIGRATION) Added namespace context configuration item migrate-skip-unreadable to ignore unreadable records during migration.

Editions affected: Enterprise, Federal & Community

AER-6774

(NETWORK) DNS names starting with a digit are mistaken as IP addresses.

Editions affected: Enterprise, Federal & Community

AER-6775

(STORAGE) For strong-consistency namespaces, don't flag a node as untrusted when devices are added.

Editions affected: Enterprise & Federal Only

Known issues

Known issues for 7.1.0.9

Assets 44
Loading

7.0.0.18

01 Nov 22:08
@pvinh-spike pvinh-spike
7.0.0.18
c13107b
Compare
Choose a tag to compare
7.0.0.18

Aerospike Server Community Edition 7.0.0.18

Aerospike Database software version 7.0.0.18 is now available.

This release is a hotfix for Aerospike server 7.0.

Bug fixes

The following issues are resolved with this hotfix.

AER-6759

(KVS) All nodes can now accurately choose the correct proxy destination in an unstable cluster.

Editions affected: Enterprise, Federal & Community

AER-6773

(MIGRATION) Added namespace context configuration item migrate-skip-unreadable to ignore unreadable records during migration.

Editions affected: Enterprise, Federal & Community

AER-6774

(NETWORK) DNS names starting with a digit are mistaken as IP addresses.

Editions affected: Enterprise, Federal & Community

Known issues

Known issues for 7.0.0.18

Assets 44
Loading

6.4.0.26

01 Nov 22:06
@pvinh-spike pvinh-spike
6.4.0.26
8dd5656
Compare
Choose a tag to compare
6.4.0.26

Aerospike Server Community Edition 6.4.0.26

Aerospike Database software version 6.4.0.26 is now available.

This release is a hotfix for Aerospike server 6.4.

Bug fixes

The following issues are resolved with this hotfix.

AER-6774

(NETWORK) DNS names starting with a digit are mistaken as IP addresses.

Editions affected: Enterprise, Federal & Community

Known issues

Known issues for 6.4.0.26

Assets 53
Loading

6.3.0.31

01 Nov 22:05
@pvinh-spike pvinh-spike
6.3.0.31
c6f972c
Compare
Choose a tag to compare
6.3.0.31

Aerospike Server Community Edition 6.3.0.31

Aerospike Database software version 6.3.0.31 is now available.

This release is a hotfix for Aerospike server 6.3.

Bug fixes

The following issues are resolved with this hotfix.

AER-6774

(NETWORK) DNS names starting with a digit are mistaken as IP addresses.

Editions affected: Enterprise, Federal & Community

Known issues

Known issues for 6.3.0.31

Assets 41
Loading

6.2.0.33

01 Nov 22:02
@pvinh-spike pvinh-spike
6.2.0.33
e790327
Compare
Choose a tag to compare
6.2.0.33

Aerospike Server Community Edition 6.2.0.33

Aerospike Database software version 6.2.0.33 is now available.

This release is a hotfix for Aerospike server 6.2.

Bug fixes

The following issues are resolved with this hotfix.

AER-6774

(NETWORK) DNS names starting with a digit are mistaken as IP addresses.

Editions affected: Enterprise, Federal & Community

Known issues

Known issues for 6.2.0.33

Assets 38
Loading

6.1.0.43

01 Nov 21:59
@pvinh-spike pvinh-spike
6.1.0.43
ecf48d3
Compare
Choose a tag to compare
6.1.0.43

Aerospike Server Community Edition 6.1.0.43

Aerospike Database software version 6.1.0.43 is now available.

This release is a hotfix for Aerospike server 6.1.

Bug fixes

The following issues are resolved with this hotfix.

AER-6774

(NETWORK) DNS names starting with a digit are mistaken as IP addresses.

Editions affected: Enterprise, Federal & Community

Known issues

Known issues for 6.1.0.43

Assets 23
Loading

7.2.0.1

08 Oct 00:05
@pvinh-spike pvinh-spike
7.2.0.1
12df0c5
Compare
Choose a tag to compare
7.2.0.1

Aerospike Server Community Edition 7.2.0.1

Aerospike Database Release Notes 7.2

October 7, 2024

Aerospike Database software version 7.2 is now available.

New in this version

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

New features

Updates

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,the effective replication factor (RF) is automatically decremented so that the quiesced node genuinely gives up partition ownership regardless of the configured RF.
  • 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.

Configuration item changes

Item Action Notes
active-rack added The rack that owns all of the masters in AP and SC namespaces.
ship-versions-policy added Stops XDR from skipping record versions.
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 removed
early_tsvc_udf_sub_error removed
early_tsvc_ops_sub_error removed
effective_active_rack added Roster’s current active-rack for SC namespaces.
fail_xdr_key_busy added Counts how many XDR key busy errors have occurred.
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 modified id parameter is now deprecated and namespace is accepted in its place.
set-config modified id parameter is now deprecated and namespace is accepted in its place.
sindex-create modified ns parameter is now deprecated and namespace is accepted in its place.
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 modified ns parameter is now deprecated and namespace is accepted in its place.
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 modified ns parameter is now deprecated and namespace is accepted in its place.
get-config:context=xdr;dc=DC-NAME; modified ns parameter is now deprecated and namespace is accepted in its place.
get-stats:context=xdr;dc=DC-NAME; 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 ... enhanced Now reads special-errors: key-busy (123) (40) where the second number in the parentheses is the XDR key busy count.
early-fail: 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
XDR key busy added Occurs when a write must wait on a previous version to ship and either the write times out or there are already too many writes waiting.

Tools changes

Changes in Tools 11.1.0

See Tools 11.1.0 Release Notes.

Client/server feature compatibility

For a complete list of client features and the Aerospike Database versions that support them, see the Client Matrix.

Minimum compatible client versions

For full feature access in Database 7.2:

  • Java client 8.1
  • Python client 15.0
  • C# client 7.2
  • C client 6.6
  • Go client 7.2
  • 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.

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 for details.

Known issues

See [Server Known Issues Reference](https://aerospike.com/do...

Read more
Assets 50
Loading

6.4.0.25

03 Oct 03:51
@pvinh-spike pvinh-spike
6.4.0.25
1c3b94d
Compare
Choose a tag to compare
6.4.0.25

Aerospike Server Community Edition 6.4.0.25

Aerospike Database software version 6.4.0.25 is now available.

This release is a hotfix for Aerospike server 6.4.

Bug fixes

The following issues are resolved with this hotfix.

AER-6771

(STORAGE) For storage-engine pmem namespaces with encryption configured, tomb raids may cause unnecessary warnings when encountering partially flushed records.

Editions affected: Enterprise & Federal Only

Known issues

Known issues for 6.4.0.25

Assets 53
Loading

6.3.0.30

03 Oct 03:50
@pvinh-spike pvinh-spike
6.3.0.30
986296c
Compare
Choose a tag to compare
6.3.0.30

Aerospike Server Community Edition 6.3.0.30

Aerospike Database software version 6.3.0.30 is now available.

This release is a hotfix for Aerospike server 6.3.

Bug fixes

The following issues are resolved with this hotfix.

AER-6771

(STORAGE) For storage-engine pmem namespaces with encryption configured, tomb raids may cause unnecessary warnings when encountering partially flushed records.

Editions affected: Enterprise & Federal Only

Known issues

Known issues for 6.3.0.30

Assets 41
Loading