Aerospike Server Community Edition 4.6.0.14

Description

• A digitally signed feature key file is now required. (Enterprise Only)
  • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
• 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.
• For Aerospike Server versions prior to 4.7 XDR does not support LDAP logins.
• 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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash.
  • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive.
  • [AER-6194] - (GEO) For namespaces with data-in-memory true, GeoJSON particles allocate up to 2KB more than the reported particle size.
• Enterprise Only
  • [AER-6195] - (MIGRATION) Theoretical race condition may cause delta migration to complete without sending all records.

Known Issues

• Known Issues: Server

Updates