Aerospike Database (January 13, 2021)

Aerospike Database version was released on January 13, 2021.

This major release contains a New Feature, Improvements, and a Bug Fix.

  • 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’.
  • Aerospike Server version 5.1 or later requires the operating system distribution’s libcurl shared object library.
  • Before upgrading to or later, customers already running 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 or newer node going down while 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 or newer 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).
  • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
  • CentOS Linux 8 End of Life is scheduled for December 2021.
© 2021 Copyright Aerospike, Inc. | All rights reserved. Creators of the Aerospike Database.