Aerospike Server Community Edition 5.2.0.4

Description

• 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 Aerospike Expression filters. Aerospike Expression filters give access to the full data type APIs (List, Map, Bit, HyperLogLog, Geospatial) and expanded metadata based filtering, to increase the power of filters in selecting records.
• Support for the info command latency has been removed and replaced with a new info command latencies to track all latency histograms.
• Support for the XDR bin-policy value 'only-specified', which replaced the configuration item ship-only-specified-bins in the 5.0 and 5.1 releases, will be removed in 5.3 and above. 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 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
• 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.

New Features

Improvements

• Enterprise & Community
  • [AER-6303] - (KVS) With debug-allocations enabled, adjust output site addresses for easier association with source code.

Bug Fixes

• Enterprise & Community
  • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert.
  • [AER-6309] - (CDT) For ordered lists, get_all_by_value_list operation with result type value always returns an empty list.
  • [AER-6308] - (EXPRESSIONS) Miscellaneous issues in new expressions, which are not yet accessible from clients.
• Enterprise Only
  • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions.
  • [AER-6302] - (XDR) Namespace context configuration item xdr-tomb-raider-period cannot be set using time units.
  • [AER-6310] - (XDR) When connection to seed node fails, TLS name will be double freed and may cause a crash.

Known Issues

• Known Issues: Server

Updates