Aerospike Server Community Edition 4.7.0.10

Description

• XDR, using ACL, in server versions between 4.1.0.1 and 4.3.0.6 cannot ship to this version. The simplest workaround is to avoid using those versions.
• Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
• A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
• When upgrading the Aerospike Server refer to the Special Upgrades documentation.
• Please reach out to your account representative if you are interested in Kerberos support.

New Features

Improvements

Bug Fixes

• Enterprise & Community
  • [AER-6179] - (KVS) When upgrading from version earlier than 4.5.1, pre-existing eviction depth is not used during startup.
• Enterprise Only
  • [AER-6170] - (XDR) Source node may crash when adding or removing namespaces in a destination cluster.
  • [AER-6172] - (XDR) Increasing datacenter context configuration item dc-connections dynamically may cause crash.

Known Issues

• Known Issues: Server

Updates