Aerospike Database (December 10, 2020)

Aerospike Database version was released on December 10, 2020.

This major release contains a New Feature, and Improvements.

  • The Cross-Datacenter Replication (XDR) feature now includes the ability to filter using Expressions.
  • 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 Database 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 Database 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 Database version or newer prior to upgrading to Aerospike Database version 5.0 or newer.
    • Aerospike Database version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
    • When upgrading the Aerospike Database refer to the Special Upgrades documentation.
  • The Aerospike Database will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
  • ATTENTION: As of Aerospike Database version 4.9, expirations and evictions are disabled by default.

Known Issues

  • Enterprise & Community
    • [AER-6340] - (KVS) HLL string or blob elements sized 31 to 254 bytes may be treated differently depending on msgpack standard.
      • Different client versions use 2 different msgpack standards. If HLLs have string or blob elements in the size range 31-254 inclusive and are accessed via clients using differing msgpack standards, a given element can be added to an HLL as 2 different elements. Also, even if individual HLLs were built consistently, operations combining them will give incorrect results if they were built using different standards. Once any of this has happened, it is not possible to fix the affected HLL(s).
© 2021 Copyright Aerospike, Inc. | All rights reserved. Creators of the Aerospike Database.