Aerospike Server EE Release Notes

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

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

  • 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] - (SECURITY) Small memory leak during LDAP login process.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash.

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

    Known Issues

    • Enterprise Only
      • [AER-6413] - (SECURITY) 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.

    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.

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

    Known Issues

    • Enterprise & Community
      • [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-6413] - (SECURITY) 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.

    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.

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

    Known Issues

    • Enterprise & Community
      • [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-6413] - (SECURITY) 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.

    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.

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

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

  • 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] - (SECURITY) Small memory leak during LDAP login process.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash.

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

    Known Issues

    • Enterprise Only
      • [AER-6413] - (SECURITY) 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.

    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.

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

    Known Issues

    • Enterprise & Community
      • [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-6413] - (SECURITY) 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.

    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.

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

    Known Issues

    • Enterprise & Community
      • [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-6413] - (SECURITY) 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.

    Bug Fixes

    • Enterprise & Community
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated.
    • Enterprise Only
      • [AER-6382] - (SECURITY) 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.

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

    Known Issues

    • Enterprise & Community
      • [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-6413] - (SECURITY) 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] - (SECURITY) 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.

    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] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges.

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

    Known Issues

    • Enterprise & Community
      • [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-6413] - (SECURITY) 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] - (SECURITY) 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] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 5.4.0.3.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 5.4.0.3.

    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.

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

    Known Issues

    • Enterprise & Community
      • [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-6413] - (SECURITY) 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] - (SECURITY) 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] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 5.4.0.3.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 5.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.

    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.

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

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

  • 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] - (SECURITY) Small memory leak during LDAP login process.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash.

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

    Known Issues

    • Enterprise Only
      • [AER-6413] - (SECURITY) 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.

    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.

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

    Known Issues

    • Enterprise & Community
      • [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-6413] - (SECURITY) 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.

    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.

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

    Known Issues

    • Enterprise & Community
      • [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-6413] - (SECURITY) 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.

    Bug Fixes

    • Enterprise & Community
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated.
    • Enterprise Only
      • [AER-6382] - (SECURITY) 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.

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

    Known Issues

    • Enterprise & Community
      • [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-6413] - (SECURITY) 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] - (SECURITY) 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.

    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] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges.

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

    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-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-6413] - (SECURITY) 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] - (SECURITY) 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] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 5.3.0.8.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 5.3.0.8.

    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.

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

    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-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-6413] - (SECURITY) 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] - (SECURITY) 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] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 5.3.0.8.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 5.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.

    Bug Fixes

    • Enterprise Only
      • [AER-6365] - (XDR) When an empty node is added, it will reject a lagging last ship time from the acting master, which may result in records not shipping.

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

    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-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-6413] - (SECURITY) 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] - (SECURITY) 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] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 5.3.0.8.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 5.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) When an empty node is added, it will reject a lagging last ship time from the acting master, which may result in records not shipping. Fixed in version 5.3.0.6.

    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] - (SECURITY) 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.

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

    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-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-6413] - (SECURITY) 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] - (SECURITY) 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] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 5.3.0.8.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 5.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) When an empty node is added, it will 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] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item. Fixed in version 5.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.

    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.

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

    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-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-6413] - (SECURITY) 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] - (SECURITY) 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] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 5.3.0.8.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 5.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) When an empty node is added, it will 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] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item. Fixed in version 5.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.

    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.

    Updates

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

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

  • 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] - (SECURITY) Small memory leak during LDAP login process.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash.

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

    Known Issues

    • Enterprise Only
      • [AER-6413] - (SECURITY) 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.

    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.

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

    Known Issues

    • Enterprise & Community
      • [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-6413] - (SECURITY) 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.

    Bug Fixes

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

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

    Known Issues

    • Enterprise & Community
      • [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-6413] - (SECURITY) 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.

    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.

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

    Known Issues

    • Enterprise & Community
      • [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-6413] - (SECURITY) 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.

    Bug Fixes

    • Enterprise & Community
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated.
    • Enterprise Only
      • [AER-6382] - (SECURITY) 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.

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

    Known Issues

    • Enterprise & Community
      • [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-6413] - (SECURITY) 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] - (SECURITY) 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.

    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] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges.

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

    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-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-6413] - (SECURITY) 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] - (SECURITY) 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] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 5.2.0.17.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 5.2.0.17.

    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.

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

    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-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-6413] - (SECURITY) 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] - (SECURITY) 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] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 5.2.0.17.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 5.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.

    Bug Fixes

    • Enterprise Only
      • [AER-6365] - (XDR) When an empty node is added, it will reject a lagging last ship time from the acting master, which may result in records not shipping.

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

    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-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-6413] - (SECURITY) 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] - (SECURITY) 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] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 5.2.0.17.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 5.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) When an empty node is added, it will reject a lagging last ship time from the acting master, which may result in records not shipping. Fixed in version 5.2.0.15.

    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] - (SECURITY) 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.

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

    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-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-6413] - (SECURITY) 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] - (SECURITY) 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] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 5.2.0.17.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 5.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) When an empty node is added, it will 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] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item. Fixed in version 5.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.

    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.

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

    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-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-6413] - (SECURITY) 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] - (SECURITY) 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] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 5.2.0.17.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 5.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) When an empty node is added, it will 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] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item. Fixed in version 5.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.

    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.

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

    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-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-6413] - (SECURITY) 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] - (SECURITY) 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] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 5.2.0.17.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 5.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) When an empty node is added, it will 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] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item. Fixed in version 5.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.

    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.

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

    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-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-6413] - (SECURITY) 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] - (SECURITY) 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] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 5.2.0.17.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 5.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) When an empty node is added, it will 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] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item. Fixed in version 5.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.

    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.

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

    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-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-6413] - (SECURITY) 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] - (SECURITY) 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] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 5.2.0.17.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 5.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) When an empty node is added, it will 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] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item. Fixed in version 5.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.

    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.

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

    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-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-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-6413] - (SECURITY) 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] - (SECURITY) 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] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 5.2.0.17.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 5.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) When an empty node is added, it will 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] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item. Fixed in version 5.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.

    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.

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

    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-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-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-6413] - (SECURITY) 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] - (SECURITY) 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] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 5.2.0.17.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 5.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) When an empty node is added, it will 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] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item. Fixed in version 5.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.

    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.

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

    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-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-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-6413] - (SECURITY) 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] - (SECURITY) 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] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 5.2.0.17.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 5.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) When an empty node is added, it will 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] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item. Fixed in version 5.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.

    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.

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

    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-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-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-6413] - (SECURITY) 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] - (SECURITY) 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] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 5.2.0.17.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 5.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) When an empty node is added, it will 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] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item. Fixed in version 5.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.

    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.

    Updates

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

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

    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.

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

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

    Bug Fixes

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

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

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

    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] - (SECURITY) Small memory leak during LDAP login process.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash.

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

    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).
    • Enterprise Only
      • [AER-6413] - (SECURITY) 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.

    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.

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

    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-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-6413] - (SECURITY) 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.

    Bug Fixes

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

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

    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-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-6413] - (SECURITY) 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.

    Bug Fixes

    • Enterprise & Community
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated.
    • Enterprise Only
      • [AER-6382] - (SECURITY) 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.

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

    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-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-6413] - (SECURITY) 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] - (SECURITY) 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.

    Bug Fixes

    • Enterprise Only
      • [AER-6376] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges.

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

    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-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-6413] - (SECURITY) 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] - (SECURITY) 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] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 5.1.0.25.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 5.1.0.25.

    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.

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

    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-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-6413] - (SECURITY) 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] - (SECURITY) 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] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 5.1.0.25.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 5.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.

    Bug Fixes

    • Enterprise Only
      • [AER-6365] - (XDR) When an empty node is added, it will reject a lagging last ship time from the acting master, which may result in records not shipping.

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

    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-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-6413] - (SECURITY) 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] - (SECURITY) 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] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 5.1.0.25.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 5.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) When an empty node is added, it will reject a lagging last ship time from the acting master, which may result in records not shipping. Fixed in version 5.1.0.23.

    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] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item.

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

    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-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-6413] - (SECURITY) 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] - (SECURITY) 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] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 5.1.0.25.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 5.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) When an empty node is added, it will 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] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item. Fixed in version 5.1.0.22.

    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.

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

    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-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-6413] - (SECURITY) 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] - (SECURITY) 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] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 5.1.0.25.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 5.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) When an empty node is added, it will 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] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item. Fixed in version 5.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.

    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.

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

    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-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-6413] - (SECURITY) 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] - (SECURITY) 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] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 5.1.0.25.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 5.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) When an empty node is added, it will 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] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item. Fixed in version 5.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.

    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.

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

    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-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-6413] - (SECURITY) 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] - (SECURITY) 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] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 5.1.0.25.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 5.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) When an empty node is added, it will 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] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item. Fixed in version 5.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.

    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.

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

    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-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-6413] - (SECURITY) 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] - (SECURITY) 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] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 5.1.0.25.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 5.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) When an empty node is added, it will 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] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item. Fixed in version 5.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.

    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.

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

    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-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-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-6413] - (SECURITY) 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] - (SECURITY) 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] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 5.1.0.25.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 5.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) When an empty node is added, it will 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] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item. Fixed in version 5.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.

    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.

  • 5.1.0.13
    Release Date: October 21, 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.

    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-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-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-6413] - (SECURITY) 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] - (SECURITY) 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] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 5.1.0.25.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 5.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) When an empty node is added, it will 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] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item. Fixed in version 5.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.
      • [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.1.0.14.

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

  • 5.1.0.12
    Release Date: October 14, 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.

    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-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-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.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 5.1.0.13.
    • Enterprise Only
      • [AER-6413] - (SECURITY) 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] - (SECURITY) 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] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 5.1.0.25.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 5.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) When an empty node is added, it will 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] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item. Fixed in version 5.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.
      • [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.1.0.14.
      • [AER-6313] - (XDR) Small memory leak when XDR client connects to seed node. Fixed in version 5.1.0.13.

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

  • 5.1.0.10
    Release Date: September 18, 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.

    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-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-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.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 5.1.0.13.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 5.1.0.12.
      • [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.1.0.12.
    • Enterprise Only
      • [AER-6413] - (SECURITY) 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] - (SECURITY) 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] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 5.1.0.25.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 5.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) When an empty node is added, it will 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] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item. Fixed in version 5.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.
      • [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.1.0.14.
      • [AER-6313] - (XDR) Small memory leak when XDR client connects to seed node. Fixed in version 5.1.0.13.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 5.1.0.12.
      • [AER-6302] - (XDR) Namespace context configuration item xdr-tomb-raider-period cannot be set using time units. Fixed in version 5.1.0.12.
      • [AER-6310] - (XDR) When connection to seed node fails, TLS name will be double freed and may cause a crash. Fixed in version 5.1.0.12.

    Improvements

    • Enterprise & Community
    • Enterprise Only
      • [AER-6288] - (XDR) Keep the last ship time of non-owned partitions relatively current.

    Bug Fixes

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

  • 5.1.0.7
    Release Date: August 24, 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.

    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-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-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.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 5.1.0.13.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 5.1.0.12.
      • [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.1.0.12.
      • [AER-6289] - (KVS) Concurrently reading and writing a new bin or set name may access a pointer which crosses a cache line boundary, causing a crash. Fixed in version 5.1.0.10.
      • [AER-6290] - (KVS) For namespaces with data not in memory, failure when reading a record from 'flat' format may cause a crash. Fixed in version 5.1.0.10.
    • Enterprise Only
      • [AER-6413] - (SECURITY) 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] - (SECURITY) 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] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 5.1.0.25.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 5.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) When an empty node is added, it will 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] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item. Fixed in version 5.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.
      • [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.1.0.14.
      • [AER-6313] - (XDR) Small memory leak when XDR client connects to seed node. Fixed in version 5.1.0.13.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 5.1.0.12.
      • [AER-6302] - (XDR) Namespace context configuration item xdr-tomb-raider-period cannot be set using time units. Fixed in version 5.1.0.12.
      • [AER-6310] - (XDR) When connection to seed node fails, TLS name will be double freed and may cause a crash. Fixed in version 5.1.0.12.
      • [AER-6287] - (KVS) When writing over a tombstone with Time-To-Live (TTL) value -2 (i.e. do not update TTL), the write fails to apply the namespace default-ttl. Fixed in version 5.1.0.10.
    • Community Only
      • [AER-6286] - (TELEMETRY) Telemetry fails to start on Amazon Elastic Compute Cloud (Amazon EC2) on Amazon Linux 2 with Python 3 installed. Fixed in version 5.1.0.10.

    Bug Fixes

    • Enterprise & Community
      • [AER-6278] - (UDF) For namespaces with data not in memory, executing a UDF on a record with more than ~3750 bins will overflow the stack.

  • 5.1.0.6
    Release Date: August 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.

    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-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-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.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 5.1.0.13.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 5.1.0.12.
      • [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.1.0.12.
      • [AER-6289] - (KVS) Concurrently reading and writing a new bin or set name may access a pointer which crosses a cache line boundary, causing a crash. Fixed in version 5.1.0.10.
      • [AER-6290] - (KVS) For namespaces with data not in memory, failure when reading a record from 'flat' format may cause a crash. Fixed in version 5.1.0.10.
      • [AER-6278] - (UDF) For namespaces with data not in memory, executing a UDF on a record with more than ~3750 bins will overflow the stack. Fixed in version 5.1.0.7.
    • Enterprise Only
      • [AER-6413] - (SECURITY) 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] - (SECURITY) 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] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 5.1.0.25.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 5.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) When an empty node is added, it will 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] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item. Fixed in version 5.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.
      • [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.1.0.14.
      • [AER-6313] - (XDR) Small memory leak when XDR client connects to seed node. Fixed in version 5.1.0.13.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 5.1.0.12.
      • [AER-6302] - (XDR) Namespace context configuration item xdr-tomb-raider-period cannot be set using time units. Fixed in version 5.1.0.12.
      • [AER-6310] - (XDR) When connection to seed node fails, TLS name will be double freed and may cause a crash. Fixed in version 5.1.0.12.
      • [AER-6287] - (KVS) When writing over a tombstone with Time-To-Live (TTL) value -2 (i.e. do not update TTL), the write fails to apply the namespace default-ttl. Fixed in version 5.1.0.10.
    • Community Only
      • [AER-6286] - (TELEMETRY) Telemetry fails to start on Amazon Elastic Compute Cloud (Amazon EC2) on Amazon Linux 2 with Python 3 installed. Fixed in version 5.1.0.10.

    Improvements

    • Enterprise & Community
      • [AER-6238] - (UDF) Added service context configuration item disable-udf-execution as a mitigation option for Lua security vulnerabilities.

    Bug Fixes

    • Enterprise & Community
      • [AER-6276] - (STORAGE) At startup, setting storage context configuration item max-write-cache too large will cause an integer overflow when calculating maximum write queue depth.

  • 5.1.0.5
    Release Date: August 11, 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.

    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-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-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.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 5.1.0.13.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 5.1.0.12.
      • [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.1.0.12.
      • [AER-6289] - (KVS) Concurrently reading and writing a new bin or set name may access a pointer which crosses a cache line boundary, causing a crash. Fixed in version 5.1.0.10.
      • [AER-6290] - (KVS) For namespaces with data not in memory, failure when reading a record from 'flat' format may cause a crash. Fixed in version 5.1.0.10.
      • [AER-6278] - (UDF) For namespaces with data not in memory, executing a UDF on a record with more than ~3750 bins will overflow the stack. Fixed in version 5.1.0.7.
      • [AER-6276] - (STORAGE) At startup, setting storage context configuration item max-write-cache too large will cause an integer overflow when calculating maximum write queue depth. Fixed in version 5.1.0.6.
    • Enterprise Only
      • [AER-6413] - (SECURITY) 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] - (SECURITY) 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] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 5.1.0.25.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 5.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) When an empty node is added, it will 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] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item. Fixed in version 5.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.
      • [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.1.0.14.
      • [AER-6313] - (XDR) Small memory leak when XDR client connects to seed node. Fixed in version 5.1.0.13.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 5.1.0.12.
      • [AER-6302] - (XDR) Namespace context configuration item xdr-tomb-raider-period cannot be set using time units. Fixed in version 5.1.0.12.
      • [AER-6310] - (XDR) When connection to seed node fails, TLS name will be double freed and may cause a crash. Fixed in version 5.1.0.12.
      • [AER-6287] - (KVS) When writing over a tombstone with Time-To-Live (TTL) value -2 (i.e. do not update TTL), the write fails to apply the namespace default-ttl. Fixed in version 5.1.0.10.
    • Community Only
      • [AER-6286] - (TELEMETRY) Telemetry fails to start on Amazon Elastic Compute Cloud (Amazon EC2) on Amazon Linux 2 with Python 3 installed. Fixed in version 5.1.0.10.

    Bug Fixes

    • Enterprise Only
      • [AER-6275] - (SECURITY) Escaping characters prevents binding to LDAP (escaping should only be done for role queries).

  • 5.1.0.4
    Release Date: August 5, 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.

    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-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-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.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 5.1.0.13.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 5.1.0.12.
      • [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.1.0.12.
      • [AER-6289] - (KVS) Concurrently reading and writing a new bin or set name may access a pointer which crosses a cache line boundary, causing a crash. Fixed in version 5.1.0.10.
      • [AER-6290] - (KVS) For namespaces with data not in memory, failure when reading a record from 'flat' format may cause a crash. Fixed in version 5.1.0.10.
      • [AER-6278] - (UDF) For namespaces with data not in memory, executing a UDF on a record with more than ~3750 bins will overflow the stack. Fixed in version 5.1.0.7.
      • [AER-6276] - (STORAGE) At startup, setting storage context configuration item max-write-cache too large will cause an integer overflow when calculating maximum write queue depth. Fixed in version 5.1.0.6.
    • Enterprise Only
      • [AER-6413] - (SECURITY) 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] - (SECURITY) 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] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 5.1.0.25.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 5.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) When an empty node is added, it will 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] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item. Fixed in version 5.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.
      • [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.1.0.14.
      • [AER-6313] - (XDR) Small memory leak when XDR client connects to seed node. Fixed in version 5.1.0.13.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 5.1.0.12.
      • [AER-6302] - (XDR) Namespace context configuration item xdr-tomb-raider-period cannot be set using time units. Fixed in version 5.1.0.12.
      • [AER-6310] - (XDR) When connection to seed node fails, TLS name will be double freed and may cause a crash. Fixed in version 5.1.0.12.
      • [AER-6287] - (KVS) When writing over a tombstone with Time-To-Live (TTL) value -2 (i.e. do not update TTL), the write fails to apply the namespace default-ttl. Fixed in version 5.1.0.10.
      • [AER-6275] - (SECURITY) Escaping characters prevents binding to LDAP (escaping should only be done for role queries). Fixed in version 5.1.0.5.
    • Community Only
      • [AER-6286] - (TELEMETRY) Telemetry fails to start on Amazon Elastic Compute Cloud (Amazon EC2) on Amazon Linux 2 with Python 3 installed. Fixed in version 5.1.0.10.

    Bug Fixes

    • Enterprise Only
      • [AER-6267] - (XDR) Setting DC context configuration item auth-user without setting auth-password-file will cause a crash.
      • [AER-6268] - (SECURITY) Setting LDAP context configuration item query-user-password-file dynamically may cause a crash.
      • [AER-6269] - (XDR) Setting DC context configuration item auth-password-file while connected to DC may cause a crash.
      • [AER-6270] - (XDR) If dynamically adding a DC, configuring a TLS specification containing a key-file without a required key-file-password will cause a crash.
      • [AER-6271] - (SECURITY) When fetching various configured items, file descriptors leak and may eventually exhaust the system and cause a crash.

  • 5.1.0.3
    Release Date: July 31, 2020
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Thanks to Matt S. for discovering the issue CVE-2020-13151.
      • To address the UDF security vulnerabilities, we are making a few changes on the server:
        • Lua’s io library has been removed, and the os library only retains time-related functions.
        • We will no longer construct/use a sandbox for each invoked record or stream UDF.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • 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.
    • 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.

    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-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-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.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 5.1.0.13.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 5.1.0.12.
      • [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.1.0.12.
      • [AER-6289] - (KVS) Concurrently reading and writing a new bin or set name may access a pointer which crosses a cache line boundary, causing a crash. Fixed in version 5.1.0.10.
      • [AER-6290] - (KVS) For namespaces with data not in memory, failure when reading a record from 'flat' format may cause a crash. Fixed in version 5.1.0.10.
      • [AER-6278] - (UDF) For namespaces with data not in memory, executing a UDF on a record with more than ~3750 bins will overflow the stack. Fixed in version 5.1.0.7.
      • [AER-6276] - (STORAGE) At startup, setting storage context configuration item max-write-cache too large will cause an integer overflow when calculating maximum write queue depth. Fixed in version 5.1.0.6.
    • Enterprise Only
      • [AER-6413] - (SECURITY) 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] - (SECURITY) 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] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 5.1.0.25.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 5.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) When an empty node is added, it will 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] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item. Fixed in version 5.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.
      • [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.1.0.14.
      • [AER-6313] - (XDR) Small memory leak when XDR client connects to seed node. Fixed in version 5.1.0.13.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 5.1.0.12.
      • [AER-6302] - (XDR) Namespace context configuration item xdr-tomb-raider-period cannot be set using time units. Fixed in version 5.1.0.12.
      • [AER-6310] - (XDR) When connection to seed node fails, TLS name will be double freed and may cause a crash. Fixed in version 5.1.0.12.
      • [AER-6287] - (KVS) When writing over a tombstone with Time-To-Live (TTL) value -2 (i.e. do not update TTL), the write fails to apply the namespace default-ttl. Fixed in version 5.1.0.10.
      • [AER-6275] - (SECURITY) Escaping characters prevents binding to LDAP (escaping should only be done for role queries). Fixed in version 5.1.0.5.
      • [AER-6267] - (XDR) Setting DC context configuration item auth-user without setting auth-password-file will cause a crash. Fixed in version 5.1.0.4.
      • [AER-6268] - (SECURITY) Setting LDAP context configuration item query-user-password-file dynamically may cause a crash. Fixed in version 5.1.0.4.
      • [AER-6269] - (XDR) Setting DC context configuration item auth-password-file while connected to DC may cause a crash. Fixed in version 5.1.0.4.
      • [AER-6270] - (XDR) If dynamically adding a DC, configuring a TLS specification containing a key-file without a required key-file-password will cause a crash. Fixed in version 5.1.0.4.
      • [AER-6271] - (SECURITY) When fetching various configured items, file descriptors leak and may eventually exhaust the system and cause a crash. Fixed in version 5.1.0.4.
    • Community Only
      • [AER-6286] - (TELEMETRY) Telemetry fails to start on Amazon Elastic Compute Cloud (Amazon EC2) on Amazon Linux 2 with Python 3 installed. Fixed in version 5.1.0.10.

    New Features

    • Enterprise & Community
      • [AER-6262] - (PACKAGING) Added support for Ubuntu 20, and removed support for Ubuntu 14.
    • Enterprise Only
      • [AER-6247] - (SECURITY) Added support for storing various configuration items in Vault.

    Improvements

    • Enterprise & Community
      • [AER-6229] - (KVS) When retransmitting replica writes, recalculate the destination nodes in case they changed due to a rebalance.
      • [AER-6244] - (KVS) Changed default value of proto-fd-idle-ms to 0 (i.e. never reap idle connections).
      • [AER-6249] - (KVS) Improved handling of record bins.
      • [AER-6264] - (FABRIC) Added fabric context configuration item channel-rw-recv-pools to specify multiple rw channel receive thread pools.
      • [AER-6234] - (STORAGE) Added throttling to prevent defrag from overwhelming the write queue.
      • [AER-6243] - (UDF) Addressed Lua security vulnerabilities by denying access to unsafe Lua library functions.
      • [AER-6257] - (UDF) UDFs unwind correctly on failure.
      • [AER-6265] - (GEO) Use stricter bounds checking for latitude and longitude.
      • [AER-4100] - (STATS) Added service context configuration item microsecond-histograms to generate high resolution latency histograms.
      • [AER-6242] - (STATS) Replaced info command latency with new command latencies to track all latency histograms.
    • Enterprise Only
      • [AER-6064] - (SECURITY) Escape problematic characters in the user Distinguished Name (DN) before giving it to the LDAP server.
      • [AER-6252] - (SECURITY) LDAP context configuration item query-user-password-file is now dynamic and is re-read whenever the password is used.
      • [AER-6253] - (SECURITY) The write privilege now includes permission to run truncate commands.
      • [AER-6255] - (STORAGE) For storage-engine pmem namespaces, set default service-threads to number of CPUs.
      • [AER-6263] - (STORAGE) Keep storage-engine pmem data blocks read-only except when they are being filled.
      • [AER-6233] - (XDR) Added DC namespace context configuration item write-policy.
      • [AER-6240] - (XDR) If the SMD-persisted last ship time is missing at startup, ship from the current time.
      • [AER-6241] - (XDR) Added retry_no_node stat.
      • [AER-6245] - (XDR) Added DC context configuration item period-ms.
      • [AER-6246] - (XDR) Added DC namespace context configuration item sc-replication-wait-ms.
      • [AER-6266] - (XDR) Added DC namespace context configuration item compression-level.

    Updates

  • 5.0.0.33
    Release Date: March 29, 2021
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0.
      • Aerospike Server version 5.0 will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • 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.

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

    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] - (SECURITY) Small memory leak during LDAP login process.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash.

  • 5.0.0.30
    Release Date: March 12, 2021
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0.
      • Aerospike Server version 5.0 will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • 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.

    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).
    • Enterprise Only
      • [AER-6413] - (SECURITY) Small memory leak during LDAP login process. Fixed in version 5.0.0.33.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.0.0.33.

    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.

  • 5.0.0.29
    Release Date: February 22, 2021
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0.
      • Aerospike Server version 5.0 will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • 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.

    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-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 5.0.0.30.
      • [AER-6402] - (SINDEX) When iterating through secondary indexes to adjust for changing list bin values, inactive indexes are incorrectly skipped, which may cause a crash. Fixed in version 5.0.0.30.
    • Enterprise Only
      • [AER-6413] - (SECURITY) Small memory leak during LDAP login process. Fixed in version 5.0.0.33.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.0.0.33.

    Bug Fixes

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

  • 5.0.0.28
    Release Date: January 30, 2021
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0.
      • Aerospike Server version 5.0 will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • 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.

    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-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 5.0.0.30.
      • [AER-6402] - (SINDEX) When iterating through secondary indexes to adjust for changing list bin values, inactive indexes are incorrectly skipped, which may cause a crash. Fixed in version 5.0.0.30.
    • Enterprise Only
      • [AER-6413] - (SECURITY) Small memory leak during LDAP login process. Fixed in version 5.0.0.33.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.0.0.33.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 5.0.0.29.

    Bug Fixes

    • Enterprise & Community
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated.
    • Enterprise Only
      • [AER-6382] - (SECURITY) 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.

  • 5.0.0.27
    Release Date: January 25, 2021
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0.
      • Aerospike Server version 5.0 will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • 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.

    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-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 5.0.0.30.
      • [AER-6402] - (SINDEX) When iterating through secondary indexes to adjust for changing list bin values, inactive indexes are incorrectly skipped, which may cause a crash. Fixed in version 5.0.0.30.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 5.0.0.28.
    • Enterprise Only
      • [AER-6413] - (SECURITY) Small memory leak during LDAP login process. Fixed in version 5.0.0.33.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.0.0.33.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 5.0.0.29.
      • [AER-6382] - (SECURITY) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 5.0.0.28.
      • [AER-6381] - (XDR) If a record expires between XDR reading and shipping, improper TTL will be shipped. Fixed in version 5.0.0.28.

    Bug Fixes

    • Enterprise Only
      • [AER-6376] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges.

  • 5.0.0.26
    Release Date: January 15, 2021
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0.
      • Aerospike Server version 5.0 will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • 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.

    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-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 5.0.0.30.
      • [AER-6402] - (SINDEX) When iterating through secondary indexes to adjust for changing list bin values, inactive indexes are incorrectly skipped, which may cause a crash. Fixed in version 5.0.0.30.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 5.0.0.28.
    • Enterprise Only
      • [AER-6413] - (SECURITY) Small memory leak during LDAP login process. Fixed in version 5.0.0.33.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.0.0.33.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 5.0.0.29.
      • [AER-6382] - (SECURITY) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 5.0.0.28.
      • [AER-6381] - (XDR) If a record expires between XDR reading and shipping, improper TTL will be shipped. Fixed in version 5.0.0.28.
      • [AER-6376] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 5.0.0.27.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 5.0.0.27.

    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.

  • 5.0.0.25
    Release Date: January 4, 2021
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0.
      • Aerospike Server version 5.0 will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • 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.

    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-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 5.0.0.30.
      • [AER-6402] - (SINDEX) When iterating through secondary indexes to adjust for changing list bin values, inactive indexes are incorrectly skipped, which may cause a crash. Fixed in version 5.0.0.30.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 5.0.0.28.
    • Enterprise Only
      • [AER-6413] - (SECURITY) Small memory leak during LDAP login process. Fixed in version 5.0.0.33.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.0.0.33.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 5.0.0.29.
      • [AER-6382] - (SECURITY) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 5.0.0.28.
      • [AER-6381] - (XDR) If a record expires between XDR reading and shipping, improper TTL will be shipped. Fixed in version 5.0.0.28.
      • [AER-6376] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 5.0.0.27.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 5.0.0.27.
      • [AER-6366] - (XDR) Dynamically removing a connector seed node may cause a crash. Fixed in version 5.0.0.26.
      • [AER-6369] - (XDR) When shipping the first record on a connection, if all bins are filtered out, a crash may result. Fixed in version 5.0.0.26.

    Improvements

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

    Bug Fixes

    • 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] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item.

  • 5.0.0.23
    Release Date: December 17, 2020
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0.
      • Aerospike Server version 5.0 will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • 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.

    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-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 5.0.0.30.
      • [AER-6402] - (SINDEX) When iterating through secondary indexes to adjust for changing list bin values, inactive indexes are incorrectly skipped, which may cause a crash. Fixed in version 5.0.0.30.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 5.0.0.28.
    • Enterprise Only
      • [AER-6413] - (SECURITY) Small memory leak during LDAP login process. Fixed in version 5.0.0.33.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.0.0.33.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 5.0.0.29.
      • [AER-6382] - (SECURITY) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 5.0.0.28.
      • [AER-6381] - (XDR) If a record expires between XDR reading and shipping, improper TTL will be shipped. Fixed in version 5.0.0.28.
      • [AER-6376] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 5.0.0.27.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 5.0.0.27.
      • [AER-6366] - (XDR) Dynamically removing a connector seed node may cause a crash. Fixed in version 5.0.0.26.
      • [AER-6369] - (XDR) When shipping the first record on a connection, if all bins are filtered out, a crash may result. Fixed in version 5.0.0.26.
      • [AER-6363] - (KVS) A write or a UDF that deletes all of a record's bins may result in a tombstone with a non-zero void-time. Fixed in version 5.0.0.25.
      • [AER-6361] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item. Fixed in version 5.0.0.25.

    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.

  • 5.0.0.22
    Release Date: December 4, 2020
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0.
      • Aerospike Server version 5.0 will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.

    Known Issues

    • Enterprise & Community
      • [AER-6340] - (KVS) HLL string or blob elements sized 31 to 254 bytes may be treated differently depending on msgpack standard. 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-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 5.0.0.30.
      • [AER-6402] - (SINDEX) When iterating through secondary indexes to adjust for changing list bin values, inactive indexes are incorrectly skipped, which may cause a crash. Fixed in version 5.0.0.30.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 5.0.0.28.
    • Enterprise Only
      • [AER-6413] - (SECURITY) Small memory leak during LDAP login process. Fixed in version 5.0.0.33.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.0.0.33.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 5.0.0.29.
      • [AER-6382] - (SECURITY) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 5.0.0.28.
      • [AER-6381] - (XDR) If a record expires between XDR reading and shipping, improper TTL will be shipped. Fixed in version 5.0.0.28.
      • [AER-6376] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 5.0.0.27.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 5.0.0.27.
      • [AER-6366] - (XDR) Dynamically removing a connector seed node may cause a crash. Fixed in version 5.0.0.26.
      • [AER-6369] - (XDR) When shipping the first record on a connection, if all bins are filtered out, a crash may result. Fixed in version 5.0.0.26.
      • [AER-6363] - (KVS) A write or a UDF that deletes all of a record's bins may result in a tombstone with a non-zero void-time. Fixed in version 5.0.0.25.
      • [AER-6361] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item. Fixed in version 5.0.0.25.
      • [AER-6350] - (XDR) If a DC is dynamically removed and another added, handling of authentication configuration items may cause a double-free. Fixed in version 5.0.0.23.

    Bug Fixes

    • Enterprise Only
      • [AER-6341] - (XDR) Source node may fail to discover the entire destination cluster when destination nodes restart.

  • 5.0.0.21
    Release Date: November 25, 2020
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0.
      • Aerospike Server version 5.0 will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.

    Known Issues

    • Enterprise & Community
      • [AER-6340] - (KVS) HLL string or blob elements sized 31 to 254 bytes may be treated differently depending on msgpack standard. 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-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 5.0.0.30.
      • [AER-6402] - (SINDEX) When iterating through secondary indexes to adjust for changing list bin values, inactive indexes are incorrectly skipped, which may cause a crash. Fixed in version 5.0.0.30.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 5.0.0.28.
    • Enterprise Only
      • [AER-6413] - (SECURITY) Small memory leak during LDAP login process. Fixed in version 5.0.0.33.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.0.0.33.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 5.0.0.29.
      • [AER-6382] - (SECURITY) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 5.0.0.28.
      • [AER-6381] - (XDR) If a record expires between XDR reading and shipping, improper TTL will be shipped. Fixed in version 5.0.0.28.
      • [AER-6376] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 5.0.0.27.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 5.0.0.27.
      • [AER-6366] - (XDR) Dynamically removing a connector seed node may cause a crash. Fixed in version 5.0.0.26.
      • [AER-6369] - (XDR) When shipping the first record on a connection, if all bins are filtered out, a crash may result. Fixed in version 5.0.0.26.
      • [AER-6363] - (KVS) A write or a UDF that deletes all of a record's bins may result in a tombstone with a non-zero void-time. Fixed in version 5.0.0.25.
      • [AER-6361] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item. Fixed in version 5.0.0.25.
      • [AER-6350] - (XDR) If a DC is dynamically removed and another added, handling of authentication configuration items may cause a double-free. Fixed in version 5.0.0.23.
      • [AER-6341] - (XDR) Source node may fail to discover the entire destination cluster when destination nodes restart. Fixed in version 5.0.0.22.

    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.

  • 5.0.0.20
    Release Date: November 19, 2020
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0.
      • Aerospike Server version 5.0 will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.

    Known Issues

    • Enterprise & Community
      • [AER-6340] - (KVS) HLL string or blob elements sized 31 to 254 bytes may be treated differently depending on msgpack standard. 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-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 5.0.0.30.
      • [AER-6402] - (SINDEX) When iterating through secondary indexes to adjust for changing list bin values, inactive indexes are incorrectly skipped, which may cause a crash. Fixed in version 5.0.0.30.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 5.0.0.28.
      • [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.0.0.21.
    • Enterprise Only
      • [AER-6413] - (SECURITY) Small memory leak during LDAP login process. Fixed in version 5.0.0.33.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.0.0.33.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 5.0.0.29.
      • [AER-6382] - (SECURITY) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 5.0.0.28.
      • [AER-6381] - (XDR) If a record expires between XDR reading and shipping, improper TTL will be shipped. Fixed in version 5.0.0.28.
      • [AER-6376] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 5.0.0.27.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 5.0.0.27.
      • [AER-6366] - (XDR) Dynamically removing a connector seed node may cause a crash. Fixed in version 5.0.0.26.
      • [AER-6369] - (XDR) When shipping the first record on a connection, if all bins are filtered out, a crash may result. Fixed in version 5.0.0.26.
      • [AER-6363] - (KVS) A write or a UDF that deletes all of a record's bins may result in a tombstone with a non-zero void-time. Fixed in version 5.0.0.25.
      • [AER-6361] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item. Fixed in version 5.0.0.25.
      • [AER-6350] - (XDR) If a DC is dynamically removed and another added, handling of authentication configuration items may cause a double-free. Fixed in version 5.0.0.23.
      • [AER-6341] - (XDR) Source node may fail to discover the entire destination cluster when destination nodes restart. Fixed in version 5.0.0.22.

    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.

  • 5.0.0.18
    Release Date: November 10, 2020
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0.
      • Aerospike Server version 5.0 will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.

    Known Issues

    • Enterprise & Community
      • [AER-6340] - (KVS) HLL string or blob elements sized 31 to 254 bytes may be treated differently depending on msgpack standard. 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-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 5.0.0.30.
      • [AER-6402] - (SINDEX) When iterating through secondary indexes to adjust for changing list bin values, inactive indexes are incorrectly skipped, which may cause a crash. Fixed in version 5.0.0.30.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 5.0.0.28.
      • [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.0.0.21.
    • Enterprise Only
      • [AER-6413] - (SECURITY) Small memory leak during LDAP login process. Fixed in version 5.0.0.33.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.0.0.33.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 5.0.0.29.
      • [AER-6382] - (SECURITY) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 5.0.0.28.
      • [AER-6381] - (XDR) If a record expires between XDR reading and shipping, improper TTL will be shipped. Fixed in version 5.0.0.28.
      • [AER-6376] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 5.0.0.27.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 5.0.0.27.
      • [AER-6366] - (XDR) Dynamically removing a connector seed node may cause a crash. Fixed in version 5.0.0.26.
      • [AER-6369] - (XDR) When shipping the first record on a connection, if all bins are filtered out, a crash may result. Fixed in version 5.0.0.26.
      • [AER-6363] - (KVS) A write or a UDF that deletes all of a record's bins may result in a tombstone with a non-zero void-time. Fixed in version 5.0.0.25.
      • [AER-6361] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item. Fixed in version 5.0.0.25.
      • [AER-6350] - (XDR) If a DC is dynamically removed and another added, handling of authentication configuration items may cause a double-free. Fixed in version 5.0.0.23.
      • [AER-6341] - (XDR) Source node may fail to discover the entire destination cluster when destination nodes restart. Fixed in version 5.0.0.22.

    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-6325] - (XDR) DCs with connector true do not properly disconnect when all namespaces are dynamically removed.

  • 5.0.0.17
    Release Date: October 31, 2020
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0.
      • Aerospike Server version 5.0 will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.

    Known Issues

    • Enterprise & Community
      • [AER-6340] - (KVS) HLL string or blob elements sized 31 to 254 bytes may be treated differently depending on msgpack standard. 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-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 5.0.0.30.
      • [AER-6402] - (SINDEX) When iterating through secondary indexes to adjust for changing list bin values, inactive indexes are incorrectly skipped, which may cause a crash. Fixed in version 5.0.0.30.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 5.0.0.28.
      • [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.0.0.21.
      • [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.0.0.18.
    • Enterprise Only
      • [AER-6413] - (SECURITY) Small memory leak during LDAP login process. Fixed in version 5.0.0.33.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.0.0.33.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 5.0.0.29.
      • [AER-6382] - (SECURITY) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 5.0.0.28.
      • [AER-6381] - (XDR) If a record expires between XDR reading and shipping, improper TTL will be shipped. Fixed in version 5.0.0.28.
      • [AER-6376] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 5.0.0.27.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 5.0.0.27.
      • [AER-6366] - (XDR) Dynamically removing a connector seed node may cause a crash. Fixed in version 5.0.0.26.
      • [AER-6369] - (XDR) When shipping the first record on a connection, if all bins are filtered out, a crash may result. Fixed in version 5.0.0.26.
      • [AER-6363] - (KVS) A write or a UDF that deletes all of a record's bins may result in a tombstone with a non-zero void-time. Fixed in version 5.0.0.25.
      • [AER-6361] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item. Fixed in version 5.0.0.25.
      • [AER-6350] - (XDR) If a DC is dynamically removed and another added, handling of authentication configuration items may cause a double-free. Fixed in version 5.0.0.23.
      • [AER-6341] - (XDR) Source node may fail to discover the entire destination cluster when destination nodes restart. Fixed in version 5.0.0.22.
      • [AER-6325] - (XDR) DCs with connector true do not properly disconnect when all namespaces are dynamically removed. Fixed in version 5.0.0.18.

    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.

  • 5.0.0.16
    Release Date: October 21, 2020
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0.
      • Aerospike Server version 5.0 will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.

    Known Issues

    • Enterprise & Community
      • [AER-6340] - (KVS) HLL string or blob elements sized 31 to 254 bytes may be treated differently depending on msgpack standard. 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-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 5.0.0.30.
      • [AER-6402] - (SINDEX) When iterating through secondary indexes to adjust for changing list bin values, inactive indexes are incorrectly skipped, which may cause a crash. Fixed in version 5.0.0.30.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 5.0.0.28.
      • [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.0.0.21.
      • [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.0.0.18.
    • Enterprise Only
      • [AER-6413] - (SECURITY) Small memory leak during LDAP login process. Fixed in version 5.0.0.33.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.0.0.33.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 5.0.0.29.
      • [AER-6382] - (SECURITY) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 5.0.0.28.
      • [AER-6381] - (XDR) If a record expires between XDR reading and shipping, improper TTL will be shipped. Fixed in version 5.0.0.28.
      • [AER-6376] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 5.0.0.27.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 5.0.0.27.
      • [AER-6366] - (XDR) Dynamically removing a connector seed node may cause a crash. Fixed in version 5.0.0.26.
      • [AER-6369] - (XDR) When shipping the first record on a connection, if all bins are filtered out, a crash may result. Fixed in version 5.0.0.26.
      • [AER-6363] - (KVS) A write or a UDF that deletes all of a record's bins may result in a tombstone with a non-zero void-time. Fixed in version 5.0.0.25.
      • [AER-6361] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item. Fixed in version 5.0.0.25.
      • [AER-6350] - (XDR) If a DC is dynamically removed and another added, handling of authentication configuration items may cause a double-free. Fixed in version 5.0.0.23.
      • [AER-6341] - (XDR) Source node may fail to discover the entire destination cluster when destination nodes restart. Fixed in version 5.0.0.22.
      • [AER-6325] - (XDR) DCs with connector true do not properly disconnect when all namespaces are dynamically removed. Fixed in version 5.0.0.18.
      • [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.0.0.17.

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

  • 5.0.0.15
    Release Date: October 14, 2020
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0.
      • Aerospike Server version 5.0 will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.

    Known Issues

    • Enterprise & Community
      • [AER-6340] - (KVS) HLL string or blob elements sized 31 to 254 bytes may be treated differently depending on msgpack standard. 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-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 5.0.0.30.
      • [AER-6402] - (SINDEX) When iterating through secondary indexes to adjust for changing list bin values, inactive indexes are incorrectly skipped, which may cause a crash. Fixed in version 5.0.0.30.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 5.0.0.28.
      • [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.0.0.21.
      • [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.0.0.18.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 5.0.0.16.
    • Enterprise Only
      • [AER-6413] - (SECURITY) Small memory leak during LDAP login process. Fixed in version 5.0.0.33.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.0.0.33.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 5.0.0.29.
      • [AER-6382] - (SECURITY) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 5.0.0.28.
      • [AER-6381] - (XDR) If a record expires between XDR reading and shipping, improper TTL will be shipped. Fixed in version 5.0.0.28.
      • [AER-6376] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 5.0.0.27.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 5.0.0.27.
      • [AER-6366] - (XDR) Dynamically removing a connector seed node may cause a crash. Fixed in version 5.0.0.26.
      • [AER-6369] - (XDR) When shipping the first record on a connection, if all bins are filtered out, a crash may result. Fixed in version 5.0.0.26.
      • [AER-6363] - (KVS) A write or a UDF that deletes all of a record's bins may result in a tombstone with a non-zero void-time. Fixed in version 5.0.0.25.
      • [AER-6361] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item. Fixed in version 5.0.0.25.
      • [AER-6350] - (XDR) If a DC is dynamically removed and another added, handling of authentication configuration items may cause a double-free. Fixed in version 5.0.0.23.
      • [AER-6341] - (XDR) Source node may fail to discover the entire destination cluster when destination nodes restart. Fixed in version 5.0.0.22.
      • [AER-6325] - (XDR) DCs with connector true do not properly disconnect when all namespaces are dynamically removed. Fixed in version 5.0.0.18.
      • [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.0.0.17.
      • [AER-6313] - (XDR) Small memory leak when XDR client connects to seed node. Fixed in version 5.0.0.16.

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

  • 5.0.0.13
    Release Date: September 18, 2020
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0.
      • Aerospike Server version 5.0 will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.

    Known Issues

    • Enterprise & Community
      • [AER-6340] - (KVS) HLL string or blob elements sized 31 to 254 bytes may be treated differently depending on msgpack standard. 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-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 5.0.0.30.
      • [AER-6402] - (SINDEX) When iterating through secondary indexes to adjust for changing list bin values, inactive indexes are incorrectly skipped, which may cause a crash. Fixed in version 5.0.0.30.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 5.0.0.28.
      • [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.0.0.21.
      • [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.0.0.18.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 5.0.0.16.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 5.0.0.15.
      • [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.0.0.15.
    • Enterprise Only
      • [AER-6413] - (SECURITY) Small memory leak during LDAP login process. Fixed in version 5.0.0.33.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.0.0.33.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 5.0.0.29.
      • [AER-6382] - (SECURITY) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 5.0.0.28.
      • [AER-6381] - (XDR) If a record expires between XDR reading and shipping, improper TTL will be shipped. Fixed in version 5.0.0.28.
      • [AER-6376] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 5.0.0.27.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 5.0.0.27.
      • [AER-6366] - (XDR) Dynamically removing a connector seed node may cause a crash. Fixed in version 5.0.0.26.
      • [AER-6369] - (XDR) When shipping the first record on a connection, if all bins are filtered out, a crash may result. Fixed in version 5.0.0.26.
      • [AER-6363] - (KVS) A write or a UDF that deletes all of a record's bins may result in a tombstone with a non-zero void-time. Fixed in version 5.0.0.25.
      • [AER-6361] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item. Fixed in version 5.0.0.25.
      • [AER-6350] - (XDR) If a DC is dynamically removed and another added, handling of authentication configuration items may cause a double-free. Fixed in version 5.0.0.23.
      • [AER-6341] - (XDR) Source node may fail to discover the entire destination cluster when destination nodes restart. Fixed in version 5.0.0.22.
      • [AER-6325] - (XDR) DCs with connector true do not properly disconnect when all namespaces are dynamically removed. Fixed in version 5.0.0.18.
      • [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.0.0.17.
      • [AER-6313] - (XDR) Small memory leak when XDR client connects to seed node. Fixed in version 5.0.0.16.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 5.0.0.15.
      • [AER-6302] - (XDR) Namespace context configuration item xdr-tomb-raider-period cannot be set using time units. Fixed in version 5.0.0.15.
      • [AER-6310] - (XDR) When connection to seed node fails, TLS name will be double freed and may cause a crash. Fixed in version 5.0.0.15.

    Improvements

    • Enterprise & Community
    • Enterprise Only
      • [AER-6288] - (XDR) Keep the last ship time of non-owned partitions relatively current.

    Bug Fixes

    • Enterprise & Community
      • [AER-6289] - (KVS) Concurrently reading and writing a new bin or set name may access a pointer which crosses a cache line boundary, causing a crash.
    • Enterprise Only
      • [AER-6287] - (KVS) When writing over a tombstone with Time-To-Live (TTL) value -2 (i.e. do not update TTL), the write fails to apply the namespace default-ttl.

  • 5.0.0.11
    Release Date: August 5, 2020
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0.
      • Aerospike Server version 5.0 will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.

    Known Issues

    • Enterprise & Community
      • [AER-6340] - (KVS) HLL string or blob elements sized 31 to 254 bytes may be treated differently depending on msgpack standard. 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-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 5.0.0.30.
      • [AER-6402] - (SINDEX) When iterating through secondary indexes to adjust for changing list bin values, inactive indexes are incorrectly skipped, which may cause a crash. Fixed in version 5.0.0.30.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 5.0.0.28.
      • [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.0.0.21.
      • [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.0.0.18.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 5.0.0.16.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 5.0.0.15.
      • [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.0.0.15.
      • [AER-6289] - (KVS) Concurrently reading and writing a new bin or set name may access a pointer which crosses a cache line boundary, causing a crash. Fixed in version 5.0.0.13.
    • Enterprise Only
      • [AER-6413] - (SECURITY) Small memory leak during LDAP login process. Fixed in version 5.0.0.33.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.0.0.33.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 5.0.0.29.
      • [AER-6382] - (SECURITY) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 5.0.0.28.
      • [AER-6381] - (XDR) If a record expires between XDR reading and shipping, improper TTL will be shipped. Fixed in version 5.0.0.28.
      • [AER-6376] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 5.0.0.27.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 5.0.0.27.
      • [AER-6366] - (XDR) Dynamically removing a connector seed node may cause a crash. Fixed in version 5.0.0.26.
      • [AER-6369] - (XDR) When shipping the first record on a connection, if all bins are filtered out, a crash may result. Fixed in version 5.0.0.26.
      • [AER-6363] - (KVS) A write or a UDF that deletes all of a record's bins may result in a tombstone with a non-zero void-time. Fixed in version 5.0.0.25.
      • [AER-6361] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item. Fixed in version 5.0.0.25.
      • [AER-6350] - (XDR) If a DC is dynamically removed and another added, handling of authentication configuration items may cause a double-free. Fixed in version 5.0.0.23.
      • [AER-6341] - (XDR) Source node may fail to discover the entire destination cluster when destination nodes restart. Fixed in version 5.0.0.22.
      • [AER-6325] - (XDR) DCs with connector true do not properly disconnect when all namespaces are dynamically removed. Fixed in version 5.0.0.18.
      • [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.0.0.17.
      • [AER-6313] - (XDR) Small memory leak when XDR client connects to seed node. Fixed in version 5.0.0.16.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 5.0.0.15.
      • [AER-6302] - (XDR) Namespace context configuration item xdr-tomb-raider-period cannot be set using time units. Fixed in version 5.0.0.15.
      • [AER-6310] - (XDR) When connection to seed node fails, TLS name will be double freed and may cause a crash. Fixed in version 5.0.0.15.
      • [AER-6287] - (KVS) When writing over a tombstone with Time-To-Live (TTL) value -2 (i.e. do not update TTL), the write fails to apply the namespace default-ttl. Fixed in version 5.0.0.13.

    Bug Fixes

    • Enterprise Only
      • [AER-6269] - (XDR) Setting DC context configuration item auth-password-file while connected to DC may cause a crash.
      • [AER-6270] - (XDR) If dynamically adding a DC, configuring a TLS spec containing a key-file without a required key-file-password will cause a crash.

  • 5.0.0.10
    Release Date: July 14, 2020
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0.
      • Aerospike Server version 5.0 will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.

    Known Issues

    • Enterprise & Community
      • [AER-6340] - (KVS) HLL string or blob elements sized 31 to 254 bytes may be treated differently depending on msgpack standard. 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-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 5.0.0.30.
      • [AER-6402] - (SINDEX) When iterating through secondary indexes to adjust for changing list bin values, inactive indexes are incorrectly skipped, which may cause a crash. Fixed in version 5.0.0.30.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 5.0.0.28.
      • [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.0.0.21.
      • [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.0.0.18.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 5.0.0.16.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 5.0.0.15.
      • [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.0.0.15.
      • [AER-6289] - (KVS) Concurrently reading and writing a new bin or set name may access a pointer which crosses a cache line boundary, causing a crash. Fixed in version 5.0.0.13.
    • Enterprise Only
      • [AER-6413] - (SECURITY) Small memory leak during LDAP login process. Fixed in version 5.0.0.33.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.0.0.33.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 5.0.0.29.
      • [AER-6382] - (SECURITY) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 5.0.0.28.
      • [AER-6381] - (XDR) If a record expires between XDR reading and shipping, improper TTL will be shipped. Fixed in version 5.0.0.28.
      • [AER-6376] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 5.0.0.27.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 5.0.0.27.
      • [AER-6366] - (XDR) Dynamically removing a connector seed node may cause a crash. Fixed in version 5.0.0.26.
      • [AER-6369] - (XDR) When shipping the first record on a connection, if all bins are filtered out, a crash may result. Fixed in version 5.0.0.26.
      • [AER-6363] - (KVS) A write or a UDF that deletes all of a record's bins may result in a tombstone with a non-zero void-time. Fixed in version 5.0.0.25.
      • [AER-6361] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item. Fixed in version 5.0.0.25.
      • [AER-6350] - (XDR) If a DC is dynamically removed and another added, handling of authentication configuration items may cause a double-free. Fixed in version 5.0.0.23.
      • [AER-6341] - (XDR) Source node may fail to discover the entire destination cluster when destination nodes restart. Fixed in version 5.0.0.22.
      • [AER-6325] - (XDR) DCs with connector true do not properly disconnect when all namespaces are dynamically removed. Fixed in version 5.0.0.18.
      • [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.0.0.17.
      • [AER-6313] - (XDR) Small memory leak when XDR client connects to seed node. Fixed in version 5.0.0.16.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 5.0.0.15.
      • [AER-6302] - (XDR) Namespace context configuration item xdr-tomb-raider-period cannot be set using time units. Fixed in version 5.0.0.15.
      • [AER-6310] - (XDR) When connection to seed node fails, TLS name will be double freed and may cause a crash. Fixed in version 5.0.0.15.
      • [AER-6287] - (KVS) When writing over a tombstone with Time-To-Live (TTL) value -2 (i.e. do not update TTL), the write fails to apply the namespace default-ttl. Fixed in version 5.0.0.13.
      • [AER-6269] - (XDR) Setting DC context configuration item auth-password-file while connected to DC may cause a crash. Fixed in version 5.0.0.11.
      • [AER-6270] - (XDR) If dynamically adding a DC, configuring a TLS specification containing a key-file without a required key-file-password will cause a crash. Fixed in version 5.0.0.11.

    Bug Fixes

    • Enterprise Only
      • [AER-6258] - (XDR) For low or intermittent load, a race may cause unnecessary timeouts.
      • [AER-6259] - (XDR) When visibility of remote DC is lost, race between shipping and reconnection may cause an assertion.

  • 5.0.0.9
    Release Date: July 7, 2020
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0.
      • Aerospike Server version 5.0 will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.

    Known Issues

    • Enterprise & Community
      • [AER-6340] - (KVS) HLL string or blob elements sized 31 to 254 bytes may be treated differently depending on msgpack standard. 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-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 5.0.0.30.
      • [AER-6402] - (SINDEX) When iterating through secondary indexes to adjust for changing list bin values, inactive indexes are incorrectly skipped, which may cause a crash. Fixed in version 5.0.0.30.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 5.0.0.28.
      • [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.0.0.21.
      • [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.0.0.18.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 5.0.0.16.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 5.0.0.15.
      • [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.0.0.15.
      • [AER-6289] - (KVS) Concurrently reading and writing a new bin or set name may access a pointer which crosses a cache line boundary, causing a crash. Fixed in version 5.0.0.13.
    • Enterprise Only
      • [AER-6413] - (SECURITY) Small memory leak during LDAP login process. Fixed in version 5.0.0.33.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.0.0.33.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 5.0.0.29.
      • [AER-6382] - (SECURITY) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 5.0.0.28.
      • [AER-6381] - (XDR) If a record expires between XDR reading and shipping, improper TTL will be shipped. Fixed in version 5.0.0.28.
      • [AER-6376] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 5.0.0.27.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 5.0.0.27.
      • [AER-6366] - (XDR) Dynamically removing a connector seed node may cause a crash. Fixed in version 5.0.0.26.
      • [AER-6369] - (XDR) When shipping the first record on a connection, if all bins are filtered out, a crash may result. Fixed in version 5.0.0.26.
      • [AER-6363] - (KVS) A write or a UDF that deletes all of a record's bins may result in a tombstone with a non-zero void-time. Fixed in version 5.0.0.25.
      • [AER-6361] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item. Fixed in version 5.0.0.25.
      • [AER-6350] - (XDR) If a DC is dynamically removed and another added, handling of authentication configuration items may cause a double-free. Fixed in version 5.0.0.23.
      • [AER-6341] - (XDR) Source node may fail to discover the entire destination cluster when destination nodes restart. Fixed in version 5.0.0.22.
      • [AER-6325] - (XDR) DCs with connector true do not properly disconnect when all namespaces are dynamically removed. Fixed in version 5.0.0.18.
      • [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.0.0.17.
      • [AER-6313] - (XDR) Small memory leak when XDR client connects to seed node. Fixed in version 5.0.0.16.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 5.0.0.15.
      • [AER-6302] - (XDR) Namespace context configuration item xdr-tomb-raider-period cannot be set using time units. Fixed in version 5.0.0.15.
      • [AER-6310] - (XDR) When connection to seed node fails, TLS name will be double freed and may cause a crash. Fixed in version 5.0.0.15.
      • [AER-6287] - (KVS) When writing over a tombstone with Time-To-Live (TTL) value -2 (i.e. do not update TTL), the write fails to apply the namespace default-ttl. Fixed in version 5.0.0.13.
      • [AER-6269] - (XDR) Setting DC context configuration item auth-password-file while connected to DC may cause a crash. Fixed in version 5.0.0.11.
      • [AER-6270] - (XDR) If dynamically adding a DC, configuring a TLS specification containing a key-file without a required key-file-password will cause a crash. Fixed in version 5.0.0.11.
      • [AER-6258] - (XDR) For low or intermittent load, a race may cause unnecessary timeouts. Fixed in version 5.0.0.10.
      • [AER-6259] - (XDR) When visibility of remote DC is lost, race between shipping and reconnection may cause an assertion. Fixed in version 5.0.0.10.

    Bug Fixes

    • Enterprise & Community
      • [AER-6251] - (UDF) When a record UDF does not pass a predicate expression metadata filter, the server will deadlock.
    • Enterprise Only
      • [AER-6250] - (UDF) Race between a background UDF scan/query internal transaction and a durable delete may cause a deadlock.

  • 5.0.0.8
    Release Date: June 25, 2020
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0.
      • Aerospike Server version 5.0 will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • XDR, using ACL, in server versions between 4.1.0.1 and 4.3.0.6 cannot ship to this version. The simplest workaround is to avoid using those versions.

    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-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 5.0.0.30.
      • [AER-6402] - (SINDEX) When iterating through secondary indexes to adjust for changing list bin values, inactive indexes are incorrectly skipped, which may cause a crash. Fixed in version 5.0.0.30.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 5.0.0.28.
      • [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.0.0.21.
      • [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.0.0.18.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 5.0.0.16.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 5.0.0.15.
      • [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.0.0.15.
      • [AER-6289] - (KVS) Concurrently reading and writing a new bin or set name may access a pointer which crosses a cache line boundary, causing a crash. Fixed in version 5.0.0.13.
      • [AER-6251] - (UDF) When a record UDF does not pass a predicate expression metadata filter, the server will deadlock. Fixed in version 5.0.0.9.
    • Enterprise Only
      • [AER-6413] - (SECURITY) Small memory leak during LDAP login process. Fixed in version 5.0.0.33.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.0.0.33.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 5.0.0.29.
      • [AER-6382] - (SECURITY) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 5.0.0.28.
      • [AER-6381] - (XDR) If a record expires between XDR reading and shipping, improper TTL will be shipped. Fixed in version 5.0.0.28.
      • [AER-6376] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 5.0.0.27.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 5.0.0.27.
      • [AER-6366] - (XDR) Dynamically removing a connector seed node may cause a crash. Fixed in version 5.0.0.26.
      • [AER-6369] - (XDR) When shipping the first record on a connection, if all bins are filtered out, a crash may result. Fixed in version 5.0.0.26.
      • [AER-6363] - (KVS) A write or a UDF that deletes all of a record's bins may result in a tombstone with a non-zero void-time. Fixed in version 5.0.0.25.
      • [AER-6361] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item. Fixed in version 5.0.0.25.
      • [AER-6350] - (XDR) If a DC is dynamically removed and another added, handling of authentication configuration items may cause a double-free. Fixed in version 5.0.0.23.
      • [AER-6341] - (XDR) Source node may fail to discover the entire destination cluster when destination nodes restart. Fixed in version 5.0.0.22.
      • [AER-6325] - (XDR) DCs with connector true do not properly disconnect when all namespaces are dynamically removed. Fixed in version 5.0.0.18.
      • [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.0.0.17.
      • [AER-6313] - (XDR) Small memory leak when XDR client connects to seed node. Fixed in version 5.0.0.16.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 5.0.0.15.
      • [AER-6302] - (XDR) Namespace context configuration item xdr-tomb-raider-period cannot be set using time units. Fixed in version 5.0.0.15.
      • [AER-6310] - (XDR) When connection to seed node fails, TLS name will be double freed and may cause a crash. Fixed in version 5.0.0.15.
      • [AER-6287] - (KVS) When writing over a tombstone with Time-To-Live (TTL) value -2 (i.e. do not update TTL), the write fails to apply the namespace default-ttl. Fixed in version 5.0.0.13.
      • [AER-6269] - (XDR) Setting DC context configuration item auth-password-file while connected to DC may cause a crash. Fixed in version 5.0.0.11.
      • [AER-6270] - (XDR) If dynamically adding a DC, configuring a TLS specification containing a key-file without a required key-file-password will cause a crash. Fixed in version 5.0.0.11.
      • [AER-6258] - (XDR) For low or intermittent load, a race may cause unnecessary timeouts. Fixed in version 5.0.0.10.
      • [AER-6259] - (XDR) When visibility of remote DC is lost, race between shipping and reconnection may cause an assertion. Fixed in version 5.0.0.10.
      • [AER-6250] - (UDF) Race between a background UDF scan/query internal transaction and a durable delete may cause a deadlock. Fixed in version 5.0.0.9.

    Bug Fixes

    • Enterprise Only
      • [AER-6248] - (XDR) Wrong node may be selected when connecting, resulting in bad load balance (connectors) or proxies (Aerospike destinations).

  • 5.0.0.7
    Release Date: June 18, 2020
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0.
      • Aerospike Server version 5.0 will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • XDR, using ACL, in server versions between 4.1.0.1 and 4.3.0.6 cannot ship to this version. The simplest workaround is to avoid using those versions.

    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-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 5.0.0.30.
      • [AER-6402] - (SINDEX) When iterating through secondary indexes to adjust for changing list bin values, inactive indexes are incorrectly skipped, which may cause a crash. Fixed in version 5.0.0.30.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 5.0.0.28.
      • [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.0.0.21.
      • [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.0.0.18.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 5.0.0.16.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 5.0.0.15.
      • [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.0.0.15.
      • [AER-6289] - (KVS) Concurrently reading and writing a new bin or set name may access a pointer which crosses a cache line boundary, causing a crash. Fixed in version 5.0.0.13.
      • [AER-6251] - (UDF) When a record UDF does not pass a predicate expression metadata filter, the server will deadlock. Fixed in version 5.0.0.9.
    • Enterprise Only
      • [AER-6413] - (SECURITY) Small memory leak during LDAP login process. Fixed in version 5.0.0.33.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.0.0.33.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 5.0.0.29.
      • [AER-6382] - (SECURITY) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 5.0.0.28.
      • [AER-6381] - (XDR) If a record expires between XDR reading and shipping, improper TTL will be shipped. Fixed in version 5.0.0.28.
      • [AER-6376] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 5.0.0.27.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 5.0.0.27.
      • [AER-6366] - (XDR) Dynamically removing a connector seed node may cause a crash. Fixed in version 5.0.0.26.
      • [AER-6369] - (XDR) When shipping the first record on a connection, if all bins are filtered out, a crash may result. Fixed in version 5.0.0.26.
      • [AER-6363] - (KVS) A write or a UDF that deletes all of a record's bins may result in a tombstone with a non-zero void-time. Fixed in version 5.0.0.25.
      • [AER-6361] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item. Fixed in version 5.0.0.25.
      • [AER-6350] - (XDR) If a DC is dynamically removed and another added, handling of authentication configuration items may cause a double-free. Fixed in version 5.0.0.23.
      • [AER-6341] - (XDR) Source node may fail to discover the entire destination cluster when destination nodes restart. Fixed in version 5.0.0.22.
      • [AER-6325] - (XDR) DCs with connector true do not properly disconnect when all namespaces are dynamically removed. Fixed in version 5.0.0.18.
      • [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.0.0.17.
      • [AER-6313] - (XDR) Small memory leak when XDR client connects to seed node. Fixed in version 5.0.0.16.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 5.0.0.15.
      • [AER-6302] - (XDR) Namespace context configuration item xdr-tomb-raider-period cannot be set using time units. Fixed in version 5.0.0.15.
      • [AER-6310] - (XDR) When connection to seed node fails, TLS name will be double freed and may cause a crash. Fixed in version 5.0.0.15.
      • [AER-6287] - (KVS) When writing over a tombstone with Time-To-Live (TTL) value -2 (i.e. do not update TTL), the write fails to apply the namespace default-ttl. Fixed in version 5.0.0.13.
      • [AER-6269] - (XDR) Setting DC context configuration item auth-password-file while connected to DC may cause a crash. Fixed in version 5.0.0.11.
      • [AER-6270] - (XDR) If dynamically adding a DC, configuring a TLS specification containing a key-file without a required key-file-password will cause a crash. Fixed in version 5.0.0.11.
      • [AER-6258] - (XDR) For low or intermittent load, a race may cause unnecessary timeouts. Fixed in version 5.0.0.10.
      • [AER-6259] - (XDR) When visibility of remote DC is lost, race between shipping and reconnection may cause an assertion. Fixed in version 5.0.0.10.
      • [AER-6250] - (UDF) Race between a background UDF scan/query internal transaction and a durable delete may cause a deadlock. Fixed in version 5.0.0.9.
      • [AER-6248] - (XDR) When connecting, race may cause the wrong node to be selected. Fixed in version 5.0.0.8.

    Improvements

    • Enterprise & Community
      • [AER-6238] - (UDF) Added service context configuration item disable-udf-execution as a mitigation option for Lua security vulnerabilities.

    Bug Fixes

    • Enterprise & Community
      • [AER-6239] - (INFO) Invalid log-set command parameters may cause a crash.
    • Enterprise Only
      • [AER-6235] - (XDR) If DC context configuration item tls-name is not set, a TLS name in DC context configuration item node-address-port will cause a crash.
      • [AER-6236] - (XDR) DC throughput stat is always zero when retrieved via info command.
      • [AER-6237] - (XDR) Rare race between replication and migration may cause XDR submission at replica to fail.

  • 5.0.0.4
    Release Date: May 21, 2020
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0.
      • Aerospike Server version 5.0 will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • XDR, using ACL, in server versions between 4.1.0.1 and 4.3.0.6 cannot ship to this version. The simplest workaround is to avoid using those versions.
    • Please reach out to your account representative if you are interested in Kerberos support.

    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-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 5.0.0.30.
      • [AER-6402] - (SINDEX) When iterating through secondary indexes to adjust for changing list bin values, inactive indexes are incorrectly skipped, which may cause a crash. Fixed in version 5.0.0.30.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 5.0.0.28.
      • [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.0.0.21.
      • [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.0.0.18.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 5.0.0.16.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 5.0.0.15.
      • [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.0.0.15.
      • [AER-6289] - (KVS) Concurrently reading and writing a new bin or set name may access a pointer which crosses a cache line boundary, causing a crash. Fixed in version 5.0.0.13.
      • [AER-6251] - (UDF) When a record UDF does not pass a predicate expression metadata filter, the server will deadlock. Fixed in version 5.0.0.9.
      • [AER-6239] - (INFO) Invalid log-set command parameters may cause a crash. Fixed in version 5.0.0.7.
    • Enterprise Only
      • [AER-6413] - (SECURITY) Small memory leak during LDAP login process. Fixed in version 5.0.0.33.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.0.0.33.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 5.0.0.29.
      • [AER-6382] - (SECURITY) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 5.0.0.28.
      • [AER-6381] - (XDR) If a record expires between XDR reading and shipping, improper TTL will be shipped. Fixed in version 5.0.0.28.
      • [AER-6376] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 5.0.0.27.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 5.0.0.27.
      • [AER-6366] - (XDR) Dynamically removing a connector seed node may cause a crash. Fixed in version 5.0.0.26.
      • [AER-6369] - (XDR) When shipping the first record on a connection, if all bins are filtered out, a crash may result. Fixed in version 5.0.0.26.
      • [AER-6363] - (KVS) A write or a UDF that deletes all of a record's bins may result in a tombstone with a non-zero void-time. Fixed in version 5.0.0.25.
      • [AER-6361] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item. Fixed in version 5.0.0.25.
      • [AER-6350] - (XDR) If a DC is dynamically removed and another added, handling of authentication configuration items may cause a double-free. Fixed in version 5.0.0.23.
      • [AER-6341] - (XDR) Source node may fail to discover the entire destination cluster when destination nodes restart. Fixed in version 5.0.0.22.
      • [AER-6325] - (XDR) DCs with connector true do not properly disconnect when all namespaces are dynamically removed. Fixed in version 5.0.0.18.
      • [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.0.0.17.
      • [AER-6313] - (XDR) Small memory leak when XDR client connects to seed node. Fixed in version 5.0.0.16.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 5.0.0.15.
      • [AER-6302] - (XDR) Namespace context configuration item xdr-tomb-raider-period cannot be set using time units. Fixed in version 5.0.0.15.
      • [AER-6310] - (XDR) When connection to seed node fails, TLS name will be double freed and may cause a crash. Fixed in version 5.0.0.15.
      • [AER-6287] - (KVS) When writing over a tombstone with Time-To-Live (TTL) value -2 (i.e. do not update TTL), the write fails to apply the namespace default-ttl. Fixed in version 5.0.0.13.
      • [AER-6269] - (XDR) Setting DC context configuration item auth-password-file while connected to DC may cause a crash. Fixed in version 5.0.0.11.
      • [AER-6270] - (XDR) If dynamically adding a DC, configuring a TLS specification containing a key-file without a required key-file-password will cause a crash. Fixed in version 5.0.0.11.
      • [AER-6258] - (XDR) For low or intermittent load, a race may cause unnecessary timeouts. Fixed in version 5.0.0.10.
      • [AER-6259] - (XDR) When visibility of remote DC is lost, race between shipping and reconnection may cause an assertion. Fixed in version 5.0.0.10.
      • [AER-6250] - (UDF) Race between a background UDF scan/query internal transaction and a durable delete may cause a deadlock. Fixed in version 5.0.0.9.
      • [AER-6248] - (XDR) When connecting, race may cause the wrong node to be selected. Fixed in version 5.0.0.8.
      • [AER-6235] - (XDR) If DC context configuration item tls-name is not set, a TLS name in DC context configuration item node-address-port will cause a crash. Fixed in version 5.0.0.7.
      • [AER-6236] - (XDR) DC throughput stat is always zero when retrieved via info command. Fixed in version 5.0.0.7.
      • [AER-6237] - (XDR) Rare race between replication and migration may cause XDR submission at replica to fail. Fixed in version 5.0.0.7.

    Improvements

    • Enterprise Only
      • [AER-6231] - (XDR) Avoid sending redundant XDR information during replication.

    Bug Fixes

    • Enterprise & Community
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated.

  • 5.0.0.3
    Release Date: May 14, 2020
    • If using XDR, it is strongly advised to upgrade to version 5.0.0.4 or above. Refer to AER-6231 and the 5.0.0.4 release notes for details.
    • The Cross-Datacenter Replication (XDR) feature has been redesigned for improvements in speed and simplicity. Refer to:
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0.
      • Aerospike Server version 5.0 will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • The maximum cluster size is now increased to 256 nodes. However, the actual limit when using multicast heartbeat mode will depend on the Maximum Transmission Unit (MTU).
      • There is a 132 node limit with MTU of 1500. A 256 node limit can be achieved with an MTU of 9000.
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • XDR, using ACL, in server versions between 4.1.0.1 and 4.3.0.6 cannot ship to this version. The simplest workaround is to avoid using those versions.
    • Community Edition clusters now limit the maximum amount of data to 5TB of unique data. Refer to:
    • Please reach out to your account representative if you are interested in Kerberos support.

    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-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 5.0.0.30.
      • [AER-6402] - (SINDEX) When iterating through secondary indexes to adjust for changing list bin values, inactive indexes are incorrectly skipped, which may cause a crash. Fixed in version 5.0.0.30.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 5.0.0.28.
      • [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.0.0.21.
      • [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.0.0.18.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 5.0.0.16.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 5.0.0.15.
      • [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.0.0.15.
      • [AER-6289] - (KVS) Concurrently reading and writing a new bin or set name may access a pointer which crosses a cache line boundary, causing a crash. Fixed in version 5.0.0.13.
      • [AER-6251] - (UDF) When a record UDF does not pass a predicate expression metadata filter, the server will deadlock. Fixed in version 5.0.0.9.
      • [AER-6239] - (INFO) Invalid log-set command parameters may cause a crash. Fixed in version 5.0.0.7.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 5.0.0.4.
    • Enterprise Only
      • [AER-6413] - (SECURITY) Small memory leak during LDAP login process. Fixed in version 5.0.0.33.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash. Fixed in version 5.0.0.33.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 5.0.0.29.
      • [AER-6382] - (SECURITY) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 5.0.0.28.
      • [AER-6381] - (XDR) If a record expires between XDR reading and shipping, improper TTL will be shipped. Fixed in version 5.0.0.28.
      • [AER-6376] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 5.0.0.27.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 5.0.0.27.
      • [AER-6366] - (XDR) Dynamically removing a connector seed node may cause a crash. Fixed in version 5.0.0.26.
      • [AER-6369] - (XDR) When shipping the first record on a connection, if all bins are filtered out, a crash may result. Fixed in version 5.0.0.26.
      • [AER-6363] - (KVS) A write or a UDF that deletes all of a record's bins may result in a tombstone with a non-zero void-time. Fixed in version 5.0.0.25.
      • [AER-6361] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item. Fixed in version 5.0.0.25.
      • [AER-6350] - (XDR) If a DC is dynamically removed and another added, handling of authentication configuration items may cause a double-free. Fixed in version 5.0.0.23.
      • [AER-6341] - (XDR) Source node may fail to discover the entire destination cluster when destination nodes restart. Fixed in version 5.0.0.22.
      • [AER-6325] - (XDR) DCs with connector true do not properly disconnect when all namespaces are dynamically removed. Fixed in version 5.0.0.18.
      • [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.0.0.17.
      • [AER-6313] - (XDR) Small memory leak when XDR client connects to seed node. Fixed in version 5.0.0.16.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 5.0.0.15.
      • [AER-6302] - (XDR) Namespace context configuration item xdr-tomb-raider-period cannot be set using time units. Fixed in version 5.0.0.15.
      • [AER-6310] - (XDR) When connection to seed node fails, TLS name will be double freed and may cause a crash. Fixed in version 5.0.0.15.
      • [AER-6287] - (KVS) When writing over a tombstone with Time-To-Live (TTL) value -2 (i.e. do not update TTL), the write fails to apply the namespace default-ttl. Fixed in version 5.0.0.13.
      • [AER-6269] - (XDR) Setting DC context configuration item auth-password-file while connected to DC may cause a crash. Fixed in version 5.0.0.11.
      • [AER-6270] - (XDR) If dynamically adding a DC, configuring a TLS specification containing a key-file without a required key-file-password will cause a crash. Fixed in version 5.0.0.11.
      • [AER-6258] - (XDR) For low or intermittent load, a race may cause unnecessary timeouts. Fixed in version 5.0.0.10.
      • [AER-6259] - (XDR) When visibility of remote DC is lost, race between shipping and reconnection may cause an assertion. Fixed in version 5.0.0.10.
      • [AER-6250] - (UDF) Race between a background UDF scan/query internal transaction and a durable delete may cause a deadlock. Fixed in version 5.0.0.9.
      • [AER-6248] - (XDR) When connecting, race may cause the wrong node to be selected. Fixed in version 5.0.0.8.
      • [AER-6235] - (XDR) If DC context configuration item tls-name is not set, a TLS name in DC context configuration item node-address-port will cause a crash. Fixed in version 5.0.0.7.
      • [AER-6236] - (XDR) DC throughput stat is always zero when retrieved via info command. Fixed in version 5.0.0.7.
      • [AER-6237] - (XDR) Rare race between replication and migration may cause XDR submission at replica to fail. Fixed in version 5.0.0.7.

    New Features

    • Community Only
      • [AER-6226] - (DEPLOYMENT) Limited Community Edition clusters to 5TB of unique data.

    Improvements

    • Enterprise & Community
      • [AER-6202] - (KVS) Increased maximum supported configuration file line length to 1024 characters.
      • [AER-6217] - (KVS) Increased bin_names_quota to 65535.
      • [AER-6218] - (KVS) Service context configuration item proto-fd-max may now be dynamically set as high as the system's current process file descriptor limit.
      • [AER-6219] - (KVS) Removed support for very old clients that sent key without digest.
      • [AER-6222] - (KVS) Do not start the server if the configuration file contains obsolete items.
      • [AER-6221] - (LOGGING) Streamlined cold start storage load ticker logging.
    • Enterprise Only
      • [AER-6225] - (DEPLOYMENT) Increased maximum cluster size to 256.
      • [AER-6200] - (XDR) Redesigned XDR system, including significant changes to configuration and statistics.

    Updates

  • 4.9.0.30
    Release Date: March 29, 2021

    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).
      • Record bins containing (Complex Data Type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.

    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] - (SECURITY) Small memory leak during LDAP login process.

  • 4.9.0.28
    Release Date: March 12, 2021

    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).
      • Record bins containing (Complex Data Type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • Enterprise Only
      • [AER-6413] - (SECURITY) Small memory leak during LDAP login process. Fixed in version 4.9.0.30.

    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.

  • 4.9.0.27
    Release Date: February 22, 2021

    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).
      • Record bins containing (Complex Data Type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 4.9.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 4.9.0.28.
    • Enterprise Only
      • [AER-6413] - (SECURITY) Small memory leak during LDAP login process. Fixed in version 4.9.0.30.

    Bug Fixes

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

  • 4.9.0.26
    Release Date: February 12, 2021

    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).
      • Record bins containing (Complex Data Type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 4.9.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 4.9.0.28.
    • Enterprise Only
      • [AER-6413] - (SECURITY) Small memory leak during LDAP login process. Fixed in version 4.9.0.30.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 4.9.0.27.

    Bug Fixes

    • Enterprise Only
      • [AER-6391] - (XDR) When restarting storage-backed data-in-memory namespaces after XDR writes have been accepted on the node, an improper assertion will occur.

  • 4.9.0.25
    Release Date: January 30, 2021

    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).
      • Record bins containing (Complex Data Type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 4.9.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 4.9.0.28.
    • Enterprise Only
      • [AER-6413] - (SECURITY) Small memory leak during LDAP login process. Fixed in version 4.9.0.30.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 4.9.0.27.
      • [AER-6391] - (XDR) When restarting storage-backed data-in-memory namespaces after XDR writes have been accepted on the node, an improper assertion will occur. Fixed in version 4.9.0.26.

    Bug Fixes

    • Enterprise & Community
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated.
    • Enterprise Only
      • [AER-6382] - (SECURITY) When connecting to LDAP server, TLS handshake occasionally fails.

  • 4.9.0.24
    Release Date: January 25, 2021

    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).
      • Record bins containing (Complex Data Type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 4.9.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 4.9.0.28.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 4.9.0.25.
    • Enterprise Only
      • [AER-6413] - (SECURITY) Small memory leak during LDAP login process. Fixed in version 4.9.0.30.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 4.9.0.27.
      • [AER-6391] - (XDR) When restarting storage-backed data-in-memory namespaces after XDR writes have been accepted on the node, an improper assertion will occur. Fixed in version 4.9.0.26.
      • [AER-6382] - (SECURITY) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 4.9.0.25.

    Bug Fixes

    • Enterprise Only
      • [AER-6376] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges.

  • 4.9.0.23
    Release Date: January 4, 2021

    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).
      • Record bins containing (Complex Data Type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 4.9.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 4.9.0.28.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 4.9.0.25.
    • Enterprise Only
      • [AER-6413] - (SECURITY) Small memory leak during LDAP login process. Fixed in version 4.9.0.30.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 4.9.0.27.
      • [AER-6391] - (XDR) When restarting storage-backed data-in-memory namespaces after XDR writes have been accepted on the node, an improper assertion will occur. Fixed in version 4.9.0.26.
      • [AER-6382] - (SECURITY) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 4.9.0.25.
      • [AER-6376] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 4.9.0.24.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 4.9.0.24.

    Improvements

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

    Bug Fixes

    • 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] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item.

  • 4.9.0.21
    Release Date: December 17, 2020

    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).
      • Record bins containing (Complex Data Type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 4.9.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 4.9.0.28.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 4.9.0.25.
    • Enterprise Only
      • [AER-6413] - (SECURITY) Small memory leak during LDAP login process. Fixed in version 4.9.0.30.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 4.9.0.27.
      • [AER-6391] - (XDR) When restarting storage-backed data-in-memory namespaces after XDR writes have been accepted on the node, an improper assertion will occur. Fixed in version 4.9.0.26.
      • [AER-6382] - (SECURITY) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 4.9.0.25.
      • [AER-6376] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 4.9.0.24.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 4.9.0.24.
      • [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 4.9.0.23.
      • [AER-6361] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item. Fixed in version 4.9.0.23.

    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.

  • 4.9.0.20
    Release Date: November 25, 2020

    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).
      • Record bins containing (Complex Data Type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 4.9.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 4.9.0.28.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 4.9.0.25.
    • Enterprise Only
      • [AER-6413] - (SECURITY) Small memory leak during LDAP login process. Fixed in version 4.9.0.30.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 4.9.0.27.
      • [AER-6391] - (XDR) When restarting storage-backed data-in-memory namespaces after XDR writes have been accepted on the node, an improper assertion will occur. Fixed in version 4.9.0.26.
      • [AER-6382] - (SECURITY) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 4.9.0.25.
      • [AER-6376] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 4.9.0.24.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 4.9.0.24.
      • [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 4.9.0.23.
      • [AER-6361] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item. Fixed in version 4.9.0.23.

    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.

  • 4.9.0.19
    Release Date: November 19, 2020

    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).
      • Record bins containing (Complex Data Type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 4.9.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 4.9.0.28.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 4.9.0.25.
      • [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 4.9.0.20.
    • Enterprise Only
      • [AER-6413] - (SECURITY) Small memory leak during LDAP login process. Fixed in version 4.9.0.30.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 4.9.0.27.
      • [AER-6391] - (XDR) When restarting storage-backed data-in-memory namespaces after XDR writes have been accepted on the node, an improper assertion will occur. Fixed in version 4.9.0.26.
      • [AER-6382] - (SECURITY) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 4.9.0.25.
      • [AER-6376] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 4.9.0.24.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 4.9.0.24.
      • [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 4.9.0.23.
      • [AER-6361] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item. Fixed in version 4.9.0.23.

    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.
    • Enterprise Only
      • [AER-6335] - (XDR) Replica writes which are XDR writes are written to the digest log and may be shipped even if forwarding is off.

  • 4.9.0.17
    Release Date: November 10, 2020

    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).
      • Record bins containing (Complex Data Type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 4.9.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 4.9.0.28.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 4.9.0.25.
      • [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 4.9.0.20.
    • Enterprise Only
      • [AER-6413] - (SECURITY) Small memory leak during LDAP login process. Fixed in version 4.9.0.30.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 4.9.0.27.
      • [AER-6391] - (XDR) When restarting storage-backed data-in-memory namespaces after XDR writes have been accepted on the node, an improper assertion will occur. Fixed in version 4.9.0.26.
      • [AER-6382] - (SECURITY) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 4.9.0.25.
      • [AER-6376] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 4.9.0.24.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 4.9.0.24.
      • [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 4.9.0.23.
      • [AER-6361] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item. Fixed in version 4.9.0.23.

    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.

  • 4.9.0.16
    Release Date: October 31, 2020

    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).
      • Record bins containing (Complex Data Type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 4.9.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 4.9.0.28.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 4.9.0.25.
      • [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 4.9.0.20.
      • [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 4.9.0.17.
    • Enterprise Only
      • [AER-6413] - (SECURITY) Small memory leak during LDAP login process. Fixed in version 4.9.0.30.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 4.9.0.27.
      • [AER-6391] - (XDR) When restarting storage-backed data-in-memory namespaces after XDR writes have been accepted on the node, an improper assertion will occur. Fixed in version 4.9.0.26.
      • [AER-6382] - (SECURITY) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 4.9.0.25.
      • [AER-6376] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 4.9.0.24.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 4.9.0.24.
      • [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 4.9.0.23.
      • [AER-6361] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item. Fixed in version 4.9.0.23.

    Improvements

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

  • 4.9.0.15
    Release Date: October 21, 2020

    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).
      • Record bins containing (Complex Data Type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 4.9.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 4.9.0.28.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 4.9.0.25.
      • [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 4.9.0.20.
      • [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 4.9.0.17.
    • Enterprise Only
      • [AER-6413] - (SECURITY) Small memory leak during LDAP login process. Fixed in version 4.9.0.30.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 4.9.0.27.
      • [AER-6391] - (XDR) When restarting storage-backed data-in-memory namespaces after XDR writes have been accepted on the node, an improper assertion will occur. Fixed in version 4.9.0.26.
      • [AER-6382] - (SECURITY) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 4.9.0.25.
      • [AER-6376] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 4.9.0.24.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 4.9.0.24.
      • [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 4.9.0.23.
      • [AER-6361] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item. Fixed in version 4.9.0.23.

    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-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range.

  • 4.9.0.14
    Release Date: October 14, 2020

    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).
      • Record bins containing (Complex Data Type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 4.9.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 4.9.0.28.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 4.9.0.25.
      • [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 4.9.0.20.
      • [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 4.9.0.17.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.9.0.15.
    • Enterprise Only
      • [AER-6413] - (SECURITY) Small memory leak during LDAP login process. Fixed in version 4.9.0.30.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 4.9.0.27.
      • [AER-6391] - (XDR) When restarting storage-backed data-in-memory namespaces after XDR writes have been accepted on the node, an improper assertion will occur. Fixed in version 4.9.0.26.
      • [AER-6382] - (SECURITY) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 4.9.0.25.
      • [AER-6376] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 4.9.0.24.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 4.9.0.24.
      • [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 4.9.0.23.
      • [AER-6361] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item. Fixed in version 4.9.0.23.

    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.
    • Enterprise Only
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions.

  • 4.9.0.12
    Release Date: September 18, 2020

    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).
      • Record bins containing (Complex Data Type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 4.9.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 4.9.0.28.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 4.9.0.25.
      • [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 4.9.0.20.
      • [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 4.9.0.17.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.9.0.15.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 4.9.0.14.
      • [AER-6309] - (CDT) For ordered lists, get_all_by_value_list operation with result type value always returns an empty list. Fixed in version 4.9.0.14.
    • Enterprise Only
      • [AER-6413] - (SECURITY) Small memory leak during LDAP login process. Fixed in version 4.9.0.30.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 4.9.0.27.
      • [AER-6391] - (XDR) When restarting storage-backed data-in-memory namespaces after XDR writes have been accepted on the node, an improper assertion will occur. Fixed in version 4.9.0.26.
      • [AER-6382] - (SECURITY) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 4.9.0.25.
      • [AER-6376] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 4.9.0.24.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 4.9.0.24.
      • [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 4.9.0.23.
      • [AER-6361] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item. Fixed in version 4.9.0.23.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.9.0.14.

    Improvements

    Bug Fixes

    • Enterprise & Community
      • [AER-6289] - (KVS) Concurrently reading and writing a new bin or set name may access a pointer which crosses a cache line boundary, causing a crash.
    • Enterprise Only
      • [AER-6287] - (KVS) When writing over a tombstone with Time-To-Live (TTL) value -2 (i.e. do not update TTL), the write fails to apply the namespace default-ttl.

  • 4.9.0.11
    Release Date: July 7, 2020

    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).
      • Record bins containing (Complex Data Type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 4.9.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 4.9.0.28.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 4.9.0.25.
      • [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 4.9.0.20.
      • [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 4.9.0.17.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.9.0.15.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 4.9.0.14.
      • [AER-6309] - (CDT) For ordered lists, get_all_by_value_list operation with result type value always returns an empty list. Fixed in version 4.9.0.14.
      • [AER-6289] - (KVS) Concurrently reading and writing a new bin or set name may access a pointer which crosses a cache line boundary, causing a crash. Fixed in version 4.9.0.12.
    • Enterprise Only
      • [AER-6413] - (SECURITY) Small memory leak during LDAP login process. Fixed in version 4.9.0.30.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 4.9.0.27.
      • [AER-6391] - (XDR) When restarting storage-backed data-in-memory namespaces after XDR writes have been accepted on the node, an improper assertion will occur. Fixed in version 4.9.0.26.
      • [AER-6382] - (SECURITY) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 4.9.0.25.
      • [AER-6376] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 4.9.0.24.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 4.9.0.24.
      • [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 4.9.0.23.
      • [AER-6361] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item. Fixed in version 4.9.0.23.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.9.0.14.
      • [AER-6287] - (KVS) When writing over a tombstone with Time-To-Live (TTL) value -2 (i.e. do not update TTL), the write fails to apply the namespace default-ttl. Fixed in version 4.9.0.12.

    Bug Fixes

    • Enterprise & Community
      • [AER-6251] - (UDF) When a record UDF does not pass a predicate expression metadata filter, the server will deadlock.
    • Enterprise Only
      • [AER-6250] - (UDF) Race between a background UDF scan/query internal transaction and a durable delete may cause a deadlock.

  • 4.9.0.10
    Release Date: June 18, 2020
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Aerospike Server will not start If the value of default-ttl is non-zero and nsup-period is zero (the default).
    • Support added for HyperLogLog (HLL) probabilistic data types.
      • Clusters connected using Cross Datacenter Replication (XDR) all clusters must have been upgraded to Aerospike Server 4.9 prior to using the HyperLogLog (HLL) data type.
      • Before downgrading from Aerospike Server 4.9 all HyperLogLog (HLL) bins must be removed by the application.
      • During the unlikely case of a downgrade the drives would need to be wiped. It is advised to review your Aerospike Server 4.9 environment prior to implementing the usage of HyperLogLog (HLL) data type bins.
    • XDR, using ACL, in server versions between 4.1.0.1 and 4.3.0.6 cannot ship to this version. The simplest workaround is to avoid using those versions.
    • When upgrading to Aerospike Server v4.9.0.7 or newer to ensure migrations complete refer to the Special Upgrades document section Avoiding partition ownership disagreement that prevents migrations from completing.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    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).
      • Record bins containing (Complex Data Type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 4.9.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 4.9.0.28.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 4.9.0.25.
      • [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 4.9.0.20.
      • [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 4.9.0.17.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.9.0.15.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 4.9.0.14.
      • [AER-6309] - (CDT) For ordered lists, get_all_by_value_list operation with result type value always returns an empty list. Fixed in version 4.9.0.14.
      • [AER-6289] - (KVS) Concurrently reading and writing a new bin or set name may access a pointer which crosses a cache line boundary, causing a crash. Fixed in version 4.9.0.12.
      • [AER-6251] - (UDF) When a record UDF does not pass a predicate expression metadata filter, the server will deadlock. Fixed in version 4.9.0.11.
    • Enterprise Only
      • [AER-6413] - (SECURITY) Small memory leak during LDAP login process. Fixed in version 4.9.0.30.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 4.9.0.27.
      • [AER-6391] - (XDR) When restarting storage-backed data-in-memory namespaces after XDR writes have been accepted on the node, an improper assertion will occur. Fixed in version 4.9.0.26.
      • [AER-6382] - (SECURITY) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 4.9.0.25.
      • [AER-6376] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 4.9.0.24.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 4.9.0.24.
      • [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 4.9.0.23.
      • [AER-6361] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item. Fixed in version 4.9.0.23.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.9.0.14.
      • [AER-6287] - (KVS) When writing over a tombstone with Time-To-Live (TTL) value -2 (i.e. do not update TTL), the write fails to apply the namespace default-ttl. Fixed in version 4.9.0.12.
      • [AER-6250] - (UDF) Race between a background UDF scan/query internal transaction and a durable delete may cause a deadlock. Fixed in verswion 4.9.0.11.

    Improvements

    • Enterprise & Community
      • [AER-6238] - (UDF) Added service context configuration item disable-udf-execution as a mitigation option for Lua security vulnerabilities.

    Bug Fixes

    • Enterprise & Community
      • [AER-6239] - (INFO) Invalid log-set command parameters may cause a crash.

  • 4.9.0.8
    Release Date: May 22, 2020
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Aerospike Server will not start If the value of default-ttl is non-zero and nsup-period is zero (the default).
    • Support added for HyperLogLog (HLL) probabilistic data types.
      • Clusters connected using Cross Datacenter Replication (XDR) all clusters must have been upgraded to Aerospike Server 4.9 prior to using the HyperLogLog (HLL) data type.
      • Before downgrading from Aerospike Server 4.9 all HyperLogLog (HLL) bins must be removed by the application.
      • During the unlikely case of a downgrade the drives would need to be wiped. It is advised to review your Aerospike Server 4.9 environment prior to implementing the usage of HyperLogLog (HLL) data type bins.
    • XDR, using ACL, in server versions between 4.1.0.1 and 4.3.0.6 cannot ship to this version. The simplest workaround is to avoid using those versions.
    • When upgrading to Aerospike Server v4.9.0.7 or newer to ensure migrations complete refer to the Special Upgrades document section Avoiding partition ownership disagreement that prevents migrations from completing.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • Please reach out to your account representative if you are interested in Kerberos support.

    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).
      • Record bins containing (Complex Data Type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 4.9.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 4.9.0.28.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 4.9.0.25.
      • [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 4.9.0.20.
      • [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 4.9.0.17.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.9.0.15.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 4.9.0.14.
      • [AER-6309] - (CDT) For ordered lists, get_all_by_value_list operation with result type value always returns an empty list. Fixed in version 4.9.0.14.
      • [AER-6289] - (KVS) Concurrently reading and writing a new bin or set name may access a pointer which crosses a cache line boundary, causing a crash. Fixed in version 4.9.0.12.
      • [AER-6251] - (UDF) When a record UDF does not pass a predicate expression metadata filter, the server will deadlock. Fixed in version 4.9.0.11.
      • [AER-6239] - (INFO) Invalid log-set command parameters may cause a crash. Fixed in version 4.9.0.10.
    • Enterprise Only
      • [AER-6413] - (SECURITY) Small memory leak during LDAP login process. Fixed in version 4.9.0.30.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 4.9.0.27.
      • [AER-6391] - (XDR) When restarting storage-backed data-in-memory namespaces after XDR writes have been accepted on the node, an improper assertion will occur. Fixed in version 4.9.0.26.
      • [AER-6382] - (SECURITY) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 4.9.0.25.
      • [AER-6376] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 4.9.0.24.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 4.9.0.24.
      • [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 4.9.0.23.
      • [AER-6361] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item. Fixed in version 4.9.0.23.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.9.0.14.
      • [AER-6287] - (KVS) When writing over a tombstone with Time-To-Live (TTL) value -2 (i.e. do not update TTL), the write fails to apply the namespace default-ttl. Fixed in version 4.9.0.12.
      • [AER-6250] - (UDF) Race between a background UDF scan/query internal transaction and a durable delete may cause a deadlock. Fixed in verswion 4.9.0.11.

    Bug Fixes

    • Enterprise & Community
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated.

  • 4.9.0.7
    Release Date: May 14, 2020
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Aerospike Server will not start If the value of default-ttl is non-zero and nsup-period is zero (the default).
    • Support added for HyperLogLog (HLL) probabilistic data types.
      • Clusters connected using Cross Datacenter Replication (XDR) all clusters must have been upgraded to Aerospike Server 4.9 prior to using the HyperLogLog (HLL) data type.
      • Before downgrading from Aerospike Server 4.9 all HyperLogLog (HLL) bins must be removed by the application.
      • During the unlikely case of a downgrade the drives would need to be wiped. It is advised to review your Aerospike Server 4.9 environment prior to implementing the usage of HyperLogLog (HLL) data type bins.
    • XDR, using ACL, in server versions between 4.1.0.1 and 4.3.0.6 cannot ship to this version. The simplest workaround is to avoid using those versions.
    • When upgrading to Aerospike Server v4.9.0.7 or newer to ensure migrations complete refer to the Special Upgrades document section Avoiding partition ownership disagreement that prevents migrations from completing.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • Please reach out to your account representative if you are interested in Kerberos support.

    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).
      • Record bins containing (Complex Data Type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 4.9.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 4.9.0.28.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 4.9.0.25.
      • [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 4.9.0.20.
      • [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 4.9.0.17.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.9.0.15.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 4.9.0.14.
      • [AER-6309] - (CDT) For ordered lists, get_all_by_value_list operation with result type value always returns an empty list. Fixed in version 4.9.0.14.
      • [AER-6289] - (KVS) Concurrently reading and writing a new bin or set name may access a pointer which crosses a cache line boundary, causing a crash. Fixed in version 4.9.0.12.
      • [AER-6251] - (UDF) When a record UDF does not pass a predicate expression metadata filter, the server will deadlock. Fixed in version 4.9.0.11.
      • [AER-6239] - (INFO) Invalid log-set command parameters may cause a crash. Fixed in version 4.9.0.10.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.9.0.8.
    • Enterprise Only
      • [AER-6413] - (SECURITY) Small memory leak during LDAP login process. Fixed in version 4.9.0.30.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 4.9.0.27.
      • [AER-6391] - (XDR) When restarting storage-backed data-in-memory namespaces after XDR writes have been accepted on the node, an improper assertion will occur. Fixed in version 4.9.0.26.
      • [AER-6382] - (SECURITY) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 4.9.0.25.
      • [AER-6376] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 4.9.0.24.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 4.9.0.24.
      • [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 4.9.0.23.
      • [AER-6361] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item. Fixed in version 4.9.0.23.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.9.0.14.
      • [AER-6287] - (KVS) When writing over a tombstone with Time-To-Live (TTL) value -2 (i.e. do not update TTL), the write fails to apply the namespace default-ttl. Fixed in version 4.9.0.12.
      • [AER-6250] - (UDF) Race between a background UDF scan/query internal transaction and a durable delete may cause a deadlock. Fixed in verswion 4.9.0.11.

    Bug Fixes

    • Enterprise Only
      • [AER-6227] - (BALANCE) When applying uniform balance, a misused stack variable may cause an inaccurate balance and prevent migrations from completing.

  • 4.9.0.6
    Release Date: April 29, 2020
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Aerospike Server will not start If the value of default-ttl is non-zero and nsup-period is zero (the default).
    • Support added for HyperLogLog (HLL) probabilistic data types.
      • Clusters connected using Cross Datacenter Replication (XDR) all clusters must have been upgraded to Aerospike Server 4.9 prior to using the HyperLogLog (HLL) data type.
      • Before downgrading from Aerospike Server 4.9 all HyperLogLog (HLL) bins must be removed by the application.
      • During the unlikely case of a downgrade the drives would need to be wiped. It is advised to review your Aerospike Server 4.9 environment prior to implementing the usage of HyperLogLog (HLL) data type bins.
    • XDR, using ACL, in server versions between 4.1.0.1 and 4.3.0.6 cannot ship to this version. The simplest workaround is to avoid using those versions.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • Please reach out to your account representative if you are interested in Kerberos support.

    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).
      • Record bins containing (Complex Data Type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 4.9.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 4.9.0.28.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 4.9.0.25.
      • [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 4.9.0.20.
      • [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 4.9.0.17.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.9.0.15.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 4.9.0.14.
      • [AER-6309] - (CDT) For ordered lists, get_all_by_value_list operation with result type value always returns an empty list. Fixed in version 4.9.0.14.
      • [AER-6289] - (KVS) Concurrently reading and writing a new bin or set name may access a pointer which crosses a cache line boundary, causing a crash. Fixed in version 4.9.0.12.
      • [AER-6251] - (UDF) When a record UDF does not pass a predicate expression metadata filter, the server will deadlock. Fixed in version 4.9.0.11.
      • [AER-6239] - (INFO) Invalid log-set command parameters may cause a crash. Fixed in version 4.9.0.10.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.9.0.8.
    • Enterprise Only
      • [AER-6413] - (SECURITY) Small memory leak during LDAP login process. Fixed in version 4.9.0.30.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 4.9.0.27.
      • [AER-6391] - (XDR) When restarting storage-backed data-in-memory namespaces after XDR writes have been accepted on the node, an improper assertion will occur. Fixed in version 4.9.0.26.
      • [AER-6382] - (SECURITY) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 4.9.0.25.
      • [AER-6376] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 4.9.0.24.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 4.9.0.24.
      • [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 4.9.0.23.
      • [AER-6361] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item. Fixed in version 4.9.0.23.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.9.0.14.
      • [AER-6287] - (KVS) When writing over a tombstone with Time-To-Live (TTL) value -2 (i.e. do not update TTL), the write fails to apply the namespace default-ttl. Fixed in version 4.9.0.12.
      • [AER-6250] - (UDF) Race between a background UDF scan/query internal transaction and a durable delete may cause a deadlock. Fixed in verswion 4.9.0.11.
      • [AER-6227] - (BALANCE) When applying uniform balance, a misused stack variable may cause an inaccurate balance and prevent migrations from completing. Fixed in version 4.9.0.7.

    Bug Fixes

    • Enterprise & Community
      • [AER-6223] - (KVS) Poor intersect count estimate when intersecting more than two HyperLogLog sets.
      • [AER-6224] - (KVS) Incorrect parsing of signed integers in certain CDT operations (e.g. range operations) or bitwise BLOB operations (e.g. with negative offsets) may cause failures or bad results.

  • 4.9.0.5
    Release Date: April 21, 2020
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Aerospike Server will not start If the value of default-ttl is non-zero and nsup-period is zero (the default).
    • Support added for HyperLogLog (HLL) probabilistic data types.
      • Clusters connected using Cross Datacenter Replication (XDR) all clusters must have been upgraded to Aerospike Server 4.9 prior to using the HyperLogLog (HLL) data type.
      • Before downgrading from Aerospike Server 4.9 all HyperLogLog (HLL) bins must be removed by the application.
      • During the unlikely case of a downgrade the drives would need to be wiped. It is advised to review your Aerospike Server 4.9 environment prior to implementing the usage of HyperLogLog (HLL) data type bins.
    • XDR, using ACL, in server versions between 4.1.0.1 and 4.3.0.6 cannot ship to this version. The simplest workaround is to avoid using those versions.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • Please reach out to your account representative if you are interested in Kerberos support.

    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).
      • Record bins containing (Complex Data Type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 4.9.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 4.9.0.28.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 4.9.0.25.
      • [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 4.9.0.20.
      • [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 4.9.0.17.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.9.0.15.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 4.9.0.14.
      • [AER-6309] - (CDT) For ordered lists, get_all_by_value_list operation with result type value always returns an empty list. Fixed in version 4.9.0.14.
      • [AER-6289] - (KVS) Concurrently reading and writing a new bin or set name may access a pointer which crosses a cache line boundary, causing a crash. Fixed in version 4.9.0.12.
      • [AER-6251] - (UDF) When a record UDF does not pass a predicate expression metadata filter, the server will deadlock. Fixed in version 4.9.0.11.
      • [AER-6239] - (INFO) Invalid log-set command parameters may cause a crash. Fixed in version 4.9.0.10.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.9.0.8.
      • [AER-6223] - (KVS) Poor intersect count estimate when intersecting more than two HyperLogLog sets. Fixed in version 4.9.0.6.
      • [AER-6224] - (KVS) Incorrect parsing of signed integers in certain CDT operations (e.g. range operations) or bitwise BLOB operations (e.g. with negative offsets) may cause failures or bad results. Fixed in version 4.9.0.6.
    • Enterprise Only
      • [AER-6413] - (SECURITY) Small memory leak during LDAP login process. Fixed in version 4.9.0.30.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 4.9.0.27.
      • [AER-6391] - (XDR) When restarting storage-backed data-in-memory namespaces after XDR writes have been accepted on the node, an improper assertion will occur. Fixed in version 4.9.0.26.
      • [AER-6382] - (SECURITY) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 4.9.0.25.
      • [AER-6376] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 4.9.0.24.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 4.9.0.24.
      • [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 4.9.0.23.
      • [AER-6361] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item. Fixed in version 4.9.0.23.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.9.0.14.
      • [AER-6287] - (KVS) When writing over a tombstone with Time-To-Live (TTL) value -2 (i.e. do not update TTL), the write fails to apply the namespace default-ttl. Fixed in version 4.9.0.12.
      • [AER-6250] - (UDF) Race between a background UDF scan/query internal transaction and a durable delete may cause a deadlock. Fixed in verswion 4.9.0.11.
      • [AER-6227] - (BALANCE) When applying uniform balance, a misused stack variable may cause an inaccurate balance and prevent migrations from completing. Fixed in version 4.9.0.7.

    Bug Fixes

    • Community Only
      • [AER-6220] - (STORAGE) In Community Edition, uninitialized storage bit may cause pre-4.9 nodes to reject records sent by 4.9 nodes.

  • 4.9.0.4
    Release Date: April 17, 2020

    COMMUNITY EDITION USERS: Please use release 4.9.0.5 or newer in lieu of this version.

    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Aerospike Server will not start If the value of default-ttl is non-zero and nsup-period is zero (the default).
    • Support added for HyperLogLog (HLL) probabilistic data types.
      • Clusters connected using Cross Datacenter Replication (XDR) all clusters must have been upgraded to Aerospike Server 4.9 prior to using the HyperLogLog (HLL) data type.
      • Before downgrading from Aerospike Server 4.9 all HyperLogLog (HLL) bins must be removed by the application.
      • During the unlikely case of a downgrade the drives would need to be wiped. It is advised to review your Aerospike Server 4.9 environment prior to implementing the usage of HyperLogLog (HLL) data type bins.
    • XDR, using ACL, in server versions between 4.1.0.1 and 4.3.0.6 cannot ship to this version. The simplest workaround is to avoid using those versions.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • Please reach out to your account representative if you are interested in Kerberos support.

    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).
      • Record bins containing (Complex Data Type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 4.9.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 4.9.0.28.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 4.9.0.25.
      • [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 4.9.0.20.
      • [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 4.9.0.17.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.9.0.15.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 4.9.0.14.
      • [AER-6309] - (CDT) For ordered lists, get_all_by_value_list operation with result type value always returns an empty list. Fixed in version 4.9.0.14.
      • [AER-6289] - (KVS) Concurrently reading and writing a new bin or set name may access a pointer which crosses a cache line boundary, causing a crash. Fixed in version 4.9.0.12.
      • [AER-6251] - (UDF) When a record UDF does not pass a predicate expression metadata filter, the server will deadlock. Fixed in version 4.9.0.11.
      • [AER-6239] - (INFO) Invalid log-set command parameters may cause a crash. Fixed in version 4.9.0.10.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.9.0.8.
      • [AER-6223] - (KVS) Poor intersect count estimate when intersecting more than two HyperLogLog sets. Fixed in version 4.9.0.6.
      • [AER-6224] - (KVS) Incorrect parsing of signed integers in certain CDT operations (e.g. range operations) or bitwise BLOB operations (e.g. with negative offsets) may cause failures or bad results. Fixed in version 4.9.0.6.
    • Enterprise Only
      • [AER-6413] - (SECURITY) Small memory leak during LDAP login process. Fixed in version 4.9.0.30.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 4.9.0.27.
      • [AER-6391] - (XDR) When restarting storage-backed data-in-memory namespaces after XDR writes have been accepted on the node, an improper assertion will occur. Fixed in version 4.9.0.26.
      • [AER-6382] - (SECURITY) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 4.9.0.25.
      • [AER-6376] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 4.9.0.24.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 4.9.0.24.
      • [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 4.9.0.23.
      • [AER-6361] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item. Fixed in version 4.9.0.23.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.9.0.14.
      • [AER-6287] - (KVS) When writing over a tombstone with Time-To-Live (TTL) value -2 (i.e. do not update TTL), the write fails to apply the namespace default-ttl. Fixed in version 4.9.0.12.
      • [AER-6250] - (UDF) Race between a background UDF scan/query internal transaction and a durable delete may cause a deadlock. Fixed in verswion 4.9.0.11.
      • [AER-6227] - (BALANCE) When applying uniform balance, a misused stack variable may cause an inaccurate balance and prevent migrations from completing. Fixed in version 4.9.0.7.
    • Community Only
      • [AER-6220] - (STORAGE) In Community Edition, uninitialized storage bit may cause pre-4.9 nodes to reject records sent by 4.9 nodes. Fixed in version 4.9.0.5.

    Bug Fixes

    • Enterprise & Community
      • [AER-6215] - (KVS) HyperLogLog similarity estimates are inconsistent when all sets are empty.
      • [AER-6216] - (KVS) Dynamically increasing service context configuration item service-threads may cause an assert.
    • Enterprise Only
      • [AER-6214] - (SECURITY) Specifying a whitelist with a maximum set of (32) networks causes a stack memory stomp.

  • 4.9.0.3
    Release Date: April 8, 2020

    COMMUNITY EDITION USERS: Please use release 4.9.0.5 or newer in lieu of this version.

    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Aerospike Server will not start If the value of default-ttl is non-zero and nsup-period is zero (the default).
    • Support added for HyperLogLog (HLL) probabilistic data types.
      • Clusters connected using Cross Datacenter Replication (XDR) all clusters must have been upgraded to Aerospike Server 4.9 prior to using the HyperLogLog (HLL) data type.
      • Before downgrading from Aerospike Server 4.9 all HyperLogLog (HLL) bins must be removed by the application.
      • During the unlikely case of a downgrade the drives would need to be wiped. It is advised to review your Aerospike Server 4.9 environment prior to implementing the usage of HyperLogLog (HLL) data type bins.
    • Added support for:
      • Partition-based basic scans, enabling accurate scans during migrations.
      • Added a max records option for sampling with basic scans.
      • Optional element creation in nested CDT operations.
    • XDR, using ACL, in server versions between 4.1.0.1 and 4.3.0.6 cannot ship to this version. The simplest workaround is to avoid using those versions.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • Please reach out to your account representative if you are interested in Kerberos support.

    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).
      • Record bins containing (Complex Data Type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 4.9.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 4.9.0.28.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 4.9.0.25.
      • [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 4.9.0.20.
      • [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 4.9.0.17.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.9.0.15.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 4.9.0.14.
      • [AER-6309] - (CDT) For ordered lists, get_all_by_value_list operation with result type value always returns an empty list. Fixed in version 4.9.0.14.
      • [AER-6289] - (KVS) Concurrently reading and writing a new bin or set name may access a pointer which crosses a cache line boundary, causing a crash. Fixed in version 4.9.0.12.
      • [AER-6251] - (UDF) When a record UDF does not pass a predicate expression metadata filter, the server will deadlock. Fixed in version 4.9.0.11.
      • [AER-6239] - (INFO) Invalid log-set command parameters may cause a crash. Fixed in version 4.9.0.10.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.9.0.8.
      • [AER-6223] - (KVS) Poor intersect count estimate when intersecting more than two HyperLogLog sets. Fixed in version 4.9.0.6.
      • [AER-6224] - (KVS) Incorrect parsing of signed integers in certain CDT operations (e.g. range operations) or bitwise BLOB operations (e.g. with negative offsets) may cause failures or bad results. Fixed in version 4.9.0.6.
      • [AER-6215] - (KVS) HyperLogLog similarity estimates are inconsistent when all sets are empty. Fixed in version 4.9.0.4.
      • [AER-6216] - (KVS) Dynamically increasing service context configuration item service-threads may cause an assert. Fixed in version 4.9.0.4.
    • Enterprise Only
      • [AER-6413] - (SECURITY) Small memory leak during LDAP login process. Fixed in version 4.9.0.30.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 4.9.0.27.
      • [AER-6391] - (XDR) When restarting storage-backed data-in-memory namespaces after XDR writes have been accepted on the node, an improper assertion will occur. Fixed in version 4.9.0.26.
      • [AER-6382] - (SECURITY) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 4.9.0.25.
      • [AER-6376] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 4.9.0.24.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 4.9.0.24.
      • [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 4.9.0.23.
      • [AER-6361] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item. Fixed in version 4.9.0.23.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.9.0.14.
      • [AER-6287] - (KVS) When writing over a tombstone with Time-To-Live (TTL) value -2 (i.e. do not update TTL), the write fails to apply the namespace default-ttl. Fixed in version 4.9.0.12.
      • [AER-6250] - (UDF) Race between a background UDF scan/query internal transaction and a durable delete may cause a deadlock. Fixed in verswion 4.9.0.11.
      • [AER-6227] - (BALANCE) When applying uniform balance, a misused stack variable may cause an inaccurate balance and prevent migrations from completing. Fixed in version 4.9.0.7.
      • [AER-6214] - (SECURITY) Specifying a whitelist with a maximum set of (32) networks causes a stack memory stomp. Fixed in version 4.9.0.4.
    • Community Only
      • [AER-6220] - (STORAGE) In Community Edition, uninitialized storage bit may cause pre-4.9 nodes to reject records sent by 4.9 nodes. Fixed in version 4.9.0.5.

    New Features

    • Enterprise & Community
      • [AER-6199] - (KVS) Added support for HyperLogLog (HLL) data types.
      • [AER-5474] - (SCAN) Basic scans now based on lists of partitions and/or digests sent by client.
      • [AER-6193] - (SCAN) Added a max records option for sampling with basic scans.
      • [AER-6203] - (CDT) Added support for optional element creation in nested CDT operations.

    Improvements

    • Enterprise & Community
      • [AER-6184] - (KVS) Configuring any eviction threshold (e.g. high-water-memory-pct) to 0 disables that eviction threshold.
      • [AER-6186] - (KVS) Changed eviction-related high water percentage configuration defaults to 0, so that eviction is inactive by default.
      • [AER-6187] - (KVS) Changed default value of nsup-period to 0, and added namespace context configuration item allow-ttl-without-nsup to allow records with TTLs when nsup-period is 0.
      • [AER-6185] - (BATCH) Added service context configuration item batch-without-digests to exclude digests from batch responses.
      • [AER-6209] - (NETWORK) Ignore additional addresses for an interface once the limit (20) is reached.
      • [AER-6192] - (MIGRATION) Increased metadata batch size and maximum outstanding data size limit, to help performance across longer links.
      • [AER-6191] - (LOGGING) Changed warning message about failure to resolve a mount point to a detail level message.
      • [AER-6210] - (LOGGING) Changed default logging level to 'critical' for all contexts.
      • [AER-6116] - (STATS) Converted 'batch-index' histogram to tracked histogram.
      • [AER-6183] - (STATS) Added delay count to batch-index log ticker line.
    • Enterprise Only
      • [AER-6205] - (KVS) Changed response (zlib) compression level to 1.
      • [AER-6208] - (KVS) Non-durable deletes will now ignore tombstones and return Not Found.
      • [AER-6158] - (TLS) Increased socket accept timeout to accommodate heartbeat across longer links.
      • [AER-6206] - (XDR) Changed (zlib) compression level to 1.

    Bug Fixes

    • Enterprise & Community
      • [AER-6211] - (KVS) Dynamically increasing both the system file descriptor limit and service context configuration item proto-fd-max to a value larger than the system limit at startup may cause an assert.

    Updates

  • 4.8.0.31
    Release Date: March 29, 2021

    Known Issues

    • Enterprise & Community
      • Record bins containing (Complex Data Type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.

    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] - (SECURITY) Small memory leak during LDAP login process.

  • 4.8.0.29
    Release Date: March 12, 2021

    Known Issues

    • Enterprise & Community
      • Record bins containing (Complex Data Type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • Enterprise Only
      • [AER-6413] - (SECURITY) Small memory leak during LDAP login process. Fixed in version 4.8.0.31.

    Bug Fixes

    • Enterprise & Community
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical.
      • [AER-6401] - (CDT) When unwinding an index for a nested CDT op which turns out to be a no-op, the index may be corrupted.
      • [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.

  • 4.8.0.28
    Release Date: February 22, 2021

    Known Issues

    • Enterprise & Community
      • Record bins containing (Complex Data Type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 4.8.0.29.
      • [AER-6401] - (CDT) When unwinding an index for a nested CDT op which turns out to be a no-op, the index may be corrupted. Fixed in version 4.8.0.29.
      • [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 4.8.0.29.
    • Enterprise Only
      • [AER-6413] - (SECURITY) Small memory leak during LDAP login process. Fixed in version 4.8.0.31.

    Bug Fixes

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

  • 4.8.0.27
    Release Date: January 30, 2021

    Known Issues

    • Enterprise & Community
      • Record bins containing (Complex Data Type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 4.8.0.29.
      • [AER-6401] - (CDT) When unwinding an index for a nested CDT op which turns out to be a no-op, the index may be corrupted. Fixed in version 4.8.0.29.
      • [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 4.8.0.29.
    • Enterprise Only
      • [AER-6413] - (SECURITY) Small memory leak during LDAP login process. Fixed in version 4.8.0.31.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 4.8.0.28.

    Bug Fixes

    • Enterprise & Community
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated.
    • Enterprise Only
      • [AER-6382] - (SECURITY) When connecting to LDAP server, TLS handshake occasionally fails.

  • 4.8.0.26
    Release Date: January 25, 2021

    Known Issues

    • Enterprise & Community
      • Record bins containing (Complex Data Type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 4.8.0.29.
      • [AER-6401] - (CDT) When unwinding an index for a nested CDT op which turns out to be a no-op, the index may be corrupted. Fixed in version 4.8.0.29.
      • [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 4.8.0.29.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 4.8.0.27.
    • Enterprise Only
      • [AER-6413] - (SECURITY) Small memory leak during LDAP login process. Fixed in version 4.8.0.31.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 4.8.0.28.
      • [AER-6382] - (SECURITY) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 4.8.0.27.

    Bug Fixes

    • Enterprise Only
      • [AER-6376] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges.

  • 4.8.0.25
    Release Date: January 4, 2021

    Known Issues

    • Enterprise & Community
      • Record bins containing (Complex Data Type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 4.8.0.29.
      • [AER-6401] - (CDT) When unwinding an index for a nested CDT op which turns out to be a no-op, the index may be corrupted. Fixed in version 4.8.0.29.
      • [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 4.8.0.29.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 4.8.0.27.
    • Enterprise Only
      • [AER-6413] - (SECURITY) Small memory leak during LDAP login process. Fixed in version 4.8.0.31.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 4.8.0.28.
      • [AER-6382] - (SECURITY) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 4.8.0.27.
      • [AER-6376] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 4.8.0.26.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 4.8.0.26.

    Improvements

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

    Bug Fixes

    • 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] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item.

  • 4.8.0.23
    Release Date: December 17, 2020

    Known Issues

    • Enterprise & Community
      • Record bins containing (Complex Data Type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 4.8.0.29.
      • [AER-6401] - (CDT) When unwinding an index for a nested CDT op which turns out to be a no-op, the index may be corrupted. Fixed in version 4.8.0.29.
      • [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 4.8.0.29.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 4.8.0.27.
    • Enterprise Only
      • [AER-6413] - (SECURITY) Small memory leak during LDAP login process. Fixed in version 4.8.0.31.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 4.8.0.28.
      • [AER-6382] - (SECURITY) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 4.8.0.27.
      • [AER-6376] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 4.8.0.26.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 4.8.0.26.
      • [AER-6363] - (KVS) A write or a UDF that deletes all of a record's bins may result in a tombstone with a non-zero void-time. Fixed in version 4.8.0.25.
      • [AER-6361] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item. Fixed in version 4.8.0.25.

    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.

  • 4.8.0.22
    Release Date: November 25, 2020
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • Enterprise & Community
      • Record bins containing (Complex Data Type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 4.8.0.29.
      • [AER-6401] - (CDT) When unwinding an index for a nested CDT op which turns out to be a no-op, the index may be corrupted. Fixed in version 4.8.0.29.
      • [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 4.8.0.29.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 4.8.0.27.
    • Enterprise Only
      • [AER-6413] - (SECURITY) Small memory leak during LDAP login process. Fixed in version 4.8.0.31.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 4.8.0.28.
      • [AER-6382] - (SECURITY) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 4.8.0.27.
      • [AER-6376] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 4.8.0.26.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 4.8.0.26.
      • [AER-6363] - (KVS) A write or a UDF that deletes all of a record's bins may result in a tombstone with a non-zero void-time. Fixed in version 4.8.0.25.
      • [AER-6361] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item. Fixed in version 4.8.0.25.

    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.

  • 4.8.0.21
    Release Date: November 19, 2020
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • Enterprise & Community
      • Record bins containing (Complex Data Type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 4.8.0.29.
      • [AER-6401] - (CDT) When unwinding an index for a nested CDT op which turns out to be a no-op, the index may be corrupted. Fixed in version 4.8.0.29.
      • [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 4.8.0.29.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 4.8.0.27.
    • Enterprise Only
      • [AER-6413] - (SECURITY) Small memory leak during LDAP login process. Fixed in version 4.8.0.31.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 4.8.0.28.
      • [AER-6382] - (SECURITY) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 4.8.0.27.
      • [AER-6376] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 4.8.0.26.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 4.8.0.26.
      • [AER-6363] - (KVS) A write or a UDF that deletes all of a record's bins may result in a tombstone with a non-zero void-time. Fixed in version 4.8.0.25.
      • [AER-6361] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item. Fixed in version 4.8.0.25.

    Bug Fixes

    • Enterprise & Community
      • [AER-6336] - (BATCH) If both filters and bin selection are used in a batch request, proxied sub-transactions are malformed and will fail.

  • 4.8.0.19
    Release Date: November 10, 2020
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • Enterprise & Community
      • Record bins containing (Complex Data Type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 4.8.0.29.
      • [AER-6401] - (CDT) When unwinding an index for a nested CDT op which turns out to be a no-op, the index may be corrupted. Fixed in version 4.8.0.29.
      • [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 4.8.0.29.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated. Fixed in version 4.8.0.27.
      • [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 4.8.0.20.
    • Enterprise Only
      • [AER-6413] - (SECURITY) Small memory leak during LDAP login process. Fixed in version 4.8.0.31.
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 4.8.0.28.
      • [AER-6382] - (SECURITY) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 4.8.0.27.
      • [AER-6376] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 4.8.0.26.
      • [AER-6378] - (SECURITY) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 4.8.0.26.
      • [AER-6363] - (KVS) A write or a UDF that deletes all of a record's bins may result in a tombstone with a non-zero void-time. Fixed in version 4.8.0.25.
      • [AER-6361] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item. Fixed in version 4.8.0.25.

    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.

  • 4.8.0.18
    Release Date: October 21, 2020
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • Enterprise & Community
      • Record bins containing (Complex Data Type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 4.8.0.29.
      • [AER-6401] - (CDT) When unwinding an index for a nested CDT op which turns out to be a no-op, the index may be corrupted. Fixed in version 4.8.0.29.
      • [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 4.8.0.29.
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated.