Aerospike Server Community Edition 5.1.0.10

Description

• ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
• For the info command latency support has been deprecated and will be removed in the next major release.
  • Please use the new replacement info command latencies to track all latency histograms.
• 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-6284] - (KVS) Disallow dynamically setting non-zero value of namespace context configuration item default-ttl unless nsup-period is non-zero or allow-ttl-without-nsup is true.
• Enterprise Only
  • [AER-6288] - (XDR) Keep the last ship time of non-owned partitions relatively current.

Bug Fixes

• Enterprise & Community
  • [AER-6289] - (KVS) Concurrently reading and writing a new bin or set name may access a pointer which crosses a cache line boundary, causing a crash.
  • [AER-6290] - (KVS) For namespaces with data not in memory, failure when reading a record from 'flat' format may cause a crash.
• Enterprise Only
  • [AER-6287] - (KVS) When writing over a tombstone with Time-To-Live (TTL) value -2 (i.e. do not update TTL), the write fails to apply the namespace default-ttl.
• Community Only
  • [AER-6286] - (TELEMETRY) Telemetry fails to start on Amazon Elastic Compute Cloud (Amazon EC2) on Amazon Linux 2 with Python 3 installed.

Known Issues

• Known Issues: Server

Updates