Aerospike Server Community Edition 5.0.0.21

Description

• 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 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.
  • Aerospike Server version 5.0 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
• 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 Only
  • [AER-6338] - (TLS) Added support with Centos 7 for certain stronger ciphers.

Bug Fixes

• Enterprise & Community
  • [AER-6339] - (KVS) On certain bitwise blob operations (and, or, xor), an out of bounds byte may be accessed and cause a crash.

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. Fixed in version 5.4.0.1.
    • 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).
  • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.0.0.37.
  • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.0.0.36.
  • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 5.0.0.30.
  • [AER-6402] - (SINDEX) When iterating through secondary indexes to adjust for changing list bin values, inactive indexes are incorrectly skipped, which may cause a crash. Fixed in version 5.0.0.30.
  • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 5.0.0.28.
• Enterprise Only
  • [AER-6451] - (KVS) Race condition between sprig element counters and changing sprig roots when rebuilding index during warm restart may cause a crash. Fixed in version 5.0.0.38.
  • [AER-6427] - (KVS) For data-in-index namespaces, durable deletes will cause an unnecessary assertion on a warm restart. Fixed in version 5.0.0.35.
  • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing. Fixed in version 5.0.0.34.
  • [AER-6413] - (SECURITY) Small memory leak during LDAP login process. Fixed in version 5.0.0.33.
  • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.0.0.33.
  • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 5.0.0.29.
  • [AER-6382] - (SECURITY) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 5.0.0.28.
  • [AER-6381] - (XDR) If a record expires between XDR reading and shipping, improper TTL will be shipped. Fixed in version 5.0.0.28.
  • [AER-6376] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 5.0.0.27.
  • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 5.0.0.27.
  • [AER-6366] - (XDR) Dynamically removing a connector seed node may cause a crash. Fixed in version 5.0.0.26.
  • [AER-6369] - (XDR) When shipping the first record on a connection, if all bins are filtered out, a crash may result. Fixed in version 5.0.0.26.
  • [AER-6363] - (KVS) A write or a UDF that deletes all of a record's bins may result in a tombstone with a non-zero void-time. Fixed in version 5.0.0.25.
  • [AER-6361] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item. Fixed in version 5.0.0.25.
  • [AER-6350] - (XDR) If a DC is dynamically removed and another added, handling of authentication configuration items may cause a double-free. Fixed in version 5.0.0.23.
  • [AER-6341] - (XDR) Source node may fail to discover the entire destination cluster when destination nodes restart. Fixed in version 5.0.0.22.

Updates