Aerospike Server Community Edition 5.6.0.20

Description

• The older Aerospike Connect Outbound versions do not work with Aerospike Server version 5.6 or newer. If you are using Aerospike Connect Outbound, you should upgrade respectively to:
  • Aerospike Connect for JMS - Outbound version 3.0.0 or newer
  • Aerospike Connect for Kafka - Outbound version 4.0.0 or newer
  • Aerospike Connect for Pulsar - Outbound version 2.0.0 or newer
  • XDR Proxy version 1.1.0 or newer
• In Aerospike Server 5.5 or earlier, a UDF returning a Boolean value as a bin would be converted to 1 or 0. In Aerospike 5.6 or newer the value returns as true or false.
• Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
• Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
• Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
• ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
• Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
  • Refer to the Special Upgrades - Upgrading from 5.0 or 5.1 to 5.3 or newer - if using the XDR bin projection functionality documentation.

• Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
• 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 or newer 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 or newer.
  • Aerospike Server version 5.0 or newer 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 or newer
• As of Aerospike Server 4.9 scans are correct. The scan priority, fail_on_cluster_change, and scan percent options, that were deprecated in Aerospike Server 4.9 are removed in Aerospike Server 5.6.
• 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.
• The Predicate Expression API will be removed in the Aerospike Server version 6.0 release. Use Aerospike Filter Expressions (added in version 5.2).
• We have removed support for Ubuntu 16.04.
  • For more information please refer to: Ubuntu 16.04 LTS (Xenial Xerus).
• Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.

New Features

Improvements

Bug Fixes

• Enterprise Only
  • [AER-6525] - (XDR) For single-bin, data-in-memory namespaces, shipping records will corrupt the index and may cause a crash.

Known Issues

• Known Issues: Server

Updates