Aerospike Server Community Edition 5.0.0.4

Description

• Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
  • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled. 
  • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
• Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 can only connect to XDR destination clusters running versions 4.1 or newer.
• All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0.
  • Aerospike Server version 5.0 will not form a cluster with version 4.8 nodes or earlier.
  • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
• The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
  • Refer to: Configuration parameters that must be removed for Aerospike Server version 5.0
• ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
  • For expirations, nsup-period must be configured (new default is 0).
  • For evictions, the relevant high-water-disk-pct/high-water-memory-pct/mounts-high-water-pct must be configured (new defaults are 0).
  • For details refer to the Namespace Retention Configuration documentation.
• 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.
• Please reach out to your account representative if you are interested in Kerberos support.

New Features

Improvements

• Enterprise Only
  • [AER-6231] - (XDR) Avoid sending redundant XDR information during replication.

Bug Fixes

• Enterprise & Community
  • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated.

Known Issues

• Known Issues: Server

Updates