Aerospike Server CE Release Notes

  • 5.7.0.7
    Release Date: September 27, 2021
    • For upgrading, or the unlikely event of downgrading, please refer to Special Upgrades.
    • The Predicate Expression API is obsolete. The Aerospike Server and Client have scheduled removal with our next major Aerospike Server release, around November 2021. Please Use Aerospike Filter Expressions (added in version 5.2).
    • The jobs info command is now officially deprecated and will continue to be supported through a deprecation period, after which it will be removed. jobs are now redundant with the new secondary index building methods and the following new info commands:
    • The configuration parameter batch-without-digests, now defaults to true, is deprecated and will be removed in six months. Customers using clients older than a year (around the time of Server 4.9 which introduced batch-without-digests) will now have to explicitly set the batch-without-digests configuration item to false.
    • A number of Best Practices will be checked at startup. The Best Practices can be enforced by enabling the new enforce-best-practices configuration item.
    • The security context configuration items enable-security and enable-ldap have been removed. The Server will not start if either enable-security or enable-ldap is present in the configuration file.
    • Security will now be enabled simply by the presence of the security { } section in the configuration file. Similarly, LDAP will now be enabled simply by the presence of the ldap { } section within the security { } section of the configuration file.
    • To use XDR with ACL auth-mode must be explicitly configured.
    • We build on Red Hat Enterprise Linux (RHEL) 8 instead of CentOS 8 when creating rpm packages.

    Improvements

    • Enterprise & Community
      • [AER-6429] - (BATCH) Changed default value of service context configuration item batch-without-digests to true - the item is now deprecated.
      • [AER-6430] - (CLUSTERING) Reject the recluster info command if already reclustering.
      • [AER-6461] - (DEPLOYMENT) Sanity-check various system settings and server configuration items at startup.
      • [AER-6432] - (FABRIC) Handle fabric node list with a more granular hash and an improved node id hash function.
      • [AER-6459] - (GEO) Changed namespace geo2dsphere-within context configuration item max-level default from 30 to 20.
      • [AER-6455] - (INFO) Replaced scan-list and query-list with scan-show and query-show, renamed query-kill to query-abort.
      • [AER-6433] - (KVS) Switch write transactions from write-commit-level 'master' to 'all' if fabric send queues are overwhelmed.
      • [AER-6441] - (KVS) Reject replica writes if they are overwhelming the write queue.
      • [AER-6447] - (KVS) By default, exclude group and 'other' permissions when creating files.
      • [AER-6452] - (KVS) Removed non-essential sprig element counters, saving three bytes of overhead per sprig.
      • [AER-6470] - (KVS) Replaced fabric idle connection queue and storage device open file descriptor queues with lockless pools.
      • [AER-6471] - (KVS) Upgraded JEMalloc submodule to 'stable-4' version, plus modifications for Valgrind.
      • [AER-6434] - (LOGGING) Do not truncate the log file when (re)opening it during log rotation.
      • [AER-6460] - (LOGGING) Improved logging around duplicate node-ids.
      • [AER-6428] - (MIGRATION) Pause immigrations if they are overwhelming the write queue.
      • [AER-6450] - (SCAN) Queue dynamic set-index population jobs, to serialize them and reduce CPU usage.
      • [AER-6464] - (SINDEX) Secondary indexes store primary index references instead of digests - reduces memory footprint and improves garbage collection.
      • [AER-6476] - (STATS) Added system_thp_mem_kbytes statistic.
      • [AER-6436] - (STORAGE) Added namespace context configuration item max-record-size.
      • [AER-6468] - (STORAGE) Allow value of 0 for storage context configuration item defrag-startup-minimum, and made that the default.
    • Enterprise Only
      • [AER-6454] - (ACL) Moved configuration item session-ttl from 'ldap' to 'security' context, and ldap-login-threads (renamed as login-threads) from 'security' to 'ldap' context.
      • [AER-6456] - (ACL) Removed security context configuration items enable-security and enable-ldap.
      • [AER-6462] - (ACL) Added support for PKI authentication.
      • [AER-6453] - (AUDIT) Added separate 'audit' logging context so that auditing via a regular log sink will not include all 'security' context logs.
      • [AER-6431] - (STATS) Added unreplicated_records statistic for strong-consistency namespaces.
      • [AER-6445] - (STORAGE) Added storage context configuration item encryption-old-key-file to support rotation of encryption keys.
      • [AER-6449] - (STORAGE) Updated storage compression submodules.
      • [AER-6440] - (XDR) Disallow DC context configuration items auth-user and auth-password-file for connector DCs.
      • [AER-6443] - (XDR) An 'xdr' context in the configuration file is no longer required in order to configure DCs dynamically.

    Updates

  • 5.6.0.13
    Release Date: September 20, 2021
    • The older Aerospike Connect Outbound versions do not work with Aerospike Server version 5.6 or newer. If you are using Aerospike Connect Outbound, you should upgrade respectively to:
      • Aerospike Connect for JMS - Outbound version 3.0.0 or newer
      • Aerospike Connect for Kafka - Outbound version 4.0.0 or newer
      • Aerospike Connect for Pulsar - Outbound version 2.0.0 or newer
      • XDR Proxy version 1.1.0 or newer
    • In Aerospike Server 5.5 or earlier, a UDF returning a Boolean value as a bin would be converted to 1 or 0. In Aerospike 5.6 or newer the value returns as true or false.
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • 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 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 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).
    • As of Aerospike Server 4.9 scans are correct. The scan priority, fail_on_cluster_change, and scan percent options, that were deprecated in Aerospike Server 4.9 are removed in Aerospike Server 5.6.
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Predicate Expression API is scheduled for removal around November 2021.
    • We have removed support for Ubuntu 16.04.

    Bug Fixes

    • Enterprise & Community
      • [AER-6479] - (EXPRESSIONS) For data-in-memory namespaces, an expression let which returns the value of one of its variables may leak memory.
      • [AER-6481] - (KVS) When a service thread exits, its epoll queue's event file descriptor leaks.
      • [AER-6480] - (SCAN) A paginated scan on a set which is indexed may not return the correct records.
      • [AER-6482] - (STORAGE) When a device runs completely out of space, defrag becomes ineffective.
    • Enterprise Only

  • 5.6.0.12
    Release Date: September 15, 2021
    • The older Aerospike Connect Outbound versions do not work with Aerospike Server version 5.6 or newer. If you are using Aerospike Connect Outbound, you should upgrade respectively to:
      • Aerospike Connect for JMS - Outbound version 3.0.0 or newer
      • Aerospike Connect for Kafka - Outbound version 4.0.0 or newer
      • Aerospike Connect for Pulsar - Outbound version 2.0.0 or newer
      • XDR Proxy version 1.1.0 or newer
    • In Aerospike Server 5.5 or earlier, a UDF returning a Boolean value as a bin would be converted to 1 or 0. In Aerospike 5.6 or newer the value returns as true or false.
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • 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 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 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).
    • As of Aerospike Server 4.9 scans are correct. The scan priority, fail_on_cluster_change, and scan percent options, that were deprecated in Aerospike Server 4.9 are removed in Aerospike Server 5.6.
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Predicate Expression API is scheduled for removal around November 2021.
    • We have removed support for Ubuntu 16.04.

    Bug Fixes

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted.

  • 5.6.0.11
    Release Date: September 2, 2021
    • The older Aerospike Connect Outbound versions do not work with Aerospike Server version 5.6 or newer. If you are using Aerospike Connect Outbound, you should upgrade respectively to:
      • Aerospike Connect for JMS - Outbound version 3.0.0 or newer
      • Aerospike Connect for Kafka - Outbound version 4.0.0 or newer
      • Aerospike Connect for Pulsar - Outbound version 2.0.0 or newer
      • XDR Proxy version 1.1.0 or newer
    • In Aerospike Server 5.5 or earlier, a UDF returning a Boolean value as a bin would be converted to 1 or 0. In Aerospike 5.6 or newer the value returns as true or false.
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • 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 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 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).
    • As of Aerospike Server 4.9 scans are correct. The scan priority, fail_on_cluster_change, and scan percent options, that were deprecated in Aerospike Server 4.9 are removed in Aerospike Server 5.6.
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Predicate Expression API is scheduled for removal around November 2021.
    • We have removed support for Ubuntu 16.04.

    Improvements

    • Enterprise & Community
      • [AER-6475] - (GEO) For data-in-memory namespaces, when trimming GeoJSON particles, reallocate into the appropriate namespace arena.

    Bug Fixes

    • Enterprise & Community
      • [AER-6473] - (EXPRESSIONS) For data-in-memory namespaces, an expression let which returns the value of one of its variables will cause a double-free.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.6.0.12.

  • 5.6.0.10
    Release Date: August 4, 2021
    • The older Aerospike Connect Outbound versions do not work with Aerospike Server version 5.6 or newer. If you are using Aerospike Connect Outbound, you should upgrade respectively to:
      • Aerospike Connect for JMS - Outbound version 3.0.0 or newer
      • Aerospike Connect for Kafka - Outbound version 4.0.0 or newer
      • Aerospike Connect for Pulsar - Outbound version 2.0.0 or newer
      • XDR Proxy version 1.1.0 or newer
    • In Aerospike Server 5.5 or earlier, a UDF returning a Boolean value as a bin would be converted to 1 or 0. In Aerospike 5.6 or newer the value returns as true or false.
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • 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 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 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).
    • As of Aerospike Server 4.9 scans are correct. The scan priority, fail_on_cluster_change, and scan percent options, that were deprecated in Aerospike Server 4.9 are removed in Aerospike Server 5.6.
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Predicate Expression API is scheduled for removal around November 2021.
    • We have removed support for Ubuntu 16.04.

    Bug Fixes

    • Enterprise Only
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.6.0.12.
      • [AER-6473] - (EXPRESSIONS) For data-in-memory namespaces, an expression let which returns the value of one of its variables will cause a double-free. Fixed in version 5.6.0.11.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.6.0.11.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.6.0.11.

  • 5.6.0.9
    Release Date: July 22, 2021
    • The older Aerospike Connect Outbound versions do not work with Aerospike Server version 5.6 or newer. If you are using Aerospike Connect Outbound, you should upgrade respectively to:
      • Aerospike Connect for JMS - Outbound version 3.0.0 or newer
      • Aerospike Connect for Kafka - Outbound version 4.0.0 or newer
      • Aerospike Connect for Pulsar - Outbound version 2.0.0 or newer
      • XDR Proxy version 1.1.0 or newer
    • In Aerospike Server 5.5 or earlier, a UDF returning a Boolean value as a bin would be converted to 1 or 0. In Aerospike 5.6 or newer the value returns as true or false.
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • 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 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 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).
    • As of Aerospike Server 4.9 scans are correct. The scan priority, fail_on_cluster_change, and scan percent options, that were deprecated in Aerospike Server 4.9 are removed in Aerospike Server 5.6.
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Predicate Expression API is scheduled for removal around November 2021.
    • We have removed support for Ubuntu 16.04.

    Bug Fixes

    • Enterprise & Community
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.6.0.12.
      • [AER-6473] - (EXPRESSIONS) For data-in-memory namespaces, an expression let which returns the value of one of its variables will cause a double-free. Fixed in version 5.6.0.11.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.6.0.11.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.6.0.11.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.6.0.10.

  • 5.6.0.8
    Release Date: July 19, 2021
    • The older Aerospike Connect Outbound versions do not work with Aerospike Server version 5.6 or newer. If you are using Aerospike Connect Outbound, you should upgrade respectively to:
      • Aerospike Connect for JMS - Outbound version 3.0.0 or newer
      • Aerospike Connect for Kafka - Outbound version 4.0.0 or newer
      • Aerospike Connect for Pulsar - Outbound version 2.0.0 or newer
      • XDR Proxy version 1.1.0 or newer
    • In Aerospike Server 5.5 or earlier, a UDF returning a Boolean value as a bin would be converted to 1 or 0. In Aerospike 5.6 or newer the value returns as true or false.
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • 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 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 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).
    • As of Aerospike Server 4.9 scans are correct. The scan priority, fail_on_cluster_change, and scan percent options, that were deprecated in Aerospike Server 4.9 are removed in Aerospike Server 5.6.
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Predicate Expression API is scheduled for removal around November 2021.
    • We have removed support for Ubuntu 16.04.

    Bug Fixes

    • 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.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.6.0.12.
      • [AER-6473] - (EXPRESSIONS) For data-in-memory namespaces, an expression let which returns the value of one of its variables will cause a double-free. Fixed in version 5.6.0.11.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.6.0.11.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.6.0.9.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.6.0.11.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.6.0.10.

  • 5.6.0.7
    Release Date: June 22, 2021
    • The older Aerospike Connect Outbound versions do not work with Aerospike Server version 5.6 or newer. If you are using Aerospike Connect Outbound, you should upgrade respectively to:
      • Aerospike Connect for JMS - Outbound version 3.0.0 or newer
      • Aerospike Connect for Kafka - Outbound version 4.0.0 or newer
      • Aerospike Connect for Pulsar - Outbound version 2.0.0 or newer
      • XDR Proxy version 1.1.0 or newer
    • In Aerospike Server 5.5 or earlier, a UDF returning a Boolean value as a bin would be converted to 1 or 0. In Aerospike 5.6 or newer the value returns as true or false.
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • 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 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 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).
    • As of Aerospike Server 4.9 scans are correct. The scan priority, fail_on_cluster_change, and scan percent options, that were deprecated in Aerospike Server 4.9 are removed in Aerospike Server 5.6.
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Predicate Expression API is scheduled for removal around November 2021.
    • We have removed support for Ubuntu 16.04.

    Bug Fixes

    • Enterprise & Community
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps.
    • Enterprise Only
      • [AER-6446] - (SCAN) Race condition when populating set indexes during warm restarts may cause a crash.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.6.0.12.
      • [AER-6473] - (EXPRESSIONS) For data-in-memory namespaces, an expression let which returns the value of one of its variables will cause a double-free. Fixed in version 5.6.0.11.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.6.0.11.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.6.0.9.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.6.0.11.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.6.0.10.
      • [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.6.0.8.

  • 5.6.0.5
    Release Date: May 27, 2021
    • The older Aerospike Connect Outbound versions do not work with Aerospike Server version 5.6 or newer. If you are using Aerospike Connect Outbound, you should upgrade respectively to:
      • Aerospike Connect for JMS - Outbound version 3.0.0 or newer
      • Aerospike Connect for Kafka - Outbound version 4.0.0 or newer
      • Aerospike Connect for Pulsar - Outbound version 2.0.0 or newer
      • XDR Proxy version 1.1.0 or newer
    • In Aerospike Server 5.5 or earlier, a UDF returning a Boolean value as a bin would be converted to 1 or 0. In Aerospike 5.6 or newer the value returns as true or false.
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • 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 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 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).
    • As of Aerospike Server 4.9 scans are correct. The scan priority, fail_on_cluster_change, and scan percent options, that were deprecated in Aerospike Server 4.9 are removed in Aerospike Server 5.6.
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Predicate Expression API is scheduled for removal around November 2021.
    • We have removed support for Ubuntu 16.04.

    Bug Fixes

    • Enterprise & Community
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes.
      • [AER-6439] - (SCAN) Disabling a set index while it is being populated may result in a deadlock.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.6.0.12.
      • [AER-6473] - (EXPRESSIONS) For data-in-memory namespaces, an expression let which returns the value of one of its variables will cause a double-free. Fixed in version 5.6.0.11.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.6.0.11.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.6.0.9.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.6.0.7.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.6.0.11.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.6.0.10.
      • [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.6.0.8.
      • [AER-6446] - (SCAN) Race condition when populating set indexes during warm restarts may cause a crash. Fixed in version 5.6.0.7.

  • 5.6.0.4
    Release Date: May 24, 2021
    • The older Aerospike Connect Outbound versions do not work with Aerospike Server version 5.6 or newer. If you are using Aerospike Connect Outbound, you should upgrade respectively to:
      • Aerospike Connect for JMS - Outbound version 3.0.0 or newer
      • Aerospike Connect for Kafka - Outbound version 4.0.0 or newer
      • Aerospike Connect for Pulsar - Outbound version 2.0.0 or newer
      • XDR Proxy version 1.1.0 or newer
    • In Aerospike Server 5.5 or earlier, a UDF returning a Boolean value as a bin would be converted to 1 or 0. In Aerospike 5.6 or newer the value returns as true or false.
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • 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 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 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).
    • As of Aerospike Server 4.9 scans are correct. The scan priority, fail_on_cluster_change, and scan percent options, that were deprecated in Aerospike Server 4.9 are removed in Aerospike Server 5.6.
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Predicate Expression API is scheduled for removal around November 2021.
    • We have removed support for Ubuntu 16.04.

    Bug Fixes

    • Enterprise Only
      • [AER-6427] - (KVS) For data-in-index namespaces, durable deletes will cause an unnecessary assertion on a warm restart.
      • [AER-6437] - (KVS) Improper initialization of set index trees during warm restart may eventually cause a crash.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.6.0.12.
      • [AER-6473] - (EXPRESSIONS) For data-in-memory namespaces, an expression let which returns the value of one of its variables will cause a double-free. Fixed in version 5.6.0.11.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.6.0.11.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.6.0.9.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.6.0.7.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.6.0.5.
      • [AER-6439] - (SCAN) Disabling a set index while it is being populated may result in a deadlock. Fixed in version 5.6.0.5.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.6.0.11.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.6.0.10.
      • [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.6.0.8.
      • [AER-6446] - (SCAN) Race condition when populating set indexes during warm restarts may cause a crash. Fixed in version 5.6.0.7.

  • 5.6.0.3
    Release Date: May 10, 2021
    • Aerospike Server release 5.6.0.3 contained a bug that may cause a server crash (AER-6437).
      • If you are running Aerospike Server version 5.6, we recommend that you upgrade to the latest release (currently 5.6.0.4).
    • The older Aerospike Connect Outbound versions do not work with Aerospike Server version 5.6 or newer. If you are using Aerospike Connect Outbound, you should upgrade respectively to:
      • Aerospike Connect for JMS - Outbound version 3.0.0 or newer
      • Aerospike Connect for Kafka - Outbound version 4.0.0 or newer
      • Aerospike Connect for Pulsar - Outbound version 2.0.0 or newer
      • XDR Proxy version 1.1.0 or newer
    • In Aerospike Server 5.5 or earlier, a UDF returning a Boolean value as a bin would be converted to 1 or 0. In Aerospike 5.6 or newer the value returns as true or false.
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • 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 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 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).
    • As of Aerospike Server 4.9 scans are correct. The scan priority, fail_on_cluster_change, and scan percent options, that were deprecated in Aerospike Server 4.9 are removed in Aerospike Server 5.6.
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Predicate Expression API is scheduled for removal around November 2021.
    • We have removed support for Ubuntu 16.04.

    New Features

    • Enterprise & Community
      • [AER-6400] - (EXPRESSIONS) Added support for Operation Expressions.
      • [AER-6399] - (EXPRESSIONS) Added support for arithmetic, branching, and variables to expressions.
      • [AER-6392] - (KVS) Added support for Boolean particle type.
      • [AER-6421] - (SCAN) Added set context configuration item enable-index to maintain a set-specific index for scans of the set.
    • Enterprise Only
      • [AER-6416] - (ACL) Added support for rate quotas, including per-user rate statistics.

    Improvements

    • Enterprise & Community
      • [AER-6422] - (EXPRESSIONS) Added a ticker warning for use of the deprecated predexp API.
      • [AER-6398] - (FABRIC) Handle fabric node list with more granular locking.
      • [AER-6407] - (KVS) Added service context configuration item os-group-perms to add group permissions when creating files.
      • [AER-6415] - (KVS) Removed 'set-' prefix from configuration items in the namespace 'set' context.
      • [AER-6425] - (KVS) Changed transient detached threads to run from a thread pool.
      • [AER-6409] - (NETWORK) Added network service context configuration item disable-localhost to prevent listening on localhost.
      • [AER-6408] - (SCAN) Removed support for non partition-based basic scans, and deprecated scan options.
      • [AER-6424] - (STATS) Added more complete file descriptor stats for client, heartbeat, and fabric.
    • Enterprise Only
      • [AER-6393] - (AUDIT) Added 'log' and 'syslog' context configuration items 'report-data-op-role' and 'report-data-op-user' to audit by role or user.
      • [AER-6394] - (AUDIT) Made all 'log' and 'syslog' context 'report-...' configuration items dynamic and properly echoed via get-config.
      • [AER-6417] - (ACL) Included number of per-user open connections in 'show user(s)' output.
      • [AER-6410] - (STATS) Added index_flash_alloc_bytes and index_flash_alloc_pct statistics.
      • [AER-6405] - (XDR) Added new stats for tracking bin-convergence conflicts.
      • [AER-6406] - (XDR) Always send the record last-update-time to connector destinations.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.6.0.12.
      • [AER-6473] - (EXPRESSIONS) For data-in-memory namespaces, an expression let which returns the value of one of its variables will cause a double-free. Fixed in version 5.6.0.11.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.6.0.11.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.6.0.9.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.6.0.7.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.6.0.5.
      • [AER-6439] - (SCAN) Disabling a set index while it is being populated may result in a deadlock. Fixed in version 5.6.0.5.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.6.0.11.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.6.0.10.
      • [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.6.0.8.
      • [AER-6446] - (SCAN) Race condition when populating set indexes during warm restarts may cause a crash. Fixed in version 5.6.0.7.
      • [AER-6437] - (KVS) Improper initialization of set index trees during warm restart may eventually cause a crash. Fixed in version 5.6.0.4.
      • [AER-6427] - (KVS) For data-in-index namespaces, durable deletes will cause an unnecessary assertion on a warm restart. Fixed in version 5.6.0.4.

    Updates

  • 5.5.0.19
    Release Date: September 20, 2021
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • 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 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 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).
    • 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.

    Bug Fixes

    • Enterprise & Community
      • [AER-6481] - (KVS) When a service thread exits, its epoll queue's event file descriptor leaks.
      • [AER-6482] - (STORAGE) When a device runs completely out of space, defrag becomes ineffective.
    • Enterprise Only

  • 5.5.0.18
    Release Date: September 15, 2021
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • 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 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 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).
    • 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.

    Bug Fixes

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted.

  • 5.5.0.17
    Release Date: September 2, 2021
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • 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 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 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).
    • 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.

    Improvements

    • Enterprise & Community
      • [AER-6475] - (GEO) For data-in-memory namespaces, when trimming GeoJSON particles, reallocate into the appropriate namespace arena.

    Bug Fixes

    • Enterprise & Community
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.5.0.18.

  • 5.5.0.16
    Release Date: August 4, 2021
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • 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 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 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).
    • 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.

    Bug Fixes

    • Enterprise Only
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.5.0.18.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.5.0.17.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.5.0.17.

  • 5.5.0.15
    Release Date: July 22, 2021
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • 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 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 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).
    • 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.

    Bug Fixes

    • Enterprise & Community
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.5.0.18.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.5.0.17.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.5.0.17.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.5.0.16.

  • 5.5.0.14
    Release Date: July 19, 2021
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • 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 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 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).
    • 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.

    Bug Fixes

    • 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.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.5.0.18.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.5.0.17.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.5.0.15.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.5.0.17.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.5.0.16.

  • 5.5.0.13
    Release Date: June 24, 2021
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • 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 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 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).
    • 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.

    Bug Fixes

    • Enterprise & Community
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.5.0.18.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.5.0.17.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.5.0.15.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.5.0.17.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.5.0.16.
      • [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.5.0.14.

  • 5.5.0.12
    Release Date: May 28, 2021
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • 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 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 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).
    • 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.

    Bug Fixes

    • Enterprise & Community
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.5.0.18.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.5.0.17.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.5.0.15.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.5.0.13.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.5.0.17.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.5.0.16.
      • [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.5.0.14.

  • 5.5.0.11
    Release Date: May 25, 2021
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • 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 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 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).
    • 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.

    Bug Fixes

    • Enterprise Only
      • [AER-6427] - (KVS) For data-in-index namespaces, durable deletes will cause an unnecessary assertion on a warm restart.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.5.0.18.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.5.0.17.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.5.0.15.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.5.0.13.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.5.0.12.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.5.0.17.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.5.0.16.
      • [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.5.0.14.

  • 5.5.0.10
    Release Date: May 10, 2021
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • 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 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 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).
    • 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.

    Bug Fixes

    • Enterprise Only
      • [AER-6420] - (DEPLOYMENT) Feature key parser does not handle DOS line endings.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.5.0.18.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.5.0.17.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.5.0.15.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.5.0.13.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.5.0.12.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.5.0.17.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.5.0.16.
      • [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.5.0.14.
      • [AER-6427] - (KVS) For data-in-index namespaces, durable deletes will cause an unnecessary assertion on a warm restart. Fixed in version 5.5.0.11.

  • 5.5.0.9
    Release Date: April 6, 2021
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • 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 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 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).
    • 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.

    Improvements

    • Enterprise Only
      • [AER-6419] - (DEPLOYMENT) Use only non-zero values when combining cluster-nodes-limit from different feature key files to determine the effective limit.

    Bug Fixes

    • Enterprise & Community
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.5.0.18.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.5.0.17.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.5.0.15.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.5.0.13.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.5.0.12.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.5.0.17.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.5.0.16.
      • [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.5.0.14.
      • [AER-6427] - (KVS) For data-in-index namespaces, durable deletes will cause an unnecessary assertion on a warm restart. Fixed in version 5.5.0.11.
      • [AER-6420] - (DEPLOYMENT) Feature key parser does not handle DOS line endings. Fixed in version 5.5.0.10.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing. Fixed in version 5.5.0.10.

  • 5.5.0.8
    Release Date: April 2, 2021
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • 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 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 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).
    • 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.

    Bug Fixes

    • Enterprise & Community
      • [AER-6414] - (UDF) For namespaces with data not in memory, UDF replications will not adjust the secondary index.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.5.0.18.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.5.0.17.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.5.0.15.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.5.0.13.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.5.0.12.
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory. Fixed in version 5.5.0.9.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.5.0.17.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.5.0.16.
      • [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.5.0.14.
      • [AER-6427] - (KVS) For data-in-index namespaces, durable deletes will cause an unnecessary assertion on a warm restart. Fixed in version 5.5.0.11.
      • [AER-6420] - (DEPLOYMENT) Feature key parser does not handle DOS line endings. Fixed in version 5.5.0.10.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing. Fixed in version 5.5.0.10.

  • 5.5.0.7
    Release Date: March 29, 2021
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • 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 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 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).
    • 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.

    Bug Fixes

    • Enterprise & Community
      • [AER-6412] - (QUERY) If a query transaction setup fails in certain ways, improper cleanup may cause a crash.
    • Enterprise Only
      • [AER-6413] - (LDAP) Small memory leak during LDAP login process.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.5.0.18.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.5.0.17.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.5.0.15.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.5.0.13.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.5.0.12.
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory. Fixed in version 5.5.0.9.
      • [AER-6414] - (UDF) For namespaces with data not in memory, UDF replications will not adjust the secondary index. Fixed in version 5.5.0.8.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.5.0.17.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.5.0.16.
      • [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.5.0.14.
      • [AER-6427] - (KVS) For data-in-index namespaces, durable deletes will cause an unnecessary assertion on a warm restart. Fixed in version 5.5.0.11.
      • [AER-6420] - (DEPLOYMENT) Feature key parser does not handle DOS line endings. Fixed in version 5.5.0.10.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing. Fixed in version 5.5.0.10.

  • 5.5.0.4
    Release Date: March 12, 2021
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • 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 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 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).
    • 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.

    Bug Fixes

    • Enterprise & Community
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical.
      • [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.
      • [AER-6396] - (STATS) The dup_res_ask statistic may be incorrect for write transactions.
    • Enterprise Only
      • [AER-6403] - (KVS) Corrupt bin-ops from clients are not properly checked before endian swapping, and may cause a crash.
      • [AER-6404] - (KVS) For single-bin, data-in-memory namespaces, durable deletes may cause a crash on writing replicas or on subsequent restarts.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.5.0.18.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.5.0.17.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.5.0.15.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.5.0.13.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.5.0.12.
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory. Fixed in version 5.5.0.9.
      • [AER-6414] - (UDF) For namespaces with data not in memory, UDF replications will not adjust the secondary index. Fixed in version 5.5.0.8.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.5.0.17.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.5.0.16.
      • [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.5.0.14.
      • [AER-6427] - (KVS) For data-in-index namespaces, durable deletes will cause an unnecessary assertion on a warm restart. Fixed in version 5.5.0.11.
      • [AER-6420] - (DEPLOYMENT) Feature key parser does not handle DOS line endings. Fixed in version 5.5.0.10.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing. Fixed in version 5.5.0.10.
      • [AER-6413] - (LDAP) Small memory leak during LDAP login process. Fixed in version 5.5.0.7.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.5.0.7.

  • 5.5.0.3
    Release Date: February 12, 2021
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • 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 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 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).
    • 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.

    Bug Fixes

    • Enterprise Only
      • [AER-6390] - (XDR) For strong-consistency namespaces, when DC namespace context configuration item bin-policy is not 'all', shipping records that are unreplicated may miss some bins.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.5.0.18.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.5.0.17.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.5.0.15.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.5.0.13.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.5.0.12.
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory. Fixed in version 5.5.0.9.
      • [AER-6414] - (UDF) For namespaces with data not in memory, UDF replications will not adjust the secondary index. Fixed in version 5.5.0.8.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 5.5.0.4.
      • [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.5.0.4.
      • [AER-6396] - (STATS) The dup_res_ask statistic may be incorrect for write transactions. Fixed in version 5.5.0.4.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.5.0.17.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.5.0.16.
      • [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.5.0.14.
      • [AER-6427] - (KVS) For data-in-index namespaces, durable deletes will cause an unnecessary assertion on a warm restart. Fixed in version 5.5.0.11.
      • [AER-6420] - (DEPLOYMENT) Feature key parser does not handle DOS line endings. Fixed in version 5.5.0.10.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing. Fixed in version 5.5.0.10.
      • [AER-6413] - (LDAP) Small memory leak during LDAP login process. Fixed in version 5.5.0.7.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.5.0.7.
      • [AER-6403] - (KVS) Corrupt bin-ops from clients are not properly checked before endian swapping, and may cause a crash. Fixed in version 5.5.0.4.
      • [AER-6404] - (KVS) For single-bin, data-in-memory namespaces, durable deletes may cause a crash on writing replicas or on subsequent restarts. Fixed in version 5.5.0.4.

  • 5.5.0.2
    Release Date: February 5, 2021
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • 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 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 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).
    • 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.

    New Features

    • Enterprise & Community
      • [AER-6389] - (PACKAGING) Removed support for CentOS 6.

    Improvements

    • Enterprise & Community
      • [AER-6388] - (DEPLOYMENT) When starting Aerospike under systemd, wait for the network to be available.
      • [AER-6387] - (STATS) Added duplicate resolution statistics and log ticker line.
      • [AER-6385] - (UDF) Unpack msgpack booleans as booleans instead of converting them to integers.
    • Enterprise Only
      • [AER-6386] - (DEPLOYMENT) Added support for fetching and using multiple feature keys in one server instance.
      • [AER-6370] - (XDR) Added support for record deletion with bin level convergence.
      • [AER-6384] - (XDR) Added DC context configuration item max-recoveries-interleaved to limit the number of partitions to recover concurrently.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.5.0.18.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.5.0.17.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.5.0.15.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.5.0.13.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.5.0.12.
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory. Fixed in version 5.5.0.9.
      • [AER-6414] - (UDF) For namespaces with data not in memory, UDF replications will not adjust the secondary index. Fixed in version 5.5.0.8.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 5.5.0.4.
      • [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.5.0.4.
      • [AER-6396] - (STATS) The dup_res_ask statistic may be incorrect for write transactions. Fixed in version 5.5.0.4.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.5.0.17.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.5.0.16.
      • [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.5.0.14.
      • [AER-6427] - (KVS) For data-in-index namespaces, durable deletes will cause an unnecessary assertion on a warm restart. Fixed in version 5.5.0.11.
      • [AER-6420] - (DEPLOYMENT) Feature key parser does not handle DOS line endings. Fixed in version 5.5.0.10.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing. Fixed in version 5.5.0.10.
      • [AER-6413] - (LDAP) Small memory leak during LDAP login process. Fixed in version 5.5.0.7.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.5.0.7.
      • [AER-6403] - (KVS) Corrupt bin-ops from clients are not properly checked before endian swapping, and may cause a crash. Fixed in version 5.5.0.4.
      • [AER-6404] - (KVS) For single-bin, data-in-memory namespaces, durable deletes may cause a crash on writing replicas or on subsequent restarts. Fixed in version 5.5.0.4.
      • [AER-6390] - (XDR) For strong-consistency namespaces, when DC namespace context configuration item bin-policy is not 'all', shipping records that are unreplicated may miss some bins. Fixed in version 5.5.0.3.

    Updates

  • 5.4.0.21
    Release Date: September 20, 2021
    • Downgrading from Aerospike Database version 5.4 or newer to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • 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 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 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).
    • 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.

    Bug Fixes

    • Enterprise & Community
      • [AER-6481] - (KVS) When a service thread exits, its epoll queue's event file descriptor leaks.
      • [AER-6482] - (STORAGE) When a device runs completely out of space, defrag becomes ineffective.
    • Enterprise Only

  • 5.4.0.20
    Release Date: September 15, 2021
    • Downgrading from Aerospike Database version 5.4 or newer to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • 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 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 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).
    • 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.

    Bug Fixes

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted.

  • 5.4.0.19
    Release Date: September 2, 2021
    • Downgrading from Aerospike Database version 5.4 or newer to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • 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 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 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).
    • 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.

    Improvements

    • Enterprise & Community
      • [AER-6475] - (GEO) For data-in-memory namespaces, when trimming GeoJSON particles, reallocate into the appropriate namespace arena.

    Bug Fixes

    • Enterprise & Community
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.4.0.20.

  • 5.4.0.18
    Release Date: August 4, 2021
    • Downgrading from Aerospike Database version 5.4 or newer to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • 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 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 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).
    • 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.

    Bug Fixes

    • Enterprise Only
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.4.0.20.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.4.0.19.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.4.0.19.

  • 5.4.0.17
    Release Date: July 22, 2021
    • Downgrading from Aerospike Database version 5.4 or newer to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • 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 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 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).
    • 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.

    Bug Fixes

    • Enterprise & Community
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.4.0.20.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.4.0.19.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.4.0.19.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.4.0.18.

  • 5.4.0.16
    Release Date: July 19, 2021
    • Downgrading from Aerospike Database version 5.4 or newer to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • 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 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 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).
    • 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.

    Bug Fixes

    • 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.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.4.0.20.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.4.0.19.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.4.0.17.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.4.0.19.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.4.0.18.

  • 5.4.0.15
    Release Date: June 24, 2021
    • Downgrading from Aerospike Database version 5.4 or newer to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • 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 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 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).
    • 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.

    Bug Fixes

    • Enterprise & Community
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.4.0.20.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.4.0.19.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.4.0.17.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.4.0.19.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.4.0.18.
      • [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.4.0.16.

  • 5.4.0.14
    Release Date: May 28, 2021
    • Downgrading from Aerospike Database version 5.4 or newer to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • 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 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 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).
    • 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.

    Bug Fixes

    • Enterprise & Community
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.4.0.20.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.4.0.19.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.4.0.17.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.4.0.15.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.4.0.19.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.4.0.18.
      • [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.4.0.16.

  • 5.4.0.13
    Release Date: May 25, 2021
    • Downgrading from Aerospike Database version 5.4 or newer to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • 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 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 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).
    • 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.

    Bug Fixes

    • Enterprise Only
      • [AER-6427] - (KVS) For data-in-index namespaces, durable deletes will cause an unnecessary assertion on a warm restart.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.4.0.20.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.4.0.19.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.4.0.17.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.4.0.15.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.4.0.14.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.4.0.19.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.4.0.18.
      • [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.4.0.16.

  • 5.4.0.12
    Release Date: May 10, 2021
    • Downgrading from Aerospike Database version 5.4 or newer to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • 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 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 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).
    • 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.

    Bug Fixes

    • Enterprise Only
      • [AER-6420] - (DEPLOYMENT) Feature key parser does not handle DOS line endings.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.4.0.20.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.4.0.19.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.4.0.17.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.4.0.15.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.4.0.14.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.4.0.19.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.4.0.18.
      • [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.4.0.16.
      • [AER-6427] - (KVS) For data-in-index namespaces, durable deletes will cause an unnecessary assertion on a warm restart. Fixed in version 5.4.0.13.

  • 5.4.0.11
    Release Date: April 6, 2021
    • Downgrading from Aerospike Database version 5.4 or newer to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • 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 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 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).
    • 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.

    Bug Fixes

    • Enterprise & Community
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.4.0.20.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.4.0.19.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.4.0.17.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.4.0.15.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.4.0.14.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.4.0.19.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.4.0.18.
      • [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.4.0.16.
      • [AER-6427] - (KVS) For data-in-index namespaces, durable deletes will cause an unnecessary assertion on a warm restart. Fixed in version 5.4.0.13.
      • [AER-6420] - (DEPLOYMENT) Feature key parser does not handle DOS line endings. Fixed in version 5.4.0.12.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing. Fixed in version 5.4.0.12.

  • 5.4.0.10
    Release Date: April 2, 2021
    • Downgrading from Aerospike Database version 5.4 or newer to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • 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 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 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).
    • 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.

    Bug Fixes

    • Enterprise & Community
      • [AER-6414] - (UDF) For namespaces with data not in memory, UDF replications will not adjust the secondary index.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.4.0.20.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.4.0.19.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.4.0.17.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.4.0.15.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.4.0.14.
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory. Fixed in version 5.4.0.11.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.4.0.19.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.4.0.18.
      • [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.4.0.16.
      • [AER-6427] - (KVS) For data-in-index namespaces, durable deletes will cause an unnecessary assertion on a warm restart. Fixed in version 5.4.0.13.
      • [AER-6420] - (DEPLOYMENT) Feature key parser does not handle DOS line endings. Fixed in version 5.4.0.12.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing. Fixed in version 5.4.0.12.

  • 5.4.0.9
    Release Date: March 29, 2021
    • Downgrading from Aerospike Database version 5.4 or newer to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • 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 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 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).
    • 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.

    Bug Fixes

    • Enterprise & Community
      • [AER-6412] - (QUERY) If a query transaction setup fails in certain ways, improper cleanup may cause a crash.
    • Enterprise Only
      • [AER-6413] - (LDAP) Small memory leak during LDAP login process.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.4.0.20.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.4.0.19.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.4.0.17.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.4.0.15.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.4.0.14.
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory. Fixed in version 5.4.0.11.
      • [AER-6414] - (UDF) For namespaces with data not in memory, UDF replications will not adjust the secondary index. Fixed in version 5.4.0.10.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.4.0.19.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.4.0.18.
      • [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.4.0.16.
      • [AER-6427] - (KVS) For data-in-index namespaces, durable deletes will cause an unnecessary assertion on a warm restart. Fixed in version 5.4.0.13.
      • [AER-6420] - (DEPLOYMENT) Feature key parser does not handle DOS line endings. Fixed in version 5.4.0.12.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing. Fixed in version 5.4.0.12.

  • 5.4.0.6
    Release Date: March 12, 2021
    • Downgrading from Aerospike Database version 5.4 or newer to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • 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 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 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).
    • 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.

    Bug Fixes

    • Enterprise & Community
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical.
      • [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.
    • Enterprise Only
      • [AER-6403] - (KVS) Corrupt bin-ops from clients are not properly checked before endian swapping, and may cause a crash.
      • [AER-6404] - (KVS) For single-bin, data-in-memory namespaces, durable deletes may cause a crash on writing replicas or on subsequent restarts.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.4.0.20.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.4.0.19.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.4.0.17.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.4.0.15.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.4.0.14.
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory. Fixed in version 5.4.0.11.
      • [AER-6414] - (UDF) For namespaces with data not in memory, UDF replications will not adjust the secondary index. Fixed in version 5.4.0.10.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.4.0.19.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.4.0.18.
      • [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.4.0.16.
      • [AER-6427] - (KVS) For data-in-index namespaces, durable deletes will cause an unnecessary assertion on a warm restart. Fixed in version 5.4.0.13.
      • [AER-6420] - (DEPLOYMENT) Feature key parser does not handle DOS line endings. Fixed in version 5.4.0.12.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing. Fixed in version 5.4.0.12.
      • [AER-6413] - (LDAP) Small memory leak during LDAP login process. Fixed in version 5.4.0.9.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.4.0.9.

  • 5.4.0.5
    Release Date: February 12, 2021
    • Downgrading from Aerospike Database version 5.4 or newer to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • 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 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 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).
    • 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.

    Bug Fixes

    • Enterprise Only
      • [AER-6390] - (XDR) For strong-consistency namespaces, when DC namespace context configuration item bin-policy is not 'all', shipping records that are unreplicated may miss some bins.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.4.0.20.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.4.0.19.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.4.0.17.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.4.0.15.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.4.0.14.
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory. Fixed in version 5.4.0.11.
      • [AER-6414] - (UDF) For namespaces with data not in memory, UDF replications will not adjust the secondary index. Fixed in version 5.4.0.10.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 5.4.0.6.
      • [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.4.0.6.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.4.0.19.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.4.0.18.
      • [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.4.0.16.
      • [AER-6427] - (KVS) For data-in-index namespaces, durable deletes will cause an unnecessary assertion on a warm restart. Fixed in version 5.4.0.13.
      • [AER-6420] - (DEPLOYMENT) Feature key parser does not handle DOS line endings. Fixed in version 5.4.0.12.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing. Fixed in version 5.4.0.12.
      • [AER-6413] - (LDAP) Small memory leak during LDAP login process. Fixed in version 5.4.0.9.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.4.0.9.
      • [AER-6403] - (KVS) Corrupt bin-ops from clients are not properly checked before endian swapping, and may cause a crash. Fixed in version 5.4.0.6.
      • [AER-6404] - (KVS) For single-bin, data-in-memory namespaces, durable deletes may cause a crash on writing replicas or on subsequent restarts. Fixed in version 5.4.0.6.

  • 5.4.0.4
    Release Date: January 30, 2021
    • Downgrading from Aerospike Database version 5.4 or newer to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • 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 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 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).
    • 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.

    Bug Fixes

    • Enterprise & Community
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated.
    • Enterprise Only
      • [AER-6382] - (LDAP) When connecting to LDAP server, TLS handshake occasionally fails.
      • [AER-6381] - (XDR) If a record expires between XDR reading and shipping, improper TTL will be shipped.
      • [AER-6383] - (XDR) If using bin convergence, UDF writes may be incorrectly rejected.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.4.0.20.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.4.0.19.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.4.0.17.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.4.0.15.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.4.0.14.
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory. Fixed in version 5.4.0.11.
      • [AER-6414] - (UDF) For namespaces with data not in memory, UDF replications will not adjust the secondary index. Fixed in version 5.4.0.10.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 5.4.0.6.
      • [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.4.0.6.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.4.0.19.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.4.0.18.
      • [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.4.0.16.
      • [AER-6427] - (KVS) For data-in-index namespaces, durable deletes will cause an unnecessary assertion on a warm restart. Fixed in version 5.4.0.13.
      • [AER-6420] - (DEPLOYMENT) Feature key parser does not handle DOS line endings. Fixed in version 5.4.0.12.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing. Fixed in version 5.4.0.12.
      • [AER-6413] - (LDAP) Small memory leak during LDAP login process. Fixed in version 5.4.0.9.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.4.0.9.
      • [AER-6403] - (KVS) Corrupt bin-ops from clients are not properly checked before endian swapping, and may cause a crash. Fixed in version 5.4.0.6.
      • [AER-6404] - (KVS) For single-bin, data-in-memory namespaces, durable deletes may cause a crash on writing replicas or on subsequent restarts. Fixed in version 5.4.0.6.
      • [AER-6390] - (XDR) For strong-consistency namespaces, when DC namespace context configuration item bin-policy is not 'all', shipping records that are unreplicated may miss some bins. Fixed in version 5.4.0.5.

  • 5.4.0.3
    Release Date: January 25, 2021
    • Downgrading from Aerospike Database version 5.4 or newer to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • 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 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 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).
    • 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.

    Improvements

    • Enterprise Only
      • [AER-6377] - (XDR) Added service context configuration item downgrading, to enable stripping bin metadata from records sent to older nodes.

    Bug Fixes

    • Enterprise Only
      • [AER-6376] - (LDAP) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library.
      • [AER-6378] - (ACL) 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.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.4.0.20.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.4.0.19.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.4.0.17.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.4.0.15.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.4.0.14.
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory. Fixed in version 5.4.0.11.
      • [AER-6414] - (UDF) For namespaces with data not in memory, UDF replications will not adjust the secondary index. Fixed in version 5.4.0.10.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 5.4.0.6.
      • [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.4.0.6.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 5.4.0.4.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.4.0.19.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.4.0.18.
      • [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.4.0.16.
      • [AER-6427] - (KVS) For data-in-index namespaces, durable deletes will cause an unnecessary assertion on a warm restart. Fixed in version 5.4.0.13.
      • [AER-6420] - (DEPLOYMENT) Feature key parser does not handle DOS line endings. Fixed in version 5.4.0.12.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing. Fixed in version 5.4.0.12.
      • [AER-6413] - (LDAP) Small memory leak during LDAP login process. Fixed in version 5.4.0.9.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.4.0.9.
      • [AER-6403] - (KVS) Corrupt bin-ops from clients are not properly checked before endian swapping, and may cause a crash. Fixed in version 5.4.0.6.
      • [AER-6404] - (KVS) For single-bin, data-in-memory namespaces, durable deletes may cause a crash on writing replicas or on subsequent restarts. Fixed in version 5.4.0.6.
      • [AER-6390] - (XDR) For strong-consistency namespaces, when DC namespace context configuration item bin-policy is not 'all', shipping records that are unreplicated may miss some bins. Fixed in version 5.4.0.5.
      • [AER-6382] - (LDAP) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 5.4.0.4.
      • [AER-6381] - (XDR) If a record expires between XDR reading and shipping, improper TTL will be shipped. Fixed in version 5.4.0.4.
      • [AER-6383] - (XDR) If using bin convergence, UDF writes may be incorrectly rejected. Fixed in version 5.4.0.4.

  • 5.4.0.2
    Release Date: January 15, 2021
    • 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 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).
    • 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.

    Bug Fixes

    • Enterprise Only
      • [AER-6366] - (XDR) Dynamically removing a connector seed node may cause a crash.
      • [AER-6369] - (XDR) When shipping the first record on a connection, if all bins are filtered out, a crash may result.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.4.0.20.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.4.0.19.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.4.0.17.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.4.0.15.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.4.0.14.
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory. Fixed in version 5.4.0.11.
      • [AER-6414] - (UDF) For namespaces with data not in memory, UDF replications will not adjust the secondary index. Fixed in version 5.4.0.10.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 5.4.0.6.
      • [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.4.0.6.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 5.4.0.4.
    • Enterprise Only
      • Downgrading from Aerospike Database version 5.4 or newer to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
      • 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.
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.4.0.19.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.4.0.18.
      • [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.4.0.16.
      • [AER-6427] - (KVS) For data-in-index namespaces, durable deletes will cause an unnecessary assertion on a warm restart. Fixed in version 5.4.0.13.
      • [AER-6420] - (DEPLOYMENT) Feature key parser does not handle DOS line endings. Fixed in version 5.4.0.12.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing. Fixed in version 5.4.0.12.
      • [AER-6413] - (LDAP) Small memory leak during LDAP login process. Fixed in version 5.4.0.9.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.4.0.9.
      • [AER-6403] - (KVS) Corrupt bin-ops from clients are not properly checked before endian swapping, and may cause a crash. Fixed in version 5.4.0.6.
      • [AER-6404] - (KVS) For single-bin, data-in-memory namespaces, durable deletes may cause a crash on writing replicas or on subsequent restarts. Fixed in version 5.4.0.6.
      • [AER-6390] - (XDR) For strong-consistency namespaces, when DC namespace context configuration item bin-policy is not 'all', shipping records that are unreplicated may miss some bins. Fixed in version 5.4.0.5.
      • [AER-6382] - (LDAP) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 5.4.0.4.
      • [AER-6381] - (XDR) If a record expires between XDR reading and shipping, improper TTL will be shipped. Fixed in version 5.4.0.4.
      • [AER-6383] - (XDR) If using bin convergence, UDF writes may be incorrectly rejected. Fixed in version 5.4.0.4.
      • [AER-6376] - (LDAP) 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.4.0.3.
      • [AER-6378] - (ACL) 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.4.0.3.

  • 5.4.0.1
    Release Date: January 13, 2021
    • 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 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).
    • 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.

    New Features

    • Enterprise Only
      • [AER-6299] - (XDR) Added bin level convergence for active-active scenarios.

    Improvements

    • Enterprise & Community
      • [AER-6367] - (KVS) For namespaces with data-in-memory true, reduced memory cost per bin by one byte.
      • [AER-6359] - (LOGGING) Changed warnings to detail level for CDT, HLL, and bitwise blob operations that fail due to policy violations.
      • [AER-6364] - (LOGGING) Changed logging level for 'starting/finished basic scan job...' messages from info to debug.
    • Enterprise Only
      • [AER-6354] - (DEPLOYMENT) Added support for fetching feature key from Vault or from an environment variable.
      • [AER-6355] - (DEPLOYMENT) Added support for feature-key-version 2.
      • [AER-6362] - (XDR) The xdr-get-filter info command now displays filter expressions in a logical language instead of as a base64 string.

    Bug Fixes

    • Enterprise & Community
      • [AER-6340] - (KVS) HLL string or blob elements sized 31 to 254 bytes may be treated differently depending on msgpack standard.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.4.0.20.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.4.0.19.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.4.0.17.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.4.0.15.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.4.0.14.
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory. Fixed in version 5.4.0.11.
      • [AER-6414] - (UDF) For namespaces with data not in memory, UDF replications will not adjust the secondary index. Fixed in version 5.4.0.10.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 5.4.0.6.
      • [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.4.0.6.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 5.4.0.4.
    • Enterprise Only
      • Downgrading from Aerospike Database version 5.4 or newer to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
      • 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.
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.4.0.19.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.4.0.18.
      • [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.4.0.16.
      • [AER-6427] - (KVS) For data-in-index namespaces, durable deletes will cause an unnecessary assertion on a warm restart. Fixed in version 5.4.0.13.
      • [AER-6420] - (DEPLOYMENT) Feature key parser does not handle DOS line endings. Fixed in version 5.4.0.12.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing. Fixed in version 5.4.0.12.
      • [AER-6413] - (LDAP) Small memory leak during LDAP login process. Fixed in version 5.4.0.9.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.4.0.9.
      • [AER-6403] - (KVS) Corrupt bin-ops from clients are not properly checked before endian swapping, and may cause a crash. Fixed in version 5.4.0.6.
      • [AER-6404] - (KVS) For single-bin, data-in-memory namespaces, durable deletes may cause a crash on writing replicas or on subsequent restarts. Fixed in version 5.4.0.6.
      • [AER-6390] - (XDR) For strong-consistency namespaces, when DC namespace context configuration item bin-policy is not 'all', shipping records that are unreplicated may miss some bins. Fixed in version 5.4.0.5.
      • [AER-6382] - (LDAP) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 5.4.0.4.
      • [AER-6381] - (XDR) If a record expires between XDR reading and shipping, improper TTL will be shipped. Fixed in version 5.4.0.4.
      • [AER-6383] - (XDR) If using bin convergence, UDF writes may be incorrectly rejected. Fixed in version 5.4.0.4.
      • [AER-6376] - (LDAP) 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.4.0.3.
      • [AER-6378] - (ACL) 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.4.0.3.
      • [AER-6366] - (XDR) Dynamically removing a connector seed node may cause a crash. Fixed in version 5.4.0.2.
      • [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.4.0.2.

  • 5.3.0.26
    Release Date: September 20, 2021
    • 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 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 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).
    • 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.

    Bug Fixes

    • Enterprise & Community
      • [AER-6481] - (KVS) When a service thread exits, its epoll queue's event file descriptor leaks.
      • [AER-6482] - (STORAGE) When a device runs completely out of space, defrag becomes ineffective.
    • Enterprise Only

  • 5.3.0.25
    Release Date: September 15, 2021
    • 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 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 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).
    • 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.

    Bug Fixes

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted.

  • 5.3.0.24
    Release Date: September 2, 2021
    • 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 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 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).
    • 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.

    Improvements

    • Enterprise & Community
      • [AER-6475] - (GEO) For data-in-memory namespaces, when trimming GeoJSON particles, reallocate into the appropriate namespace arena.

    Bug Fixes

    • Enterprise & Community
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.3.0.25.

  • 5.3.0.23
    Release Date: August 4, 2021
    • 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 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 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).
    • 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.

    Bug Fixes

    • Enterprise Only
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.3.0.25.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.3.0.24.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.3.0.24.

  • 5.3.0.22
    Release Date: July 22, 2021
    • 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 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 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).
    • 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.

    Bug Fixes

    • Enterprise & Community
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.3.0.25.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.3.0.24.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.3.0.24.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.3.0.23.

  • 5.3.0.21
    Release Date: July 19, 2021
    • 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 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 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).
    • 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.

    Bug Fixes

    • 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.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.3.0.25.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.3.0.24.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.3.0.22.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.3.0.24.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.3.0.23.

  • 5.3.0.20
    Release Date: June 24, 2021
    • 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 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 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).
    • 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.

    Bug Fixes

    • Enterprise & Community
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.3.0.25.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.3.0.24.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.3.0.22.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.3.0.24.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.3.0.23.
      • [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.3.0.21.

  • 5.3.0.19
    Release Date: May 28, 2021
    • 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 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 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).
    • 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.

    Bug Fixes

    • Enterprise & Community
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.3.0.25.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.3.0.24.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.3.0.22.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.3.0.20.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.3.0.24.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.3.0.23.
      • [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.3.0.21.

  • 5.3.0.18
    Release Date: May 25, 2021
    • 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 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 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).
    • 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.

    Bug Fixes

    • Enterprise Only
      • [AER-6427] - (KVS) For data-in-index namespaces, durable deletes will cause an unnecessary assertion on a warm restart.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.3.0.25.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.3.0.24.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.3.0.22.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.3.0.20.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.3.0.19.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.3.0.24.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.3.0.23.
      • [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.3.0.21.

  • 5.3.0.17
    Release Date: May 10, 2021
    • 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 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 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).
    • 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.

    Bug Fixes

    • Enterprise Only
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.3.0.25.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.3.0.24.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.3.0.22.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.3.0.20.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.3.0.19.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.3.0.24.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.3.0.23.
      • [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.3.0.21.
      • [AER-6427] - (KVS) For data-in-index namespaces, durable deletes will cause an unnecessary assertion on a warm restart. Fixed in version 5.3.0.18.

  • 5.3.0.16
    Release Date: April 6, 2021
    • 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 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 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).
    • 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.

    Bug Fixes

    • Enterprise & Community
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.3.0.25.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.3.0.24.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.3.0.22.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.3.0.20.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.3.0.19.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.3.0.24.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.3.0.23.
      • [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.3.0.21.
      • [AER-6427] - (KVS) For data-in-index namespaces, durable deletes will cause an unnecessary assertion on a warm restart. Fixed in version 5.3.0.18.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing. Fixed in version 5.3.0.17.

  • 5.3.0.15
    Release Date: April 2, 2021
    • 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 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 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).
    • 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.

    Bug Fixes

    • Enterprise & Community
      • [AER-6414] - (UDF) For namespaces with data not in memory, UDF replications will not adjust the secondary index.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.3.0.25.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.3.0.24.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.3.0.22.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.3.0.20.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.3.0.19.
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory. Fixed in version 5.3.0.16.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.3.0.24.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.3.0.23.
      • [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.3.0.21.
      • [AER-6427] - (KVS) For data-in-index namespaces, durable deletes will cause an unnecessary assertion on a warm restart. Fixed in version 5.3.0.18.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing. Fixed in version 5.3.0.17.

  • 5.3.0.14
    Release Date: March 29, 2021
    • 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 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 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).
    • 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.

    Bug Fixes

    • Enterprise & Community
      • [AER-6412] - (QUERY) If a query transaction setup fails in certain ways, improper cleanup may cause a crash.
    • Enterprise Only
      • [AER-6413] - (LDAP) Small memory leak during LDAP login process.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.3.0.25.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.3.0.24.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.3.0.22.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.3.0.20.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.3.0.19.
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory. Fixed in version 5.3.0.16.
      • [AER-6414] - (UDF) For namespaces with data not in memory, UDF replications will not adjust the secondary index. Fixed in version 5.3.0.15.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.3.0.24.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.3.0.23.
      • [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.3.0.21.
      • [AER-6427] - (KVS) For data-in-index namespaces, durable deletes will cause an unnecessary assertion on a warm restart. Fixed in version 5.3.0.18.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing. Fixed in version 5.3.0.17.

  • 5.3.0.11
    Release Date: March 12, 2021
    • 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 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 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).
    • 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.

    Bug Fixes

    • Enterprise & Community
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical.
      • [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.
    • Enterprise Only
      • [AER-6404] - (KVS) For single-bin, data-in-memory namespaces, durable deletes may cause a crash on writing replicas or on subsequent restarts.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.3.0.25.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.3.0.24.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.3.0.22.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.3.0.20.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.3.0.19.
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory. Fixed in version 5.3.0.16.
      • [AER-6414] - (UDF) For namespaces with data not in memory, UDF replications will not adjust the secondary index. Fixed in version 5.3.0.15.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.3.0.24.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.3.0.23.
      • [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.3.0.21.
      • [AER-6427] - (KVS) For data-in-index namespaces, durable deletes will cause an unnecessary assertion on a warm restart. Fixed in version 5.3.0.18.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing. Fixed in version 5.3.0.17.
      • [AER-6413] - (LDAP) Small memory leak during LDAP login process. Fixed in version 5.3.0.14.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.3.0.14.

  • 5.3.0.10
    Release Date: February 12, 2021
    • 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 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 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).
    • 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.

    Bug Fixes

    • Enterprise Only
      • [AER-6390] - (XDR) For strong-consistency namespaces, when DC namespace context configuration item bin-policy is not 'all', shipping records that are unreplicated may miss some bins.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.3.0.25.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.3.0.24.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.3.0.22.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.3.0.20.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.3.0.19.
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory. Fixed in version 5.3.0.16.
      • [AER-6414] - (UDF) For namespaces with data not in memory, UDF replications will not adjust the secondary index. Fixed in version 5.3.0.15.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 5.3.0.11.
      • [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.3.0.11.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.3.0.24.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.3.0.23.
      • [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.3.0.21.
      • [AER-6427] - (KVS) For data-in-index namespaces, durable deletes will cause an unnecessary assertion on a warm restart. Fixed in version 5.3.0.18.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing. Fixed in version 5.3.0.17.
      • [AER-6413] - (LDAP) Small memory leak during LDAP login process. Fixed in version 5.3.0.14.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.3.0.14.
      • [AER-6404] - (KVS) For single-bin, data-in-memory namespaces, durable deletes may cause a crash on writing replicas or on subsequent restarts. Fixed in version 5.3.0.11.

  • 5.3.0.9
    Release Date: January 30, 2021
    • 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 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 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).
    • 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.

    Bug Fixes

    • Enterprise & Community
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated.
    • Enterprise Only
      • [AER-6382] - (LDAP) When connecting to LDAP server, TLS handshake occasionally fails.
      • [AER-6381] - (XDR) If a record expires between XDR reading and shipping, improper TTL will be shipped.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.3.0.25.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.3.0.24.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.3.0.22.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.3.0.20.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.3.0.19.
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory. Fixed in version 5.3.0.16.
      • [AER-6414] - (UDF) For namespaces with data not in memory, UDF replications will not adjust the secondary index. Fixed in version 5.3.0.15.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 5.3.0.11.
      • [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.3.0.11.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.3.0.24.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.3.0.23.
      • [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.3.0.21.
      • [AER-6427] - (KVS) For data-in-index namespaces, durable deletes will cause an unnecessary assertion on a warm restart. Fixed in version 5.3.0.18.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing. Fixed in version 5.3.0.17.
      • [AER-6413] - (LDAP) Small memory leak during LDAP login process. Fixed in version 5.3.0.14.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.3.0.14.
      • [AER-6404] - (KVS) For single-bin, data-in-memory namespaces, durable deletes may cause a crash on writing replicas or on subsequent restarts. Fixed in version 5.3.0.11.
      • [AER-6390] - (XDR) For strong-consistency namespaces, when DC namespace context configuration item bin-policy is not 'all', shipping records that are unreplicated may miss some bins. Fixed in version 5.3.0.10.

  • 5.3.0.8
    Release Date: January 25, 2021
    • 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 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 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).
    • 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.

    Improvements

    • Enterprise Only
      • [AER-6377] - (XDR) Added service context configuration item downgrading, to enable stripping bin metadata from records sent to older nodes.

    Bug Fixes

    • Enterprise Only
      • [AER-6376] - (LDAP) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library.
      • [AER-6378] - (ACL) 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.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.3.0.25.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.3.0.24.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.3.0.22.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.3.0.20.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.3.0.19.
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory. Fixed in version 5.3.0.16.
      • [AER-6414] - (UDF) For namespaces with data not in memory, UDF replications will not adjust the secondary index. Fixed in version 5.3.0.15.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 5.3.0.11.
      • [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.3.0.11.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 5.3.0.9.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.3.0.24.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.3.0.23.
      • [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.3.0.21.
      • [AER-6427] - (KVS) For data-in-index namespaces, durable deletes will cause an unnecessary assertion on a warm restart. Fixed in version 5.3.0.18.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing. Fixed in version 5.3.0.17.
      • [AER-6413] - (LDAP) Small memory leak during LDAP login process. Fixed in version 5.3.0.14.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.3.0.14.
      • [AER-6404] - (KVS) For single-bin, data-in-memory namespaces, durable deletes may cause a crash on writing replicas or on subsequent restarts. Fixed in version 5.3.0.11.
      • [AER-6390] - (XDR) For strong-consistency namespaces, when DC namespace context configuration item bin-policy is not 'all', shipping records that are unreplicated may miss some bins. Fixed in version 5.3.0.10.
      • [AER-6382] - (LDAP) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 5.3.0.9.
      • [AER-6381] - (XDR) If a record expires between XDR reading and shipping, improper TTL will be shipped. Fixed in version 5.3.0.9.

  • 5.3.0.7
    Release Date: January 15, 2021
    • 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 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).
    • 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.

    Bug Fixes

    • Enterprise Only
      • [AER-6366] - (XDR) Dynamically removing a connector seed node may cause a crash.
      • [AER-6369] - (XDR) When shipping the first record on a connection, if all bins are filtered out, a crash may result.

    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-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.3.0.25.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.3.0.24.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.3.0.22.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.3.0.20.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.3.0.19.
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory. Fixed in version 5.3.0.16.
      • [AER-6414] - (UDF) For namespaces with data not in memory, UDF replications will not adjust the secondary index. Fixed in version 5.3.0.15.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 5.3.0.11.
      • [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.3.0.11.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 5.3.0.9.
    • Enterprise Only
      • 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.
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.3.0.24.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.3.0.23.
      • [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.3.0.21.
      • [AER-6427] - (KVS) For data-in-index namespaces, durable deletes will cause an unnecessary assertion on a warm restart. Fixed in version 5.3.0.18.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing. Fixed in version 5.3.0.17.
      • [AER-6413] - (LDAP) Small memory leak during LDAP login process. Fixed in version 5.3.0.14.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.3.0.14.
      • [AER-6404] - (KVS) For single-bin, data-in-memory namespaces, durable deletes may cause a crash on writing replicas or on subsequent restarts. Fixed in version 5.3.0.11.
      • [AER-6390] - (XDR) For strong-consistency namespaces, when DC namespace context configuration item bin-policy is not 'all', shipping records that are unreplicated may miss some bins. Fixed in version 5.3.0.10.
      • [AER-6382] - (LDAP) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 5.3.0.9.
      • [AER-6381] - (XDR) If a record expires between XDR reading and shipping, improper TTL will be shipped. Fixed in version 5.3.0.9.
      • [AER-6376] - (LDAP) 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.3.0.8.
      • [AER-6378] - (ACL) 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.3.0.8.

  • 5.3.0.6
    Release Date: January 7, 2021
    • 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 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).
    • 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.

    Bug Fixes

    • Enterprise Only
      • [AER-6365] - (XDR) Reverts behavior change in AER-6240 as empty node addition may reject a lagging last ship time from the acting master, which may result in records not shipping.

    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-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.3.0.25.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.3.0.24.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.3.0.22.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.3.0.20.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.3.0.19.
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory. Fixed in version 5.3.0.16.
      • [AER-6414] - (UDF) For namespaces with data not in memory, UDF replications will not adjust the secondary index. Fixed in version 5.3.0.15.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 5.3.0.11.
      • [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.3.0.11.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 5.3.0.9.
    • Enterprise Only
      • 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.
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.3.0.24.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.3.0.23.
      • [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.3.0.21.
      • [AER-6427] - (KVS) For data-in-index namespaces, durable deletes will cause an unnecessary assertion on a warm restart. Fixed in version 5.3.0.18.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing. Fixed in version 5.3.0.17.
      • [AER-6413] - (LDAP) Small memory leak during LDAP login process. Fixed in version 5.3.0.14.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.3.0.14.
      • [AER-6404] - (KVS) For single-bin, data-in-memory namespaces, durable deletes may cause a crash on writing replicas or on subsequent restarts. Fixed in version 5.3.0.11.
      • [AER-6390] - (XDR) For strong-consistency namespaces, when DC namespace context configuration item bin-policy is not 'all', shipping records that are unreplicated may miss some bins. Fixed in version 5.3.0.10.
      • [AER-6382] - (LDAP) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 5.3.0.9.
      • [AER-6381] - (XDR) If a record expires between XDR reading and shipping, improper TTL will be shipped. Fixed in version 5.3.0.9.
      • [AER-6376] - (LDAP) 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.3.0.8.
      • [AER-6378] - (ACL) 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.3.0.8.
      • [AER-6366] - (XDR) Dynamically removing a connector seed node may cause a crash. Fixed in version 5.3.0.7.
      • [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.3.0.7.

  • 5.3.0.5
    Release Date: January 4, 2021
    • 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 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).
    • 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.

    Improvements

    • Enterprise & Community
      • [AER-6357] - (KVS) Handle exceeding the OS file descriptor limit gracefully, without asserting.
    • Enterprise Only
      • [AER-6360] - (XDR) Close idle connections when DC context configuration item max-used-service-threads is decreased dynamically.

    Bug Fixes

    • Enterprise & Community
      • [AER-6358] - (KVS) For single-bin, data-in-memory namespaces, unwinding on failing a write operation may incorrectly free the original bin particle.
    • Enterprise Only
      • [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.
      • [AER-6361] - (LDAP) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item.
      • [AER-6356] - (XDR) When DC namespace context configuration item bin-policy is not 'all', locally written bins may not get shipped during recovery.

    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-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.3.0.25.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.3.0.24.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.3.0.22.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.3.0.20.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.3.0.19.
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory. Fixed in version 5.3.0.16.
      • [AER-6414] - (UDF) For namespaces with data not in memory, UDF replications will not adjust the secondary index. Fixed in version 5.3.0.15.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 5.3.0.11.
      • [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.3.0.11.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 5.3.0.9.
    • Enterprise Only
      • 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.
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.3.0.24.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.3.0.23.
      • [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.3.0.21.
      • [AER-6427] - (KVS) For data-in-index namespaces, durable deletes will cause an unnecessary assertion on a warm restart. Fixed in version 5.3.0.18.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing. Fixed in version 5.3.0.17.
      • [AER-6413] - (LDAP) Small memory leak during LDAP login process. Fixed in version 5.3.0.14.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.3.0.14.
      • [AER-6404] - (KVS) For single-bin, data-in-memory namespaces, durable deletes may cause a crash on writing replicas or on subsequent restarts. Fixed in version 5.3.0.11.
      • [AER-6390] - (XDR) For strong-consistency namespaces, when DC namespace context configuration item bin-policy is not 'all', shipping records that are unreplicated may miss some bins. Fixed in version 5.3.0.10.
      • [AER-6382] - (LDAP) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 5.3.0.9.
      • [AER-6381] - (XDR) If a record expires between XDR reading and shipping, improper TTL will be shipped. Fixed in version 5.3.0.9.
      • [AER-6376] - (LDAP) 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.3.0.8.
      • [AER-6378] - (ACL) 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.3.0.8.
      • [AER-6366] - (XDR) Dynamically removing a connector seed node may cause a crash. Fixed in version 5.3.0.7.
      • [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.3.0.7.
      • [AER-6365] - (XDR) Reverts behavior change in AER-6240 as empty node addition may reject a lagging last ship time from the acting master, which may result in records not shipping. Fixed in version 5.3.0.6.

  • 5.3.0.3
    Release Date: December 17, 2020
    • 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 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).
    • 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.

    Bug Fixes

    • Enterprise & Community
      • [AER-6351] - (SCAN) When generating sub-transactions for background scans and queries, the record TTL of the parent transaction is ignored.
    • Enterprise Only
      • [AER-6353] - (TLS) If network TLS context configuration items cert-file or key-file point to environment variables, the server will not start.
      • [AER-6350] - (XDR) If a DC is dynamically removed and another added, handling of authentication configuration items may cause a double-free.

    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-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.3.0.25.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.3.0.24.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.3.0.22.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.3.0.20.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.3.0.19.
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory. Fixed in version 5.3.0.16.
      • [AER-6414] - (UDF) For namespaces with data not in memory, UDF replications will not adjust the secondary index. Fixed in version 5.3.0.15.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 5.3.0.11.
      • [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.3.0.11.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 5.3.0.9.
      • [AER-6358] - (KVS) For single-bin, data-in-memory namespaces, unwinding on failing a write operation may incorrectly free the original bin particle. Fixed in version 5.3.0.5.
    • Enterprise Only
      • 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.
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.3.0.24.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.3.0.23.
      • [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.3.0.21.
      • [AER-6427] - (KVS) For data-in-index namespaces, durable deletes will cause an unnecessary assertion on a warm restart. Fixed in version 5.3.0.18.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing. Fixed in version 5.3.0.17.
      • [AER-6413] - (LDAP) Small memory leak during LDAP login process. Fixed in version 5.3.0.14.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.3.0.14.
      • [AER-6404] - (KVS) For single-bin, data-in-memory namespaces, durable deletes may cause a crash on writing replicas or on subsequent restarts. Fixed in version 5.3.0.11.
      • [AER-6390] - (XDR) For strong-consistency namespaces, when DC namespace context configuration item bin-policy is not 'all', shipping records that are unreplicated may miss some bins. Fixed in version 5.3.0.10.
      • [AER-6382] - (LDAP) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 5.3.0.9.
      • [AER-6381] - (XDR) If a record expires between XDR reading and shipping, improper TTL will be shipped. Fixed in version 5.3.0.9.
      • [AER-6376] - (LDAP) 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.3.0.8.
      • [AER-6378] - (ACL) 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.3.0.8.
      • [AER-6366] - (XDR) Dynamically removing a connector seed node may cause a crash. Fixed in version 5.3.0.7.
      • [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.3.0.7.
      • [AER-6365] - (XDR) Reverts behavior change in AER-6240 as empty node addition may reject a lagging last ship time from the acting master, which may result in records not shipping. Fixed in version 5.3.0.6.
      • [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.3.0.5.
      • [AER-6361] - (LDAP) 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.3.0.5.
      • [AER-6356] - (XDR) When DC namespace context configuration item bin-policy is not 'all', locally written bins may not get shipped during recovery. Fixed in version 5.3.0.5.

  • 5.3.0.2
    Release Date: December 10, 2020
    • 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 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).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.

    New Features

    • Enterprise Only
      • [AER-6300] - (XDR) Added expression filtering for XDR.

    Improvements

    • Enterprise & Community
      • [AER-6329] - (BALANCE) Clear irrelevant cluster-related information on non-roster and orphaned nodes.
      • [AER-6296] - (CDT) Added check for duplicate keys in unordered maps.
      • [AER-5852] - (CLUSTERING) tip-clear info command must specify seed as it was configured (DNS name or IP address).
      • [AER-6297] - (CLUSTERING) Added heartbeat context configuration item connect-timeout-ms to enable multi-site clustering with round trip latency more than 100 ms.
      • [AER-6333] - (CLUSTERING) Stop heartbeat on shutdown, to get node kicked out of the cluster in case it was not quiesced and shutdown takes a long time.
      • [AER-6342] - (CLUSTERING) Periodically re-resolve inactive seeds that were configured by DNS name.
      • [AER-6320] - (EXPRESSIONS) Added as_exp_memory_size() operation to use a record's data-in-memory size in expressions.
      • [AER-6344] - (SCAN) Scans now reuse threads from a pool instead of always using fresh system threads.
      • [AER-6345] - (SINDEX) Added storage context configuration item sindex-startup-device-scan to build secondary indexes at startup by scanning devices.
      • [AER-3284] - (STATS) Added object size histograms for storage-engine memory namespaces.
      • [AER-6317] - (UDF) Implemented record.memory_size().
    • Enterprise Only
      • [AER-6349] - (DEPLOYMENT) Added cluster-nodes-limit feature key to restrict cluster size.
      • [AER-6324] - (KVS) Added support for fetching configuration items specified via file path from environment variables.
      • [AER-6337] - (STATS) Included tomb raider device reads and commit-to-device writes in storage benchmark histograms.
      • [AER-6346] - (STATS) Added nodes count in XDR DC stats and log ticker line.
      • [AER-6305] - (XDR) Removed support for 'only-specified' value of DC namespace context configuration item bin-policy.
      • [AER-6319] - (XDR) Added throttling to limit how often SMD saves XDR information to file.
      • [AER-6321] - (XDR) Changed default value of namespace context configuration item xdr-bin-tombstone-ttl to 24 hours.
      • [AER-6328] - (XDR) Added DC context configuration item max-used-service-threads to limit the number of connections to the DC.
      • [AER-6331] - (XDR) When selecting service threads for XDR transactions, ensure all versions of a record ship on the same service thread.

    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-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.3.0.25.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.3.0.24.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.3.0.22.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.3.0.20.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.3.0.19.
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory. Fixed in version 5.3.0.16.
      • [AER-6414] - (UDF) For namespaces with data not in memory, UDF replications will not adjust the secondary index. Fixed in version 5.3.0.15.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 5.3.0.11.
      • [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.3.0.11.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 5.3.0.9.
      • [AER-6358] - (KVS) For single-bin, data-in-memory namespaces, unwinding on failing a write operation may incorrectly free the original bin particle. Fixed in version 5.3.0.5.
    • Enterprise Only
      • 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.
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.3.0.24.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.3.0.23.
      • [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.3.0.21.
      • [AER-6427] - (KVS) For data-in-index namespaces, durable deletes will cause an unnecessary assertion on a warm restart. Fixed in version 5.3.0.18.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing. Fixed in version 5.3.0.17.
      • [AER-6413] - (LDAP) Small memory leak during LDAP login process. Fixed in version 5.3.0.14.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.3.0.14.
      • [AER-6404] - (KVS) For single-bin, data-in-memory namespaces, durable deletes may cause a crash on writing replicas or on subsequent restarts. Fixed in version 5.3.0.11.
      • [AER-6390] - (XDR) For strong-consistency namespaces, when DC namespace context configuration item bin-policy is not 'all', shipping records that are unreplicated may miss some bins. Fixed in version 5.3.0.10.
      • [AER-6382] - (LDAP) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 5.3.0.9.
      • [AER-6381] - (XDR) If a record expires between XDR reading and shipping, improper TTL will be shipped. Fixed in version 5.3.0.9.
      • [AER-6376] - (LDAP) 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.3.0.8.
      • [AER-6378] - (ACL) 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.3.0.8.
      • [AER-6366] - (XDR) Dynamically removing a connector seed node may cause a crash. Fixed in version 5.3.0.7.
      • [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.3.0.7.
      • [AER-6365] - (XDR) Reverts behavior change in AER-6240 as empty node addition may reject a lagging last ship time from the acting master, which may result in records not shipping. Fixed in version 5.3.0.6.
      • [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.3.0.5.
      • [AER-6361] - (LDAP) 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.3.0.5.
      • [AER-6356] - (XDR) When DC namespace context configuration item bin-policy is not 'all', locally written bins may not get shipped during recovery. Fixed in version 5.3.0.5.
      • [AER-6353] - (TLS) If network TLS context configuration items cert-file or key-file point to environment variables, the server will not start. Fixed in version 5.3.0.3.
      • [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.3.0.3.

    Updates

  • 5.2.0.36
    Release Date: September 20, 2021
    • 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).
    • 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.

    Bug Fixes

    • Enterprise & Community
      • [AER-6481] - (KVS) When a service thread exits, its epoll queue's event file descriptor leaks.
      • [AER-6482] - (STORAGE) When a device runs completely out of space, defrag becomes ineffective.
    • Enterprise Only

  • 5.2.0.35
    Release Date: September 15, 2021
    • 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).
    • 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.

    Bug Fixes

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted.

  • 5.2.0.34
    Release Date: September 2, 2021
    • 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).
    • 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.

    Improvements

    • Enterprise & Community
      • [AER-6475] - (GEO) For data-in-memory namespaces, when trimming GeoJSON particles, reallocate into the appropriate namespace arena.

    Bug Fixes

    • Enterprise & Community
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.2.0.35.

  • 5.2.0.33
    Release Date: August 4, 2021
    • 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).
    • 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.

    Bug Fixes

    • Enterprise Only
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.2.0.35.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.2.0.34.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.2.0.34.

  • 5.2.0.32
    Release Date: July 22, 2021
    • 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).
    • 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.

    Bug Fixes

    • Enterprise & Community
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.2.0.35.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.2.0.34.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.2.0.34.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.2.0.33.

  • 5.2.0.31
    Release Date: July 19, 2021
    • 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).
    • 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.

    Bug Fixes

    • 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.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.2.0.35.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.2.0.34.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.2.0.32.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.2.0.34.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.2.0.33.

  • 5.2.0.30
    Release Date: June 24, 2021
    • 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).
    • 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.

    Bug Fixes

    • Enterprise & Community
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.2.0.35.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.2.0.34.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.2.0.32.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.2.0.34.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.2.0.33.
      • [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.2.0.31.

  • 5.2.0.29
    Release Date: May 28, 2021
    • 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).
    • 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.

    Bug Fixes

    • Enterprise & Community
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.2.0.35.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.2.0.34.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.2.0.32.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.2.0.30.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.2.0.34.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.2.0.33.
      • [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.2.0.31.

  • 5.2.0.28
    Release Date: May 25, 2021
    • 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).
    • 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.

    Bug Fixes

    • Enterprise Only
      • [AER-6427] - (KVS) For data-in-index namespaces, durable deletes will cause an unnecessary assertion on a warm restart.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.2.0.35.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.2.0.34.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.2.0.32.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.2.0.30.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.2.0.29.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.2.0.34.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.2.0.33.
      • [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.2.0.31.

  • 5.2.0.27
    Release Date: May 10, 2021
    • 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).
    • 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.

    Bug Fixes

    • Enterprise Only
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.2.0.35.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.2.0.34.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.2.0.32.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.2.0.30.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.2.0.29.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.2.0.34.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.2.0.33.
      • [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.2.0.31.
      • [AER-6427] - (KVS) For data-in-index namespaces, durable deletes will cause an unnecessary assertion on a warm restart. Fixed in version 5.2.0.28.

  • 5.2.0.26
    Release Date: April 6, 2021
    • 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).
    • 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.

    Bug Fixes

    • Enterprise & Community
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.2.0.35.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.2.0.34.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.2.0.32.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.2.0.30.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.2.0.29.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.2.0.34.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.2.0.33.
      • [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.2.0.31.
      • [AER-6427] - (KVS) For data-in-index namespaces, durable deletes will cause an unnecessary assertion on a warm restart. Fixed in version 5.2.0.28.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing. Fixed in version 5.2.0.27.

  • 5.2.0.25
    Release Date: April 2, 2021
    • 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).
    • 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.

    Bug Fixes

    • Enterprise & Community
      • [AER-6414] - (UDF) For namespaces with data not in memory, UDF replications will not adjust the secondary index.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.2.0.35.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.2.0.34.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.2.0.32.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.2.0.30.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.2.0.29.
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory. Fixed in version 5.2.0.26.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.2.0.34.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.2.0.33.
      • [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.2.0.31.
      • [AER-6427] - (KVS) For data-in-index namespaces, durable deletes will cause an unnecessary assertion on a warm restart. Fixed in version 5.2.0.28.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing. Fixed in version 5.2.0.27.

  • 5.2.0.24
    Release Date: March 29, 2021
    • 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).
    • 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.

    Bug Fixes

    • Enterprise & Community
      • [AER-6412] - (QUERY) If a query transaction setup fails in certain ways, improper cleanup may cause a crash.
    • Enterprise Only
      • [AER-6413] - (LDAP) Small memory leak during LDAP login process.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.2.0.35.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.2.0.34.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.2.0.32.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.2.0.30.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.2.0.29.
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory. Fixed in version 5.2.0.26.
      • [AER-6414] - (UDF) For namespaces with data not in memory, UDF replications will not adjust the secondary index. Fixed in version 5.2.0.25.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.2.0.34.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.2.0.33.
      • [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.2.0.31.
      • [AER-6427] - (KVS) For data-in-index namespaces, durable deletes will cause an unnecessary assertion on a warm restart. Fixed in version 5.2.0.28.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing. Fixed in version 5.2.0.27.

  • 5.2.0.21
    Release Date: March 12, 2021
    • 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).
    • 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.

    Bug Fixes

    • Enterprise & Community
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical.
      • [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.
    • Enterprise Only
      • [AER-6404] - (KVS) For single-bin, data-in-memory namespaces, durable deletes may cause a crash on writing replicas or on subsequent restarts.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.2.0.35.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.2.0.34.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.2.0.32.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.2.0.30.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.2.0.29.
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory. Fixed in version 5.2.0.26.
      • [AER-6414] - (UDF) For namespaces with data not in memory, UDF replications will not adjust the secondary index. Fixed in version 5.2.0.25.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.2.0.34.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.2.0.33.
      • [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.2.0.31.
      • [AER-6427] - (KVS) For data-in-index namespaces, durable deletes will cause an unnecessary assertion on a warm restart. Fixed in version 5.2.0.28.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing. Fixed in version 5.2.0.27.
      • [AER-6413] - (LDAP) Small memory leak during LDAP login process. Fixed in version 5.2.0.24.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.2.0.24.

  • 5.2.0.20
    Release Date: February 22, 2021
    • 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).
    • 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.

    Bug Fixes

    • Enterprise Only
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.2.0.35.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.2.0.34.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.2.0.32.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.2.0.30.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.2.0.29.
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory. Fixed in version 5.2.0.26.
      • [AER-6414] - (UDF) For namespaces with data not in memory, UDF replications will not adjust the secondary index. Fixed in version 5.2.0.25.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 5.2.0.21.
      • [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.2.0.21.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.2.0.34.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.2.0.33.
      • [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.2.0.31.
      • [AER-6427] - (KVS) For data-in-index namespaces, durable deletes will cause an unnecessary assertion on a warm restart. Fixed in version 5.2.0.28.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing. Fixed in version 5.2.0.27.
      • [AER-6413] - (LDAP) Small memory leak during LDAP login process. Fixed in version 5.2.0.24.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.2.0.24.
      • [AER-6404] - (KVS) For single-bin, data-in-memory namespaces, durable deletes may cause a crash on writing replicas or on subsequent restarts. Fixed in version 5.2.0.21.

  • 5.2.0.19
    Release Date: February 12, 2021
    • 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).
    • 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.

    Bug Fixes

    • Enterprise Only
      • [AER-6390] - (XDR) For strong-consistency namespaces, when DC namespace context configuration item bin-policy is not 'all', shipping records that are unreplicated may miss some bins.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.2.0.35.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.2.0.34.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.2.0.32.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.2.0.30.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.2.0.29.
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory. Fixed in version 5.2.0.26.
      • [AER-6414] - (UDF) For namespaces with data not in memory, UDF replications will not adjust the secondary index. Fixed in version 5.2.0.25.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 5.2.0.21.
      • [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.2.0.21.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.2.0.34.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.2.0.33.
      • [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.2.0.31.
      • [AER-6427] - (KVS) For data-in-index namespaces, durable deletes will cause an unnecessary assertion on a warm restart. Fixed in version 5.2.0.28.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing. Fixed in version 5.2.0.27.
      • [AER-6413] - (LDAP) Small memory leak during LDAP login process. Fixed in version 5.2.0.24.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.2.0.24.
      • [AER-6404] - (KVS) For single-bin, data-in-memory namespaces, durable deletes may cause a crash on writing replicas or on subsequent restarts. Fixed in version 5.2.0.21.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 5.2.0.20.

  • 5.2.0.18
    Release Date: January 30, 2021
    • 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).
    • 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.

    Bug Fixes

    • Enterprise & Community
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated.
    • Enterprise Only
      • [AER-6382] - (LDAP) When connecting to LDAP server, TLS handshake occasionally fails.
      • [AER-6381] - (XDR) If a record expires between XDR reading and shipping, improper TTL will be shipped.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.2.0.35.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.2.0.34.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.2.0.32.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.2.0.30.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.2.0.29.
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory. Fixed in version 5.2.0.26.
      • [AER-6414] - (UDF) For namespaces with data not in memory, UDF replications will not adjust the secondary index. Fixed in version 5.2.0.25.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 5.2.0.21.
      • [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.2.0.21.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.2.0.34.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.2.0.33.
      • [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.2.0.31.
      • [AER-6427] - (KVS) For data-in-index namespaces, durable deletes will cause an unnecessary assertion on a warm restart. Fixed in version 5.2.0.28.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing. Fixed in version 5.2.0.27.
      • [AER-6413] - (LDAP) Small memory leak during LDAP login process. Fixed in version 5.2.0.24.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.2.0.24.
      • [AER-6404] - (KVS) For single-bin, data-in-memory namespaces, durable deletes may cause a crash on writing replicas or on subsequent restarts. Fixed in version 5.2.0.21.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 5.2.0.20.
      • [AER-6390] - (XDR) For strong-consistency namespaces, when DC namespace context configuration item bin-policy is not 'all', shipping records that are unreplicated may miss some bins. Fixed in version 5.2.0.19.

  • 5.2.0.17
    Release Date: January 25, 2021
    • 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).
    • 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.

    Improvements

    • Enterprise Only
      • [AER-6377] - (XDR) Added service context configuration item downgrading, to enable stripping bin metadata from records sent to older nodes.

    Bug Fixes

    • Enterprise Only
      • [AER-6376] - (LDAP) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library.
      • [AER-6378] - (ACL) 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.

    Known Issues

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.2.0.35.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.2.0.34.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.2.0.32.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.2.0.30.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.2.0.29.
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory. Fixed in version 5.2.0.26.
      • [AER-6414] - (UDF) For namespaces with data not in memory, UDF replications will not adjust the secondary index. Fixed in version 5.2.0.25.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 5.2.0.21.
      • [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.2.0.21.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 5.2.0.18.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.2.0.34.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.2.0.33.
      • [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.2.0.31.
      • [AER-6427] - (KVS) For data-in-index namespaces, durable deletes will cause an unnecessary assertion on a warm restart. Fixed in version 5.2.0.28.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing. Fixed in version 5.2.0.27.
      • [AER-6413] - (LDAP) Small memory leak during LDAP login process. Fixed in version 5.2.0.24.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.2.0.24.
      • [AER-6404] - (KVS) For single-bin, data-in-memory namespaces, durable deletes may cause a crash on writing replicas or on subsequent restarts. Fixed in version 5.2.0.21.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 5.2.0.20.
      • [AER-6390] - (XDR) For strong-consistency namespaces, when DC namespace context configuration item bin-policy is not 'all', shipping records that are unreplicated may miss some bins. Fixed in version 5.2.0.19.
      • [AER-6382] - (LDAP) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 5.2.0.18.
      • [AER-6381] - (XDR) If a record expires between XDR reading and shipping, improper TTL will be shipped. Fixed in version 5.2.0.18.

  • 5.2.0.16
    Release Date: January 15, 2021
    • 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).
    • 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.

    Bug Fixes

    • Enterprise Only
      • [AER-6366] - (XDR) Dynamically removing a connector seed node may cause a crash.
      • [AER-6369] - (XDR) When shipping the first record on a connection, if all bins are filtered out, a crash may result.

    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-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.2.0.35.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.2.0.34.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.2.0.32.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.2.0.30.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.2.0.29.
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory. Fixed in version 5.2.0.26.
      • [AER-6414] - (UDF) For namespaces with data not in memory, UDF replications will not adjust the secondary index. Fixed in version 5.2.0.25.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 5.2.0.21.
      • [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.2.0.21.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 5.2.0.18.
    • Enterprise Only
      • 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.
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.2.0.34.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.2.0.33.
      • [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.2.0.31.
      • [AER-6427] - (KVS) For data-in-index namespaces, durable deletes will cause an unnecessary assertion on a warm restart. Fixed in version 5.2.0.28.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing. Fixed in version 5.2.0.27.
      • [AER-6413] - (LDAP) Small memory leak during LDAP login process. Fixed in version 5.2.0.24.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.2.0.24.
      • [AER-6404] - (KVS) For single-bin, data-in-memory namespaces, durable deletes may cause a crash on writing replicas or on subsequent restarts. Fixed in version 5.2.0.21.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 5.2.0.20.
      • [AER-6390] - (XDR) For strong-consistency namespaces, when DC namespace context configuration item bin-policy is not 'all', shipping records that are unreplicated may miss some bins. Fixed in version 5.2.0.19.
      • [AER-6382] - (LDAP) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 5.2.0.18.
      • [AER-6381] - (XDR) If a record expires between XDR reading and shipping, improper TTL will be shipped. Fixed in version 5.2.0.18.
      • [AER-6376] - (LDAP) 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.2.0.17.
      • [AER-6378] - (ACL) 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.2.0.17.

  • 5.2.0.15
    Release Date: January 7, 2021
    • 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).
    • 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.

    Bug Fixes

    • Enterprise Only
      • [AER-6365] - (XDR) Reverts behavior change in AER-6240 as empty node addition may reject a lagging last ship time from the acting master, which may result in records not shipping.

    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-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.2.0.35.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.2.0.34.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.2.0.32.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.2.0.30.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.2.0.29.
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory. Fixed in version 5.2.0.26.
      • [AER-6414] - (UDF) For namespaces with data not in memory, UDF replications will not adjust the secondary index. Fixed in version 5.2.0.25.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 5.2.0.21.
      • [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.2.0.21.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 5.2.0.18.
    • Enterprise Only
      • 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.
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.2.0.34.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.2.0.33.
      • [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.2.0.31.
      • [AER-6427] - (KVS) For data-in-index namespaces, durable deletes will cause an unnecessary assertion on a warm restart. Fixed in version 5.2.0.28.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing. Fixed in version 5.2.0.27.
      • [AER-6413] - (LDAP) Small memory leak during LDAP login process. Fixed in version 5.2.0.24.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.2.0.24.
      • [AER-6404] - (KVS) For single-bin, data-in-memory namespaces, durable deletes may cause a crash on writing replicas or on subsequent restarts. Fixed in version 5.2.0.21.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 5.2.0.20.
      • [AER-6390] - (XDR) For strong-consistency namespaces, when DC namespace context configuration item bin-policy is not 'all', shipping records that are unreplicated may miss some bins. Fixed in version 5.2.0.19.
      • [AER-6382] - (LDAP) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 5.2.0.18.
      • [AER-6381] - (XDR) If a record expires between XDR reading and shipping, improper TTL will be shipped. Fixed in version 5.2.0.18.
      • [AER-6376] - (LDAP) 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.2.0.17.
      • [AER-6378] - (ACL) 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.2.0.17.
      • [AER-6366] - (XDR) Dynamically removing a connector seed node may cause a crash. Fixed in version 5.2.0.16.
      • [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.2.0.16.

  • 5.2.0.14
    Release Date: January 4, 2021
    • 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).
    • 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.

    Improvements

    • Enterprise & Community
      • [AER-6357] - (KVS) Handle exceeding the OS file descriptor limit gracefully, without asserting.

    Bug Fixes

    • Enterprise & Community
      • [AER-6358] - (KVS) For single-bin, data-in-memory namespaces, unwinding on failing a write operation may incorrectly free the original bin particle.
    • Enterprise Only
      • [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.
      • [AER-6361] - (LDAP) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item.
      • [AER-6356] - (XDR) When DC namespace context configuration item bin-policy is not 'all', locally written bins may not get shipped during recovery.

    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-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.2.0.35.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.2.0.34.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.2.0.32.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.2.0.30.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.2.0.29.
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory. Fixed in version 5.2.0.26.
      • [AER-6414] - (UDF) For namespaces with data not in memory, UDF replications will not adjust the secondary index. Fixed in version 5.2.0.25.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 5.2.0.21.
      • [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.2.0.21.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 5.2.0.18.
    • Enterprise Only
      • 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.
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.2.0.34.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.2.0.33.
      • [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.2.0.31.
      • [AER-6427] - (KVS) For data-in-index namespaces, durable deletes will cause an unnecessary assertion on a warm restart. Fixed in version 5.2.0.28.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing. Fixed in version 5.2.0.27.
      • [AER-6413] - (LDAP) Small memory leak during LDAP login process. Fixed in version 5.2.0.24.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.2.0.24.
      • [AER-6404] - (KVS) For single-bin, data-in-memory namespaces, durable deletes may cause a crash on writing replicas or on subsequent restarts. Fixed in version 5.2.0.21.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 5.2.0.20.
      • [AER-6390] - (XDR) For strong-consistency namespaces, when DC namespace context configuration item bin-policy is not 'all', shipping records that are unreplicated may miss some bins. Fixed in version 5.2.0.19.
      • [AER-6382] - (LDAP) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 5.2.0.18.
      • [AER-6381] - (XDR) If a record expires between XDR reading and shipping, improper TTL will be shipped. Fixed in version 5.2.0.18.
      • [AER-6376] - (LDAP) 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.2.0.17.
      • [AER-6378] - (ACL) 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.2.0.17.
      • [AER-6366] - (XDR) Dynamically removing a connector seed node may cause a crash. Fixed in version 5.2.0.16.
      • [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.2.0.16.
      • [AER-6365] - (XDR) Reverts behavior change in AER-6240 as empty node addition may reject a lagging last ship time from the acting master, which may result in records not shipping. Fixed in version 5.2.0.15.

  • 5.2.0.12
    Release Date: December 17, 2020
    • 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).
    • 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.

    Bug Fixes

    • Enterprise & Community
      • [AER-6351] - (SCAN) When generating sub-transactions for background scans and queries, the record TTL of the parent transaction is ignored.
    • Enterprise Only
      • [AER-6350] - (XDR) If a DC is dynamically removed and another added, handling of authentication configuration items may cause a double-free.

    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-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.2.0.35.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.2.0.34.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.2.0.32.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.2.0.30.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.2.0.29.
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory. Fixed in version 5.2.0.26.
      • [AER-6414] - (UDF) For namespaces with data not in memory, UDF replications will not adjust the secondary index. Fixed in version 5.2.0.25.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 5.2.0.21.
      • [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.2.0.21.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 5.2.0.18.
      • [AER-6358] - (KVS) For single-bin, data-in-memory namespaces, unwinding on failing a write operation may incorrectly free the original bin particle. Fixed in version 5.2.0.14.
    • Enterprise Only
      • 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.
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.2.0.34.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.2.0.33.
      • [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.2.0.31.
      • [AER-6427] - (KVS) For data-in-index namespaces, durable deletes will cause an unnecessary assertion on a warm restart. Fixed in version 5.2.0.28.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing. Fixed in version 5.2.0.27.
      • [AER-6413] - (LDAP) Small memory leak during LDAP login process. Fixed in version 5.2.0.24.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.2.0.24.
      • [AER-6404] - (KVS) For single-bin, data-in-memory namespaces, durable deletes may cause a crash on writing replicas or on subsequent restarts. Fixed in version 5.2.0.21.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 5.2.0.20.
      • [AER-6390] - (XDR) For strong-consistency namespaces, when DC namespace context configuration item bin-policy is not 'all', shipping records that are unreplicated may miss some bins. Fixed in version 5.2.0.19.
      • [AER-6382] - (LDAP) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 5.2.0.18.
      • [AER-6381] - (XDR) If a record expires between XDR reading and shipping, improper TTL will be shipped. Fixed in version 5.2.0.18.
      • [AER-6376] - (LDAP) 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.2.0.17.
      • [AER-6378] - (ACL) 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.2.0.17.
      • [AER-6366] - (XDR) Dynamically removing a connector seed node may cause a crash. Fixed in version 5.2.0.16.
      • [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.2.0.16.
      • [AER-6365] - (XDR) Reverts behavior change in AER-6240 as empty node addition may reject a lagging last ship time from the acting master, which may result in records not shipping. Fixed in version 5.2.0.15.
      • [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.2.0.14.
      • [AER-6361] - (LDAP) 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.2.0.14.
      • [AER-6356] - (XDR) When DC namespace context configuration item bin-policy is not 'all', locally written bins may not get shipped during recovery. Fixed in version 5.2.0.14.

  • 5.2.0.11
    Release Date: December 4, 2020
    • 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).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.

    Bug Fixes

    • Enterprise & Community
      • [AER-6343] - (UDF) In single-bin namespaces, UDFs cannot read or write bin values.
    • Enterprise Only
      • [AER-6341] - (XDR) Source node may fail to discover the entire destination cluster when destination nodes restart.

    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-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.2.0.35.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.2.0.34.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.2.0.32.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.2.0.30.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.2.0.29.
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory. Fixed in version 5.2.0.26.
      • [AER-6414] - (UDF) For namespaces with data not in memory, UDF replications will not adjust the secondary index. Fixed in version 5.2.0.25.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 5.2.0.21.
      • [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.2.0.21.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 5.2.0.18.
      • [AER-6358] - (KVS) For single-bin, data-in-memory namespaces, unwinding on failing a write operation may incorrectly free the original bin particle. Fixed in version 5.2.0.14.
    • Enterprise Only
      • 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.
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.2.0.34.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.2.0.33.
      • [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.2.0.31.
      • [AER-6427] - (KVS) For data-in-index namespaces, durable deletes will cause an unnecessary assertion on a warm restart. Fixed in version 5.2.0.28.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing. Fixed in version 5.2.0.27.
      • [AER-6413] - (LDAP) Small memory leak during LDAP login process. Fixed in version 5.2.0.24.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.2.0.24.
      • [AER-6404] - (KVS) For single-bin, data-in-memory namespaces, durable deletes may cause a crash on writing replicas or on subsequent restarts. Fixed in version 5.2.0.21.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 5.2.0.20.
      • [AER-6390] - (XDR) For strong-consistency namespaces, when DC namespace context configuration item bin-policy is not 'all', shipping records that are unreplicated may miss some bins. Fixed in version 5.2.0.19.
      • [AER-6382] - (LDAP) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 5.2.0.18.
      • [AER-6381] - (XDR) If a record expires between XDR reading and shipping, improper TTL will be shipped. Fixed in version 5.2.0.18.
      • [AER-6376] - (LDAP) 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.2.0.17.
      • [AER-6378] - (ACL) 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.2.0.17.
      • [AER-6366] - (XDR) Dynamically removing a connector seed node may cause a crash. Fixed in version 5.2.0.16.
      • [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.2.0.16.
      • [AER-6365] - (XDR) Reverts behavior change in AER-6240 as empty node addition may reject a lagging last ship time from the acting master, which may result in records not shipping. Fixed in version 5.2.0.15.
      • [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.2.0.14.
      • [AER-6361] - (LDAP) 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.2.0.14.
      • [AER-6356] - (XDR) When DC namespace context configuration item bin-policy is not 'all', locally written bins may not get shipped during recovery. Fixed in version 5.2.0.14.
      • [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.2.0.12.

  • 5.2.0.10
    Release Date: November 25, 2020
    • 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).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.

    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-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.2.0.35.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.2.0.34.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.2.0.32.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.2.0.30.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.2.0.29.
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory. Fixed in version 5.2.0.26.
      • [AER-6414] - (UDF) For namespaces with data not in memory, UDF replications will not adjust the secondary index. Fixed in version 5.2.0.25.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 5.2.0.21.
      • [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.2.0.21.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 5.2.0.18.
      • [AER-6358] - (KVS) For single-bin, data-in-memory namespaces, unwinding on failing a write operation may incorrectly free the original bin particle. Fixed in version 5.2.0.14.
      • [AER-6343] - (UDF) In single-bin namespaces, UDFs cannot read or write bin values. Fixed in version 5.2.0.11.
    • Enterprise Only
      • 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.
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.2.0.34.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.2.0.33.
      • [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.2.0.31.
      • [AER-6427] - (KVS) For data-in-index namespaces, durable deletes will cause an unnecessary assertion on a warm restart. Fixed in version 5.2.0.28.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing. Fixed in version 5.2.0.27.
      • [AER-6413] - (LDAP) Small memory leak during LDAP login process. Fixed in version 5.2.0.24.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.2.0.24.
      • [AER-6404] - (KVS) For single-bin, data-in-memory namespaces, durable deletes may cause a crash on writing replicas or on subsequent restarts. Fixed in version 5.2.0.21.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 5.2.0.20.
      • [AER-6390] - (XDR) For strong-consistency namespaces, when DC namespace context configuration item bin-policy is not 'all', shipping records that are unreplicated may miss some bins. Fixed in version 5.2.0.19.
      • [AER-6382] - (LDAP) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 5.2.0.18.
      • [AER-6381] - (XDR) If a record expires between XDR reading and shipping, improper TTL will be shipped. Fixed in version 5.2.0.18.
      • [AER-6376] - (LDAP) 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.2.0.17.
      • [AER-6378] - (ACL) 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.2.0.17.
      • [AER-6366] - (XDR) Dynamically removing a connector seed node may cause a crash. Fixed in version 5.2.0.16.
      • [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.2.0.16.
      • [AER-6365] - (XDR) Reverts behavior change in AER-6240 as empty node addition may reject a lagging last ship time from the acting master, which may result in records not shipping. Fixed in version 5.2.0.15.
      • [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.2.0.14.
      • [AER-6361] - (LDAP) 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.2.0.14.
      • [AER-6356] - (XDR) When DC namespace context configuration item bin-policy is not 'all', locally written bins may not get shipped during recovery. Fixed in version 5.2.0.14.
      • [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.2.0.12.
      • [AER-6341] - (XDR) Source node may fail to discover the entire destination cluster when destination nodes restart. Fixed in version 5.2.0.11.

  • 5.2.0.9
    Release Date: November 19, 2020
    • 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).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.

    Bug Fixes

    • Enterprise & Community
      • [AER-6330] - (KVS) Invalid HLL element list parameter may cause a crash.
      • [AER-6332] - (KVS) An HLL union operation on an existing bin will overflow the stack.
      • [AER-6334] - (EXPRESSIONS) A map value (as opposed to a map bin) in a compare expression results in an improper error.
      • [AER-6336] - (BATCH) If both filters and bin selection are used in a batch request, proxied sub-transactions are malformed and will fail.

    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-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.2.0.35.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.2.0.34.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.2.0.32.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.2.0.30.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.2.0.29.
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory. Fixed in version 5.2.0.26.
      • [AER-6414] - (UDF) For namespaces with data not in memory, UDF replications will not adjust the secondary index. Fixed in version 5.2.0.25.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 5.2.0.21.
      • [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.2.0.21.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 5.2.0.18.
      • [AER-6358] - (KVS) For single-bin, data-in-memory namespaces, unwinding on failing a write operation may incorrectly free the original bin particle. Fixed in version 5.2.0.14.
      • [AER-6343] - (UDF) In single-bin namespaces, UDFs cannot read or write bin values. Fixed in version 5.2.0.11.
      • [AER-6339] - (KVS) On certain bitwise blob operations (and, or, xor), an out of bounds byte may be accessed and cause a crash. Fixed in version 5.2.0.10.
    • Enterprise Only
      • 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.
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.2.0.34.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.2.0.33.
      • [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.2.0.31.
      • [AER-6427] - (KVS) For data-in-index namespaces, durable deletes will cause an unnecessary assertion on a warm restart. Fixed in version 5.2.0.28.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing. Fixed in version 5.2.0.27.
      • [AER-6413] - (LDAP) Small memory leak during LDAP login process. Fixed in version 5.2.0.24.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.2.0.24.
      • [AER-6404] - (KVS) For single-bin, data-in-memory namespaces, durable deletes may cause a crash on writing replicas or on subsequent restarts. Fixed in version 5.2.0.21.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 5.2.0.20.
      • [AER-6390] - (XDR) For strong-consistency namespaces, when DC namespace context configuration item bin-policy is not 'all', shipping records that are unreplicated may miss some bins. Fixed in version 5.2.0.19.
      • [AER-6382] - (LDAP) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 5.2.0.18.
      • [AER-6381] - (XDR) If a record expires between XDR reading and shipping, improper TTL will be shipped. Fixed in version 5.2.0.18.
      • [AER-6376] - (LDAP) 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.2.0.17.
      • [AER-6378] - (ACL) 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.2.0.17.
      • [AER-6366] - (XDR) Dynamically removing a connector seed node may cause a crash. Fixed in version 5.2.0.16.
      • [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.2.0.16.
      • [AER-6365] - (XDR) Reverts behavior change in AER-6240 as empty node addition may reject a lagging last ship time from the acting master, which may result in records not shipping. Fixed in version 5.2.0.15.
      • [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.2.0.14.
      • [AER-6361] - (LDAP) 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.2.0.14.
      • [AER-6356] - (XDR) When DC namespace context configuration item bin-policy is not 'all', locally written bins may not get shipped during recovery. Fixed in version 5.2.0.14.
      • [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.2.0.12.
      • [AER-6341] - (XDR) Source node may fail to discover the entire destination cluster when destination nodes restart. Fixed in version 5.2.0.11.

  • 5.2.0.7
    Release Date: November 10, 2020
    • 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).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.

    Bug Fixes

    • Enterprise & Community
      • [AER-6326] - (KVS) When Aerospike runs as the init process (e.g. in some container scenarios), signals do not stop Aerospike as intended.
    • Enterprise Only
      • [AER-6327] - (TLS) When refreshing certificates, older chained certificates are not cleared.
      • [AER-6325] - (XDR) DCs with connector true do not properly disconnect when all namespaces are dynamically removed.

    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-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.2.0.35.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.2.0.34.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.2.0.32.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.2.0.30.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.2.0.29.
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory. Fixed in version 5.2.0.26.
      • [AER-6414] - (UDF) For namespaces with data not in memory, UDF replications will not adjust the secondary index. Fixed in version 5.2.0.25.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 5.2.0.21.
      • [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.2.0.21.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 5.2.0.18.
      • [AER-6358] - (KVS) For single-bin, data-in-memory namespaces, unwinding on failing a write operation may incorrectly free the original bin particle. Fixed in version 5.2.0.14.
      • [AER-6343] - (UDF) In single-bin namespaces, UDFs cannot read or write bin values. Fixed in version 5.2.0.11.
      • [AER-6339] - (KVS) On certain bitwise blob operations (and, or, xor), an out of bounds byte may be accessed and cause a crash. Fixed in version 5.2.0.10.
      • [AER-6330] - (KVS) Invalid HLL element list parameter may cause a crash. Fixed in version 5.2.0.9.
      • [AER-6332] - (KVS) An HLL union operation on an existing bin will overflow the stack. Fixed in version 5.2.0.9.
      • [AER-6334] - (EXPRESSIONS) A map value (as opposed to a map bin) in a compare expression results in an improper error. Fixed in version 5.2.0.9.
      • [AER-6336] - (BATCH) If both filters and bin selection are used in a batch request, proxied sub-transactions are malformed and will fail. Fixed in version 5.2.0.9.
    • Enterprise Only
      • 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.
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.2.0.34.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.2.0.33.
      • [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.2.0.31.
      • [AER-6427] - (KVS) For data-in-index namespaces, durable deletes will cause an unnecessary assertion on a warm restart. Fixed in version 5.2.0.28.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing. Fixed in version 5.2.0.27.
      • [AER-6413] - (LDAP) Small memory leak during LDAP login process. Fixed in version 5.2.0.24.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.2.0.24.
      • [AER-6404] - (KVS) For single-bin, data-in-memory namespaces, durable deletes may cause a crash on writing replicas or on subsequent restarts. Fixed in version 5.2.0.21.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 5.2.0.20.
      • [AER-6390] - (XDR) For strong-consistency namespaces, when DC namespace context configuration item bin-policy is not 'all', shipping records that are unreplicated may miss some bins. Fixed in version 5.2.0.19.
      • [AER-6382] - (LDAP) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 5.2.0.18.
      • [AER-6381] - (XDR) If a record expires between XDR reading and shipping, improper TTL will be shipped. Fixed in version 5.2.0.18.
      • [AER-6376] - (LDAP) 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.2.0.17.
      • [AER-6378] - (ACL) 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.2.0.17.
      • [AER-6366] - (XDR) Dynamically removing a connector seed node may cause a crash. Fixed in version 5.2.0.16.
      • [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.2.0.16.
      • [AER-6365] - (XDR) Reverts behavior change in AER-6240 as empty node addition may reject a lagging last ship time from the acting master, which may result in records not shipping. Fixed in version 5.2.0.15.
      • [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.2.0.14.
      • [AER-6361] - (LDAP) 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.2.0.14.
      • [AER-6356] - (XDR) When DC namespace context configuration item bin-policy is not 'all', locally written bins may not get shipped during recovery. Fixed in version 5.2.0.14.
      • [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.2.0.12.
      • [AER-6341] - (XDR) Source node may fail to discover the entire destination cluster when destination nodes restart. Fixed in version 5.2.0.11.

  • 5.2.0.6
    Release Date: October 31, 2020
    • 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).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.

    Improvements

    • Enterprise & Community
      • [AER-6323] - (KVS) With debug-allocations enabled, adjust every logged site address for easier association with source code.

    Bug Fixes

    • Enterprise & Community
    • Enterprise Only
      • [AER-6322] - (XDR) When TLS handshake fails or times out, security authentication request buffer may be double freed, which may 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-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.2.0.35.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.2.0.34.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.2.0.32.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.2.0.30.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.2.0.29.
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory. Fixed in version 5.2.0.26.
      • [AER-6414] - (UDF) For namespaces with data not in memory, UDF replications will not adjust the secondary index. Fixed in version 5.2.0.25.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 5.2.0.21.
      • [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.2.0.21.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 5.2.0.18.
      • [AER-6358] - (KVS) For single-bin, data-in-memory namespaces, unwinding on failing a write operation may incorrectly free the original bin particle. Fixed in version 5.2.0.14.
      • [AER-6343] - (UDF) In single-bin namespaces, UDFs cannot read or write bin values. Fixed in version 5.2.0.11.
      • [AER-6339] - (KVS) On certain bitwise blob operations (and, or, xor), an out of bounds byte may be accessed and cause a crash. Fixed in version 5.2.0.10.
      • [AER-6330] - (KVS) Invalid HLL element list parameter may cause a crash. Fixed in version 5.2.0.9.
      • [AER-6332] - (KVS) An HLL union operation on an existing bin will overflow the stack. Fixed in version 5.2.0.9.
      • [AER-6334] - (EXPRESSIONS) A map value (as opposed to a map bin) in a compare expression results in an improper error. Fixed in version 5.2.0.9.
      • [AER-6336] - (BATCH) If both filters and bin selection are used in a batch request, proxied sub-transactions are malformed and will fail. Fixed in version 5.2.0.9.
      • [AER-6326] - (KVS) When Aerospike runs as the init process (e.g. in some container scenarios), signals do not stop Aerospike as intended. Fixed in version 5.2.0.7.
    • Enterprise Only
      • 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.
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.2.0.34.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.2.0.33.
      • [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.2.0.31.
      • [AER-6427] - (KVS) For data-in-index namespaces, durable deletes will cause an unnecessary assertion on a warm restart. Fixed in version 5.2.0.28.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing. Fixed in version 5.2.0.27.
      • [AER-6413] - (LDAP) Small memory leak during LDAP login process. Fixed in version 5.2.0.24.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.2.0.24.
      • [AER-6404] - (KVS) For single-bin, data-in-memory namespaces, durable deletes may cause a crash on writing replicas or on subsequent restarts. Fixed in version 5.2.0.21.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 5.2.0.20.
      • [AER-6390] - (XDR) For strong-consistency namespaces, when DC namespace context configuration item bin-policy is not 'all', shipping records that are unreplicated may miss some bins. Fixed in version 5.2.0.19.
      • [AER-6382] - (LDAP) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 5.2.0.18.
      • [AER-6381] - (XDR) If a record expires between XDR reading and shipping, improper TTL will be shipped. Fixed in version 5.2.0.18.
      • [AER-6376] - (LDAP) 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.2.0.17.
      • [AER-6378] - (ACL) 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.2.0.17.
      • [AER-6366] - (XDR) Dynamically removing a connector seed node may cause a crash. Fixed in version 5.2.0.16.
      • [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.2.0.16.
      • [AER-6365] - (XDR) Reverts behavior change in AER-6240 as empty node addition may reject a lagging last ship time from the acting master, which may result in records not shipping. Fixed in version 5.2.0.15.
      • [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.2.0.14.
      • [AER-6361] - (LDAP) 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.2.0.14.
      • [AER-6356] - (XDR) When DC namespace context configuration item bin-policy is not 'all', locally written bins may not get shipped during recovery. Fixed in version 5.2.0.14.
      • [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.2.0.12.
      • [AER-6341] - (XDR) Source node may fail to discover the entire destination cluster when destination nodes restart. Fixed in version 5.2.0.11.
      • [AER-6327] - (TLS) When refreshing certificates, older chained certificates are not cleared. Fixed in version 5.2.0.7.
      • [AER-6325] - (XDR) DCs with connector true do not properly disconnect when all namespaces are dynamically removed. Fixed in version 5.2.0.7.

  • 5.2.0.5
    Release Date: October 21, 2020
    • 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).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.

    Improvements

    • Enterprise & Community
      • [AER-6311] - (SCAN) Do not start more threads for a scan than there are partitions requested.
      • [AER-6312] - (SECONDARY INDEX) When populating secondary indexes at startup, only read records in sets which have indexes.
    • Community Only
      • [AER-6314] - (PACKAGING) Removed Python dependency in Debian Community Edition builds.

    Bug Fixes

    • Enterprise & Community
      • [AER-6316] - (EXPRESSIONS) Expressions may erroneously compare different blob types sent from the client.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range.
    • Enterprise Only
      • [AER-6313] - (XDR) Small memory leak when XDR client connects to seed node.

    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-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.2.0.35.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.2.0.34.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.2.0.32.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.2.0.30.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.2.0.29.
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory. Fixed in version 5.2.0.26.
      • [AER-6414] - (UDF) For namespaces with data not in memory, UDF replications will not adjust the secondary index. Fixed in version 5.2.0.25.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 5.2.0.21.
      • [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.2.0.21.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 5.2.0.18.
      • [AER-6358] - (KVS) For single-bin, data-in-memory namespaces, unwinding on failing a write operation may incorrectly free the original bin particle. Fixed in version 5.2.0.14.
      • [AER-6343] - (UDF) In single-bin namespaces, UDFs cannot read or write bin values. Fixed in version 5.2.0.11.
      • [AER-6339] - (KVS) On certain bitwise blob operations (and, or, xor), an out of bounds byte may be accessed and cause a crash. Fixed in version 5.2.0.10.
      • [AER-6330] - (KVS) Invalid HLL element list parameter may cause a crash. Fixed in version 5.2.0.9.
      • [AER-6332] - (KVS) An HLL union operation on an existing bin will overflow the stack. Fixed in version 5.2.0.9.
      • [AER-6334] - (EXPRESSIONS) A map value (as opposed to a map bin) in a compare expression results in an improper error. Fixed in version 5.2.0.9.
      • [AER-6336] - (BATCH) If both filters and bin selection are used in a batch request, proxied sub-transactions are malformed and will fail. Fixed in version 5.2.0.9.
      • [AER-6326] - (KVS) When Aerospike runs as the init process (e.g. in some container scenarios), signals do not stop Aerospike as intended. Fixed in version 5.2.0.7.
      • [AER-6318] - (EXPRESSIONS) The as_exp_hll_may_contain() operation returns an improper result. Fixed in version 5.2.0.6.
    • Enterprise Only
      • 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.
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.2.0.34.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.2.0.33.
      • [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.2.0.31.
      • [AER-6427] - (KVS) For data-in-index namespaces, durable deletes will cause an unnecessary assertion on a warm restart. Fixed in version 5.2.0.28.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing. Fixed in version 5.2.0.27.
      • [AER-6413] - (LDAP) Small memory leak during LDAP login process. Fixed in version 5.2.0.24.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.2.0.24.
      • [AER-6404] - (KVS) For single-bin, data-in-memory namespaces, durable deletes may cause a crash on writing replicas or on subsequent restarts. Fixed in version 5.2.0.21.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 5.2.0.20.
      • [AER-6390] - (XDR) For strong-consistency namespaces, when DC namespace context configuration item bin-policy is not 'all', shipping records that are unreplicated may miss some bins. Fixed in version 5.2.0.19.
      • [AER-6382] - (LDAP) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 5.2.0.18.
      • [AER-6381] - (XDR) If a record expires between XDR reading and shipping, improper TTL will be shipped. Fixed in version 5.2.0.18.
      • [AER-6376] - (LDAP) 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.2.0.17.
      • [AER-6378] - (ACL) 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.2.0.17.
      • [AER-6366] - (XDR) Dynamically removing a connector seed node may cause a crash. Fixed in version 5.2.0.16.
      • [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.2.0.16.
      • [AER-6365] - (XDR) Reverts behavior change in AER-6240 as empty node addition may reject a lagging last ship time from the acting master, which may result in records not shipping. Fixed in version 5.2.0.15.
      • [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.2.0.14.
      • [AER-6361] - (LDAP) 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.2.0.14.
      • [AER-6356] - (XDR) When DC namespace context configuration item bin-policy is not 'all', locally written bins may not get shipped during recovery. Fixed in version 5.2.0.14.
      • [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.2.0.12.
      • [AER-6341] - (XDR) Source node may fail to discover the entire destination cluster when destination nodes restart. Fixed in version 5.2.0.11.
      • [AER-6327] - (TLS) When refreshing certificates, older chained certificates are not cleared. Fixed in version 5.2.0.7.
      • [AER-6325] - (XDR) DCs with connector true do not properly disconnect when all namespaces are dynamically removed. Fixed in version 5.2.0.7.
      • [AER-6322] - (XDR) When TLS handshake fails or times out, security authentication request buffer may be double freed, which may cause a crash. Fixed in version 5.2.0.6.

  • 5.2.0.4
    Release Date: October 14, 2020
    • 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).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.

    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

    • 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-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.2.0.35.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.2.0.34.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.2.0.32.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.2.0.30.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.2.0.29.
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory. Fixed in version 5.2.0.26.
      • [AER-6414] - (UDF) For namespaces with data not in memory, UDF replications will not adjust the secondary index. Fixed in version 5.2.0.25.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 5.2.0.21.
      • [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.2.0.21.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 5.2.0.18.
      • [AER-6358] - (KVS) For single-bin, data-in-memory namespaces, unwinding on failing a write operation may incorrectly free the original bin particle. Fixed in version 5.2.0.14.
      • [AER-6343] - (UDF) In single-bin namespaces, UDFs cannot read or write bin values. Fixed in version 5.2.0.11.
      • [AER-6339] - (KVS) On certain bitwise blob operations (and, or, xor), an out of bounds byte may be accessed and cause a crash. Fixed in version 5.2.0.10.
      • [AER-6330] - (KVS) Invalid HLL element list parameter may cause a crash. Fixed in version 5.2.0.9.
      • [AER-6332] - (KVS) An HLL union operation on an existing bin will overflow the stack. Fixed in version 5.2.0.9.
      • [AER-6334] - (EXPRESSIONS) A map value (as opposed to a map bin) in a compare expression results in an improper error. Fixed in version 5.2.0.9.
      • [AER-6336] - (BATCH) If both filters and bin selection are used in a batch request, proxied sub-transactions are malformed and will fail. Fixed in version 5.2.0.9.
      • [AER-6326] - (KVS) When Aerospike runs as the init process (e.g. in some container scenarios), signals do not stop Aerospike as intended. Fixed in version 5.2.0.7.
      • [AER-6318] - (EXPRESSIONS) The as_exp_hll_may_contain() operation returns an improper result. Fixed in version 5.2.0.6.
      • [AER-6316] - (EXPRESSIONS) Expressions may erroneously compare different blob types sent from the client. Fixed in version 5.2.0.5.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 5.2.0.5.
    • Enterprise Only
      • 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.
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.2.0.34.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.2.0.33.
      • [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.2.0.31.
      • [AER-6427] - (KVS) For data-in-index namespaces, durable deletes will cause an unnecessary assertion on a warm restart. Fixed in version 5.2.0.28.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing. Fixed in version 5.2.0.27.
      • [AER-6413] - (LDAP) Small memory leak during LDAP login process. Fixed in version 5.2.0.24.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.2.0.24.
      • [AER-6404] - (KVS) For single-bin, data-in-memory namespaces, durable deletes may cause a crash on writing replicas or on subsequent restarts. Fixed in version 5.2.0.21.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 5.2.0.20.
      • [AER-6390] - (XDR) For strong-consistency namespaces, when DC namespace context configuration item bin-policy is not 'all', shipping records that are unreplicated may miss some bins. Fixed in version 5.2.0.19.
      • [AER-6382] - (LDAP) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 5.2.0.18.
      • [AER-6381] - (XDR) If a record expires between XDR reading and shipping, improper TTL will be shipped. Fixed in version 5.2.0.18.
      • [AER-6376] - (LDAP) 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.2.0.17.
      • [AER-6378] - (ACL) 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.2.0.17.
      • [AER-6366] - (XDR) Dynamically removing a connector seed node may cause a crash. Fixed in version 5.2.0.16.
      • [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.2.0.16.
      • [AER-6365] - (XDR) Reverts behavior change in AER-6240 as empty node addition may reject a lagging last ship time from the acting master, which may result in records not shipping. Fixed in version 5.2.0.15.
      • [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.2.0.14.
      • [AER-6361] - (LDAP) 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.2.0.14.
      • [AER-6356] - (XDR) When DC namespace context configuration item bin-policy is not 'all', locally written bins may not get shipped during recovery. Fixed in version 5.2.0.14.
      • [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.2.0.12.
      • [AER-6341] - (XDR) Source node may fail to discover the entire destination cluster when destination nodes restart. Fixed in version 5.2.0.11.
      • [AER-6327] - (TLS) When refreshing certificates, older chained certificates are not cleared. Fixed in version 5.2.0.7.
      • [AER-6325] - (XDR) DCs with connector true do not properly disconnect when all namespaces are dynamically removed. Fixed in version 5.2.0.7.
      • [AER-6322] - (XDR) When TLS handshake fails or times out, security authentication request buffer may be double freed, which may cause a crash. Fixed in version 5.2.0.6.
      • [AER-6313] - (XDR) Small memory leak when XDR client connects to seed node. Fixed in version 5.2.0.5.

  • 5.2.0.2
    Release Date: October 1, 2020
    • 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).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.

    New Features

    • Enterprise & Community
      • [AER-6292] - (EXPRESSIONS) Redesigned predicate expressions, expanding their scope and capabilities.
    • Enterprise Only
      • [AER-6272] - (XDR) Added DC namespace context configuration item bin-policy to determine which bins to ship.

    Improvements

    • Enterprise & Community
      • [AER-6291] - (LOGGING) Changed warning to detail level on failure to write to storage, and changed 'out of space' warning to ticker warning.
      • [AER-6283] - (SINDEX) For namespaces with data-in-memory true, adjust secondary indexes when records expire or are evicted.
      • [AER-6285] - (QUERY) Use bin IDs instead of names internally for scans and queries with bin selection, to improve performance.
      • [AER-5487] - (STATS) Added device_data_bytes statistic for sets.
      • [AER-6282] - (STATS) Removed latency info command.
      • [AER-6277] - (UDF) Implemented record.device_size().
      • [AER-6279] - (UDF) Only load records from storage if necessary (speeds up metadata-only read-only UDFs).
      • [AER-6293] - (UDF) Explicitly forbid record UDF policies that were previously ignored.
    • Enterprise Only
      • [AER-6280] - (BALANCE) Added service context configuration item stay-quiesced.
      • [AER-6274] - (MIGRATION) Added namespace context configuration item ignore-migrate-fill-delay.
      • [AER-6281] - (UDF) Validate a UDF transaction's durable-delete flag for UDFs that delete the record.
      • [AER-6273] - (XDR) Added DC namespace context configuration item remote-namespace to ship a local namespace to a different remote namespace.

    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-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.2.0.35.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.2.0.34.
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash. Fixed in version 5.2.0.32.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.2.0.30.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.2.0.29.
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory. Fixed in version 5.2.0.26.
      • [AER-6414] - (UDF) For namespaces with data not in memory, UDF replications will not adjust the secondary index. Fixed in version 5.2.0.25.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 5.2.0.21.
      • [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.2.0.21.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 5.2.0.18.
      • [AER-6358] - (KVS) For single-bin, data-in-memory namespaces, unwinding on failing a write operation may incorrectly free the original bin particle. Fixed in version 5.2.0.14.
      • [AER-6343] - (UDF) In single-bin namespaces, UDFs cannot read or write bin values. Fixed in version 5.2.0.11.
      • [AER-6339] - (KVS) On certain bitwise blob operations (and, or, xor), an out of bounds byte may be accessed and cause a crash. Fixed in version 5.2.0.10.
      • [AER-6330] - (KVS) Invalid HLL element list parameter may cause a crash. Fixed in version 5.2.0.9.
      • [AER-6332] - (KVS) An HLL union operation on an existing bin will overflow the stack. Fixed in version 5.2.0.9.
      • [AER-6334] - (EXPRESSIONS) A map value (as opposed to a map bin) in a compare expression results in an improper error. Fixed in version 5.2.0.9.
      • [AER-6336] - (BATCH) If both filters and bin selection are used in a batch request, proxied sub-transactions are malformed and will fail. Fixed in version 5.2.0.9.
      • [AER-6326] - (KVS) When Aerospike runs as the init process (e.g. in some container scenarios), signals do not stop Aerospike as intended. Fixed in version 5.2.0.7.
      • [AER-6318] - (EXPRESSIONS) The as_exp_hll_may_contain() operation returns an improper result. Fixed in version 5.2.0.6.
      • [AER-6316] - (EXPRESSIONS) Expressions may erroneously compare different blob types sent from the client. Fixed in version 5.2.0.5.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 5.2.0.5.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 5.2.0.4.
      • [AER-6309] - (CDT) For ordered lists, get_all_by_value_list operation with result type value always returns an empty list. Fixed in version 5.2.0.4.
      • [AER-6308] - (EXPRESSIONS) Miscellaneous issues in new expressions, which are not yet accessible from clients. Fixed in version 5.2.0.4.
    • Enterprise Only
      • 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.
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.2.0.34.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.2.0.33.
      • [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.2.0.31.
      • [AER-6427] - (KVS) For data-in-index namespaces, durable deletes will cause an unnecessary assertion on a warm restart. Fixed in version 5.2.0.28.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing. Fixed in version 5.2.0.27.
      • [AER-6413] - (LDAP) Small memory leak during LDAP login process. Fixed in version 5.2.0.24.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.2.0.24.
      • [AER-6404] - (KVS) For single-bin, data-in-memory namespaces, durable deletes may cause a crash on writing replicas or on subsequent restarts. Fixed in version 5.2.0.21.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 5.2.0.20.
      • [AER-6390] - (XDR) For strong-consistency namespaces, when DC namespace context configuration item bin-policy is not 'all', shipping records that are unreplicated may miss some bins. Fixed in version 5.2.0.19.
      • [AER-6382] - (LDAP) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 5.2.0.18.
      • [AER-6381] - (XDR) If a record expires between XDR reading and shipping, improper TTL will be shipped. Fixed in version 5.2.0.18.
      • [AER-6376] - (LDAP) 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.2.0.17.
      • [AER-6378] - (ACL) 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.2.0.17.
      • [AER-6366] - (XDR) Dynamically removing a connector seed node may cause a crash. Fixed in version 5.2.0.16.
      • [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.2.0.16.
      • [AER-6365] - (XDR) Reverts behavior change in AER-6240 as empty node addition may reject a lagging last ship time from the acting master, which may result in records not shipping. Fixed in version 5.2.0.15.
      • [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.2.0.14.
      • [AER-6361] - (LDAP) 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.2.0.14.
      • [AER-6356] - (XDR) When DC namespace context configuration item bin-policy is not 'all', locally written bins may not get shipped during recovery. Fixed in version 5.2.0.14.
      • [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.2.0.12.
      • [AER-6341] - (XDR) Source node may fail to discover the entire destination cluster when destination nodes restart. Fixed in version 5.2.0.11.
      • [AER-6327] - (TLS) When refreshing certificates, older chained certificates are not cleared. Fixed in version 5.2.0.7.
      • [AER-6325] - (XDR) DCs with connector true do not properly disconnect when all namespaces are dynamically removed. Fixed in version 5.2.0.7.
      • [AER-6322] - (XDR) When TLS handshake fails or times out, security authentication request buffer may be double freed, which may cause a crash. Fixed in version 5.2.0.6.
      • [AER-6313] - (XDR) Small memory leak when XDR client connects to seed node. Fixed in version 5.2.0.5.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 5.2.0.4.
      • [AER-6302] - (XDR) Namespace context configuration item xdr-tomb-raider-period cannot be set using time units. Fixed in version 5.2.0.4.
      • [AER-6310] - (XDR) When connection to seed node fails, TLS name will be double freed and may cause a crash. Fixed in version 5.2.0.4.

    Updates

  • 5.1.0.42
    Release Date: September 20, 2021
    • 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).
    • 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.

    Bug Fixes

    • Enterprise & Community
      • [AER-6481] - (KVS) When a service thread exits, its epoll queue's event file descriptor leaks.
      • [AER-6482] - (STORAGE) When a device runs completely out of space, defrag becomes ineffective.

    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).

  • 5.1.0.41
    Release Date: September 15, 2021
    • 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).
    • 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.

    Bug Fixes

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted.

    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).

  • 5.1.0.40
    Release Date: September 2, 2021
    • 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).
    • 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.

    Improvements

    • Enterprise & Community
      • [AER-6475] - (GEO) For data-in-memory namespaces, when trimming GeoJSON particles, reallocate into the appropriate namespace arena.

    Bug Fixes

    • Enterprise & Community
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces.

    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-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.1.0.41.

  • 5.1.0.39
    Release Date: August 4, 2021
    • 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).
    • 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.

    Bug Fixes

    • Enterprise Only
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or 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-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.1.0.41.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.1.0.40.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.1.0.40.

  • 5.1.0.38
    Release Date: July 19, 2021
    • 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).
    • 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.

    Bug Fixes

    • 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.

    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-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.1.0.41.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.1.0.40.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.1.0.40.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.1.0.39.

  • 5.1.0.37
    Release Date: June 24, 2021
    • 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).
    • 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.

    Bug Fixes

    • Enterprise & Community
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps.

    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-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.1.0.41.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.1.0.40.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.1.0.40.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.1.0.39.
      • [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.1.0.38.

  • 5.1.0.36
    Release Date: May 28, 2021
    • 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).
    • 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.

    Bug Fixes

    • Enterprise & Community
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes.

    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-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.1.0.41.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.1.0.40.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.1.0.37.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.1.0.40.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.1.0.39.
      • [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.1.0.38.

  • 5.1.0.35
    Release Date: May 25, 2021
    • 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).
    • 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.

    Bug Fixes

    • Enterprise Only
      • [AER-6427] - (KVS) For data-in-index namespaces, durable deletes will cause an unnecessary assertion on a warm restart.

    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-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.1.0.41.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.1.0.40.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.1.0.37.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.1.0.36.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.1.0.40.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.1.0.39.
      • [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.1.0.38.

  • 5.1.0.34
    Release Date: May 10, 2021
    • 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).
    • 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.

    Bug Fixes

    • Enterprise Only
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing.

    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-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.1.0.41.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.1.0.40.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.1.0.37.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.1.0.36.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.1.0.40.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.1.0.39.
      • [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.1.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.1.0.35.

  • 5.1.0.33
    Release Date: April 6, 2021
    • 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).
    • 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.

    Bug Fixes

    • Enterprise & Community
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory.

    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-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.1.0.41.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.1.0.40.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.1.0.37.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.1.0.36.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.1.0.40.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.1.0.39.
      • [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.1.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.1.0.35.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing. Fixed in version 5.1.0.34.

  • 5.1.0.32
    Release Date: April 2, 2021
    • 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).
    • 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.

    Bug Fixes

    • Enterprise & Community
      • [AER-6414] - (UDF) For namespaces with data not in memory, UDF replications will not adjust the secondary index.

    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-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.1.0.41.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.1.0.40.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.1.0.37.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.1.0.36.
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory. Fixed in version 5.1.0.33.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.1.0.40.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.1.0.39.
      • [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.1.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.1.0.35.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing. Fixed in version 5.1.0.34.

  • 5.1.0.31
    Release Date: March 29, 2021
    • 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).
    • 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.

    Bug Fixes

    • Enterprise & Community
      • [AER-6412] - (QUERY) If a query transaction setup fails in certain ways, improper cleanup may cause a crash.
    • Enterprise Only
      • [AER-6413] - (LDAP) Small memory leak during LDAP login process.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may 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-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.1.0.41.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.1.0.40.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.1.0.37.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.1.0.36.
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory. Fixed in version 5.1.0.33.
      • [AER-6414] - (UDF) For namespaces with data not in memory, UDF replications will not adjust the secondary index. Fixed in version 5.1.0.32.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.1.0.40.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.1.0.39.
      • [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.1.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.1.0.35.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing. Fixed in version 5.1.0.34.

  • 5.1.0.28
    Release Date: March 12, 2021
    • 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).
    • 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.

    Bug Fixes

    • Enterprise & Community
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical.
      • [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.
    • Enterprise Only
      • [AER-6404] - (KVS) For single-bin, data-in-memory namespaces, durable deletes may cause a crash on writing replicas or on subsequent restarts.

    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-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.1.0.41.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.1.0.40.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.1.0.37.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.1.0.36.
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory. Fixed in version 5.1.0.33.
      • [AER-6414] - (UDF) For namespaces with data not in memory, UDF replications will not adjust the secondary index. Fixed in version 5.1.0.32.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.1.0.40.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.1.0.39.
      • [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.1.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.1.0.35.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing. Fixed in version 5.1.0.34.
      • [AER-6413] - (LDAP) Small memory leak during LDAP login process. Fixed in version 5.1.0.31.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.1.0.31.

  • 5.1.0.27
    Release Date: February 22, 2021
    • 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).
    • 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.

    Bug Fixes

    • Enterprise Only
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers.

    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-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.1.0.41.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.1.0.40.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.1.0.37.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.1.0.36.
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory. Fixed in version 5.1.0.33.
      • [AER-6414] - (UDF) For namespaces with data not in memory, UDF replications will not adjust the secondary index. Fixed in version 5.1.0.32.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 5.1.0.28.
      • [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.1.0.28.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.1.0.40.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.1.0.39.
      • [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.1.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.1.0.35.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing. Fixed in version 5.1.0.34.
      • [AER-6413] - (LDAP) Small memory leak during LDAP login process. Fixed in version 5.1.0.31.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.1.0.31.
      • [AER-6404] - (KVS) For single-bin, data-in-memory namespaces, durable deletes may cause a crash on writing replicas or on subsequent restarts. Fixed in version 5.1.0.28.

  • 5.1.0.26
    Release Date: January 30, 2021
    • 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).
    • 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.

    Bug Fixes

    • Enterprise & Community
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated.
    • Enterprise Only
      • [AER-6382] - (LDAP) When connecting to LDAP server, TLS handshake occasionally fails.
      • [AER-6381] - (XDR) If a record expires between XDR reading and shipping, improper TTL will be shipped.

    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-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.1.0.41.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.1.0.40.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.1.0.37.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.1.0.36.
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory. Fixed in version 5.1.0.33.
      • [AER-6414] - (UDF) For namespaces with data not in memory, UDF replications will not adjust the secondary index. Fixed in version 5.1.0.32.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 5.1.0.28.
      • [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.1.0.28.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.1.0.40.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.1.0.39.
      • [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.1.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.1.0.35.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing. Fixed in version 5.1.0.34.
      • [AER-6413] - (LDAP) Small memory leak during LDAP login process. Fixed in version 5.1.0.31.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.1.0.31.
      • [AER-6404] - (KVS) For single-bin, data-in-memory namespaces, durable deletes may cause a crash on writing replicas or on subsequent restarts. Fixed in version 5.1.0.28.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 5.1.0.27.

  • 5.1.0.25
    Release Date: January 25, 2021
    • 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).
    • 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.

    Bug Fixes

    • Enterprise Only
      • [AER-6376] - (LDAP) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library.
      • [AER-6378] - (ACL) 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.

    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-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.1.0.41.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.1.0.40.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.1.0.37.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.1.0.36.
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory. Fixed in version 5.1.0.33.
      • [AER-6414] - (UDF) For namespaces with data not in memory, UDF replications will not adjust the secondary index. Fixed in version 5.1.0.32.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 5.1.0.28.
      • [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.1.0.28.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 5.1.0.26.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.1.0.40.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.1.0.39.
      • [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.1.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.1.0.35.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing. Fixed in version 5.1.0.34.
      • [AER-6413] - (LDAP) Small memory leak during LDAP login process. Fixed in version 5.1.0.31.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.1.0.31.
      • [AER-6404] - (KVS) For single-bin, data-in-memory namespaces, durable deletes may cause a crash on writing replicas or on subsequent restarts. Fixed in version 5.1.0.28.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 5.1.0.27.
      • [AER-6382] - (LDAP) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 5.1.0.26.
      • [AER-6381] - (XDR) If a record expires between XDR reading and shipping, improper TTL will be shipped. Fixed in version 5.1.0.26.

  • 5.1.0.24
    Release Date: January 15, 2021
    • 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).
    • 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.

    Bug Fixes

    • Enterprise Only
      • [AER-6366] - (XDR) Dynamically removing a connector seed node may cause a crash.
      • [AER-6369] - (XDR) When shipping the first record on a connection, if all bins are filtered out, a crash may result.

    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-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.1.0.41.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.1.0.40.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.1.0.37.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.1.0.36.
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory. Fixed in version 5.1.0.33.
      • [AER-6414] - (UDF) For namespaces with data not in memory, UDF replications will not adjust the secondary index. Fixed in version 5.1.0.32.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 5.1.0.28.
      • [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.1.0.28.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 5.1.0.26.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.1.0.40.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.1.0.39.
      • [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.1.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.1.0.35.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing. Fixed in version 5.1.0.34.
      • [AER-6413] - (LDAP) Small memory leak during LDAP login process. Fixed in version 5.1.0.31.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.1.0.31.
      • [AER-6404] - (KVS) For single-bin, data-in-memory namespaces, durable deletes may cause a crash on writing replicas or on subsequent restarts. Fixed in version 5.1.0.28.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 5.1.0.27.
      • [AER-6382] - (LDAP) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 5.1.0.26.
      • [AER-6381] - (XDR) If a record expires between XDR reading and shipping, improper TTL will be shipped. Fixed in version 5.1.0.26.
      • [AER-6376] - (LDAP) 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.1.0.25.
      • [AER-6378] - (ACL) 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.1.0.25.

  • 5.1.0.23
    Release Date: January 7, 2021
    • 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).
    • 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.

    Bug Fixes

    • Enterprise Only
      • [AER-6365] - (XDR) Reverts behavior change in AER-6240 as empty node addition may reject a lagging last ship time from the acting master, which may result in records not shipping.

    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-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.1.0.41.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.1.0.40.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.1.0.37.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.1.0.36.
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory. Fixed in version 5.1.0.33.
      • [AER-6414] - (UDF) For namespaces with data not in memory, UDF replications will not adjust the secondary index. Fixed in version 5.1.0.32.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 5.1.0.28.
      • [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.1.0.28.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 5.1.0.26.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.1.0.40.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.1.0.39.
      • [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.1.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.1.0.35.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing. Fixed in version 5.1.0.34.
      • [AER-6413] - (LDAP) Small memory leak during LDAP login process. Fixed in version 5.1.0.31.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.1.0.31.
      • [AER-6404] - (KVS) For single-bin, data-in-memory namespaces, durable deletes may cause a crash on writing replicas or on subsequent restarts. Fixed in version 5.1.0.28.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 5.1.0.27.
      • [AER-6382] - (LDAP) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 5.1.0.26.
      • [AER-6381] - (XDR) If a record expires between XDR reading and shipping, improper TTL will be shipped. Fixed in version 5.1.0.26.
      • [AER-6376] - (LDAP) 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.1.0.25.
      • [AER-6378] - (ACL) 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.1.0.25.
      • [AER-6366] - (XDR) Dynamically removing a connector seed node may cause a crash. Fixed in version 5.1.0.24.
      • [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.1.0.24.

  • 5.1.0.22
    Release Date: January 4, 2021
    • 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).
    • 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.

    Improvements

    • Enterprise & Community
      • [AER-6357] - (KVS) Handle exceeding the OS file descriptor limit gracefully, without asserting.

    Bug Fixes

    • Enterprise & Community
      • [AER-6358] - (KVS) For single-bin, data-in-memory namespaces, unwinding on failing a write operation may incorrectly free the original bin particle.
    • Enterprise Only
      • [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.
      • [AER-6361] - (LDAP) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item.

    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-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.1.0.41.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.1.0.40.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.1.0.37.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.1.0.36.
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory. Fixed in version 5.1.0.33.
      • [AER-6414] - (UDF) For namespaces with data not in memory, UDF replications will not adjust the secondary index. Fixed in version 5.1.0.32.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 5.1.0.28.
      • [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.1.0.28.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 5.1.0.26.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.1.0.40.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.1.0.39.
      • [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.1.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.1.0.35.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing. Fixed in version 5.1.0.34.
      • [AER-6413] - (LDAP) Small memory leak during LDAP login process. Fixed in version 5.1.0.31.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.1.0.31.
      • [AER-6404] - (KVS) For single-bin, data-in-memory namespaces, durable deletes may cause a crash on writing replicas or on subsequent restarts. Fixed in version 5.1.0.28.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 5.1.0.27.
      • [AER-6382] - (LDAP) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 5.1.0.26.
      • [AER-6381] - (XDR) If a record expires between XDR reading and shipping, improper TTL will be shipped. Fixed in version 5.1.0.26.
      • [AER-6376] - (LDAP) 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.1.0.25.
      • [AER-6378] - (ACL) 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.1.0.25.
      • [AER-6366] - (XDR) Dynamically removing a connector seed node may cause a crash. Fixed in version 5.1.0.24.
      • [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.1.0.24.
      • [AER-6365] - (XDR) Reverts behavior change in AER-6240 as empty node addition may reject a lagging last ship time from the acting master, which may result in records not shipping. Fixed in version 5.1.0.23.

  • 5.1.0.20
    Release Date: December 17, 2020
    • 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).
    • 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.

    Bug Fixes

    • Enterprise & Community
      • [AER-6351] - (SCAN) When generating sub-transactions for background scans and queries, the record TTL of the parent transaction is ignored.
    • Enterprise Only
      • [AER-6350] - (XDR) If a DC is dynamically removed and another added, handling of authentication configuration items may cause a double-free.

    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-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.1.0.41.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.1.0.40.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.1.0.37.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.1.0.36.
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory. Fixed in version 5.1.0.33.
      • [AER-6414] - (UDF) For namespaces with data not in memory, UDF replications will not adjust the secondary index. Fixed in version 5.1.0.32.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 5.1.0.28.
      • [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.1.0.28.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 5.1.0.26.
      • [AER-6358] - (KVS) For single-bin, data-in-memory namespaces, unwinding on failing a write operation may incorrectly free the original bin particle. Fixed in version 5.1.0.22.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.1.0.40.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.1.0.39.
      • [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.1.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.1.0.35.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing. Fixed in version 5.1.0.34.
      • [AER-6413] - (LDAP) Small memory leak during LDAP login process. Fixed in version 5.1.0.31.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.1.0.31.
      • [AER-6404] - (KVS) For single-bin, data-in-memory namespaces, durable deletes may cause a crash on writing replicas or on subsequent restarts. Fixed in version 5.1.0.28.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 5.1.0.27.
      • [AER-6382] - (LDAP) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 5.1.0.26.
      • [AER-6381] - (XDR) If a record expires between XDR reading and shipping, improper TTL will be shipped. Fixed in version 5.1.0.26.
      • [AER-6376] - (LDAP) 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.1.0.25.
      • [AER-6378] - (ACL) 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.1.0.25.
      • [AER-6366] - (XDR) Dynamically removing a connector seed node may cause a crash. Fixed in version 5.1.0.24.
      • [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.1.0.24.
      • [AER-6365] - (XDR) Reverts behavior change in AER-6240 as empty node addition may reject a lagging last ship time from the acting master, which may result in records not shipping. Fixed in version 5.1.0.23.
      • [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.1.0.22.
      • [AER-6361] - (LDAP) 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.1.0.22.

  • 5.1.0.19
    Release Date: December 4, 2020
    • 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).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.

    Bug Fixes

    • Enterprise & Community
      • [AER-6343] - (UDF) In single-bin namespaces, UDFs cannot read or write bin values.
    • Enterprise Only
      • [AER-6341] - (XDR) Source node may fail to discover the entire destination cluster when destination nodes restart.

    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-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.1.0.41.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.1.0.40.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.1.0.37.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.1.0.36.
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory. Fixed in version 5.1.0.33.
      • [AER-6414] - (UDF) For namespaces with data not in memory, UDF replications will not adjust the secondary index. Fixed in version 5.1.0.32.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 5.1.0.28.
      • [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.1.0.28.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 5.1.0.26.
      • [AER-6358] - (KVS) For single-bin, data-in-memory namespaces, unwinding on failing a write operation may incorrectly free the original bin particle. Fixed in version 5.1.0.22.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.1.0.40.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.1.0.39.
      • [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.1.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.1.0.35.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing. Fixed in version 5.1.0.34.
      • [AER-6413] - (LDAP) Small memory leak during LDAP login process. Fixed in version 5.1.0.31.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.1.0.31.
      • [AER-6404] - (KVS) For single-bin, data-in-memory namespaces, durable deletes may cause a crash on writing replicas or on subsequent restarts. Fixed in version 5.1.0.28.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 5.1.0.27.
      • [AER-6382] - (LDAP) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 5.1.0.26.
      • [AER-6381] - (XDR) If a record expires between XDR reading and shipping, improper TTL will be shipped. Fixed in version 5.1.0.26.
      • [AER-6376] - (LDAP) 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.1.0.25.
      • [AER-6378] - (ACL) 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.1.0.25.
      • [AER-6366] - (XDR) Dynamically removing a connector seed node may cause a crash. Fixed in version 5.1.0.24.
      • [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.1.0.24.
      • [AER-6365] - (XDR) Reverts behavior change in AER-6240 as empty node addition may reject a lagging last ship time from the acting master, which may result in records not shipping. Fixed in version 5.1.0.23.
      • [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.1.0.22.
      • [AER-6361] - (LDAP) 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.1.0.22.
      • [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.1.0.20.

  • 5.1.0.18
    Release Date: November 25, 2020
    • 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).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.

    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-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.1.0.41.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.1.0.40.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.1.0.37.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.1.0.36.
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory. Fixed in version 5.1.0.33.
      • [AER-6414] - (UDF) For namespaces with data not in memory, UDF replications will not adjust the secondary index. Fixed in version 5.1.0.32.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 5.1.0.28.
      • [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.1.0.28.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 5.1.0.26.
      • [AER-6358] - (KVS) For single-bin, data-in-memory namespaces, unwinding on failing a write operation may incorrectly free the original bin particle. Fixed in version 5.1.0.22.
      • [AER-6343] - (UDF) In single-bin namespaces, UDFs cannot read or write bin values. Fixed in version 5.1.0.19.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.1.0.40.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.1.0.39.
      • [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.1.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.1.0.35.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing. Fixed in version 5.1.0.34.
      • [AER-6413] - (LDAP) Small memory leak during LDAP login process. Fixed in version 5.1.0.31.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.1.0.31.
      • [AER-6404] - (KVS) For single-bin, data-in-memory namespaces, durable deletes may cause a crash on writing replicas or on subsequent restarts. Fixed in version 5.1.0.28.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 5.1.0.27.
      • [AER-6382] - (LDAP) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 5.1.0.26.
      • [AER-6381] - (XDR) If a record expires between XDR reading and shipping, improper TTL will be shipped. Fixed in version 5.1.0.26.
      • [AER-6376] - (LDAP) 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.1.0.25.
      • [AER-6378] - (ACL) 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.1.0.25.
      • [AER-6366] - (XDR) Dynamically removing a connector seed node may cause a crash. Fixed in version 5.1.0.24.
      • [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.1.0.24.
      • [AER-6365] - (XDR) Reverts behavior change in AER-6240 as empty node addition may reject a lagging last ship time from the acting master, which may result in records not shipping. Fixed in version 5.1.0.23.
      • [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.1.0.22.
      • [AER-6361] - (LDAP) 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.1.0.22.
      • [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.1.0.20.
      • [AER-6341] - (XDR) Source node may fail to discover the entire destination cluster when destination nodes restart. Fixed in version 5.1.0.19.

  • 5.1.0.17
    Release Date: November 19, 2020
    • 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).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.

    Bug Fixes

    • Enterprise & Community
      • [AER-6330] - (KVS) Invalid HLL element list parameter may cause a crash.
      • [AER-6332] - (KVS) An HLL union operation on an existing bin will overflow the stack.
      • [AER-6336] - (BATCH) If both filters and bin selection are used in a batch request, proxied sub-transactions are malformed and will fail.

    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-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.1.0.41.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.1.0.40.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.1.0.37.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.1.0.36.
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory. Fixed in version 5.1.0.33.
      • [AER-6414] - (UDF) For namespaces with data not in memory, UDF replications will not adjust the secondary index. Fixed in version 5.1.0.32.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 5.1.0.28.
      • [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.1.0.28.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 5.1.0.26.
      • [AER-6358] - (KVS) For single-bin, data-in-memory namespaces, unwinding on failing a write operation may incorrectly free the original bin particle. Fixed in version 5.1.0.22.
      • [AER-6343] - (UDF) In single-bin namespaces, UDFs cannot read or write bin values. Fixed in version 5.1.0.19.
      • [AER-6339] - (KVS) On certain bitwise blob operations (and, or, xor), an out of bounds byte may be accessed and cause a crash. Fixed in version 5.1.0.18.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.1.0.40.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.1.0.39.
      • [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.1.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.1.0.35.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing. Fixed in version 5.1.0.34.
      • [AER-6413] - (LDAP) Small memory leak during LDAP login process. Fixed in version 5.1.0.31.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.1.0.31.
      • [AER-6404] - (KVS) For single-bin, data-in-memory namespaces, durable deletes may cause a crash on writing replicas or on subsequent restarts. Fixed in version 5.1.0.28.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 5.1.0.27.
      • [AER-6382] - (LDAP) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 5.1.0.26.
      • [AER-6381] - (XDR) If a record expires between XDR reading and shipping, improper TTL will be shipped. Fixed in version 5.1.0.26.
      • [AER-6376] - (LDAP) 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.1.0.25.
      • [AER-6378] - (ACL) 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.1.0.25.
      • [AER-6366] - (XDR) Dynamically removing a connector seed node may cause a crash. Fixed in version 5.1.0.24.
      • [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.1.0.24.
      • [AER-6365] - (XDR) Reverts behavior change in AER-6240 as empty node addition may reject a lagging last ship time from the acting master, which may result in records not shipping. Fixed in version 5.1.0.23.
      • [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.1.0.22.
      • [AER-6361] - (LDAP) 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.1.0.22.
      • [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.1.0.20.
      • [AER-6341] - (XDR) Source node may fail to discover the entire destination cluster when destination nodes restart. Fixed in version 5.1.0.19.

  • 5.1.0.15
    Release Date: November 10, 2020
    • 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).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.

    Bug Fixes

    • Enterprise & Community
      • [AER-6326] - (KVS) When Aerospike runs as the init process (e.g. in some container scenarios), signals do not stop Aerospike as intended.
    • Enterprise Only
      • [AER-6327] - (TLS) When refreshing certificates, older chained certificates are not cleared.
      • [AER-6325] - (XDR) DCs with connector true do not properly disconnect when all namespaces are dynamically removed.

    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-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.1.0.41.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.1.0.40.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.1.0.37.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.1.0.36.
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory. Fixed in version 5.1.0.33.
      • [AER-6414] - (UDF) For namespaces with data not in memory, UDF replications will not adjust the secondary index. Fixed in version 5.1.0.32.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 5.1.0.28.
      • [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.1.0.28.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 5.1.0.26.
      • [AER-6358] - (KVS) For single-bin, data-in-memory namespaces, unwinding on failing a write operation may incorrectly free the original bin particle. Fixed in version 5.1.0.22.
      • [AER-6343] - (UDF) In single-bin namespaces, UDFs cannot read or write bin values. Fixed in version 5.1.0.19.
      • [AER-6339] - (KVS) On certain bitwise blob operations (and, or, xor), an out of bounds byte may be accessed and cause a crash. Fixed in version 5.1.0.18.
      • [AER-6330] - (KVS) Invalid HLL element list parameter may cause a crash. Fixed in version 5.1.0.17.
      • [AER-6332] - (KVS) An HLL union operation on an existing bin will overflow the stack. Fixed in version 5.1.0.17.
      • [AER-6336] - (BATCH) If both filters and bin selection are used in a batch request, proxied sub-transactions are malformed and will fail. Fixed in version 5.1.0.17.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.1.0.40.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.1.0.39.
      • [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.1.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.1.0.35.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing. Fixed in version 5.1.0.34.
      • [AER-6413] - (LDAP) Small memory leak during LDAP login process. Fixed in version 5.1.0.31.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.1.0.31.
      • [AER-6404] - (KVS) For single-bin, data-in-memory namespaces, durable deletes may cause a crash on writing replicas or on subsequent restarts. Fixed in version 5.1.0.28.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 5.1.0.27.
      • [AER-6382] - (LDAP) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 5.1.0.26.
      • [AER-6381] - (XDR) If a record expires between XDR reading and shipping, improper TTL will be shipped. Fixed in version 5.1.0.26.
      • [AER-6376] - (LDAP) 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.1.0.25.
      • [AER-6378] - (ACL) 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.1.0.25.
      • [AER-6366] - (XDR) Dynamically removing a connector seed node may cause a crash. Fixed in version 5.1.0.24.
      • [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.1.0.24.
      • [AER-6365] - (XDR) Reverts behavior change in AER-6240 as empty node addition may reject a lagging last ship time from the acting master, which may result in records not shipping. Fixed in version 5.1.0.23.
      • [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.1.0.22.
      • [AER-6361] - (LDAP) 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.1.0.22.
      • [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.1.0.20.
      • [AER-6341] - (XDR) Source node may fail to discover the entire destination cluster when destination nodes restart. Fixed in version 5.1.0.19.

  • 5.1.0.14
    Release Date: October 31, 2020
    • 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).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.

    Improvements

    • Enterprise & Community
      • [AER-6323] - (KVS) With debug-allocations enabled, adjust every logged site address for easier association with source code.

    Bug Fixes

    • Enterprise Only
      • [AER-6322] - (XDR) When TLS handshake fails or times out, security authentication request buffer may be double freed, which may 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-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted. Fixed in version 5.1.0.41.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write. Fixed in version 5.1.0.40.
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.1.0.37.
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 5.1.0.36.
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory. Fixed in version 5.1.0.33.
      • [AER-6414] - (UDF) For namespaces with data not in memory, UDF replications will not adjust the secondary index. Fixed in version 5.1.0.32.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 5.1.0.28.
      • [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.1.0.28.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 5.1.0.26.
      • [AER-6358] - (KVS) For single-bin, data-in-memory namespaces, unwinding on failing a write operation may incorrectly free the original bin particle. Fixed in version 5.1.0.22.
      • [AER-6343] - (UDF) In single-bin namespaces, UDFs cannot read or write bin values. Fixed in version 5.1.0.19.
      • [AER-6339] - (KVS) On certain bitwise blob operations (and, or, xor), an out of bounds byte may be accessed and cause a crash. Fixed in version 5.1.0.18.
      • [AER-6330] - (KVS) Invalid HLL element list parameter may cause a crash. Fixed in version 5.1.0.17.
      • [AER-6332] - (KVS) An HLL union operation on an existing bin will overflow the stack. Fixed in version 5.1.0.17.
      • [AER-6336] - (BATCH) If both filters and bin selection are used in a batch request, proxied sub-transactions are malformed and will fail. Fixed in version 5.1.0.17.
      • [AER-6326] - (KVS) When Aerospike runs as the init process (e.g. in some container scenarios), signals do not stop Aerospike as intended. Fixed in version 5.1.0.15.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces. Fixed in version 5.1.0.40.
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash. Fixed in version 5.1.0.39.
      • [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.1.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.1.0.35.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing. Fixed in version 5.1.0.34.
      • [AER-6413] - (LDAP) Small memory leak during LDAP login process. Fixed in version 5.1.0.31.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.1.0.31.
      • [AER-6404] - (KVS) For single-bin, data-in-memory namespaces, durable deletes may cause a crash on writing replicas or on subsequent restarts. Fixed in version 5.1.0.28.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 5.1.0.27.
      • [AER-6382] - (LDAP) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 5.1.0.26.
      • [AER-6381] - (XDR) If a record expires between XDR reading and shipping, improper TTL will be shipped. Fixed in version 5.1.0.26.
      • [AER-6376] - (LDAP) 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.1.0.25.
      • [AER-6378] - (ACL) 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.1.0.25.
      • [AER-6366] - (XDR) Dynamically removing a connector seed node may cause a crash. Fixed in version 5.1.0.24.
      • [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.1.0.24.
      • [AER-6365] - (XDR) Reverts behavior change in AER-6240 as empty node addition may reject a lagging last ship time from the acting master, which may result in records not shipping. Fixed in version 5.1.0.23.
      • [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.1.0.22.
      • [AER-6361] - (LDAP) 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.1.0.22.
      • [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.1.0.20.
      • [AER-6341] - (XDR) Source node may fail to discover the entire destination cluster when destination nodes restart. Fixed in version 5.1.0.19.
      • [AER-6327] - (TLS) When refreshing certificates, older chained certificates are not cleared. Fixed in version 5.1.0.15.
      • [AER-6325] - (XDR) DCs with connector true do not properly disconnect when all namespaces are dynamically removed. Fixed in version 5.1.0.15.