Aerospike Server CE Release Notes

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

    Improvements

    • Enterprise & Community
      • [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.8.0.17
    Release Date: October 14, 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-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.
      • [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.8.0.19.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.8.0.18.

    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.8.0.15
    Release Date: September 18, 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-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.
      • [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.8.0.19.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.8.0.18.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 4.8.0.17.
      • [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.8.0.17.
    • Enterprise Only
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.8.0.17.

    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.8.0.14
    Release Date: July 7, 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-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.
      • [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.8.0.19.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.8.0.18.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 4.8.0.17.
      • [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.8.0.17.
      • [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.8.0.15.
    • Enterprise Only
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.8.0.17.
      • [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.8.0.15.

    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.8.0.13
    Release Date: June 18, 2020
    • 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.

    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-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.
      • [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.8.0.19.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.8.0.18.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 4.8.0.17.
      • [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.8.0.17.
      • [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.8.0.15.
      • [AER-6251] - (UDF) When a record UDF does not pass a predicate expression metadata filter, the server will deadlock. Fixed in version 4.8.0.14.
    • Enterprise Only
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.8.0.17.
      • [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.8.0.15.
      • [AER-6250] - (UDF) Race between a background UDF scan/query internal transaction and a durable delete may cause a deadlock. Fixed in version 4.8.0.14.

    Improvements

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

  • 4.8.0.11
    Release Date: May 22, 2020
    • 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
      • 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-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.
      • [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.8.0.19.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.8.0.18.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 4.8.0.17.
      • [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.8.0.17.
      • [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.8.0.15.
      • [AER-6251] - (UDF) When a record UDF does not pass a predicate expression metadata filter, the server will deadlock. Fixed in version 4.8.0.14.
    • Enterprise Only
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.8.0.17.
      • [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.8.0.15.
      • [AER-6250] - (UDF) Race between a background UDF scan/query internal transaction and a durable delete may cause a deadlock. Fixed in version 4.8.0.14.

    Bug Fixes

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

  • 4.8.0.10
    Release Date: May 15, 2020
    • 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
      • 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-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.
      • [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.8.0.19.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.8.0.18.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 4.8.0.17.
      • [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.8.0.17.
      • [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.8.0.15.
      • [AER-6251] - (UDF) When a record UDF does not pass a predicate expression metadata filter, the server will deadlock. Fixed in version 4.8.0.14.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.8.0.11.
    • Enterprise Only
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.8.0.17.
      • [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.8.0.15.
      • [AER-6250] - (UDF) Race between a background UDF scan/query internal transaction and a durable delete may cause a deadlock. Fixed in version 4.8.0.14.

    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.8.0.9
    Release Date: April 17, 2020
    • 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
      • 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-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.
      • [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.8.0.19.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.8.0.18.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 4.8.0.17.
      • [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.8.0.17.
      • [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.8.0.15.
      • [AER-6251] - (UDF) When a record UDF does not pass a predicate expression metadata filter, the server will deadlock. Fixed in version 4.8.0.14.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.8.0.11.
    • Enterprise Only
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.8.0.17.
      • [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.8.0.15.
      • [AER-6250] - (UDF) Race between a background UDF scan/query internal transaction and a durable delete may cause a deadlock. Fixed in version 4.8.0.14.
      • [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.8.0.10.

    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.
      • [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.8.0.8
    Release Date: March 19, 2020
    • 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
      • 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-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.
      • [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.8.0.19.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.8.0.18.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 4.8.0.17.
      • [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.8.0.17.
      • [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.8.0.15.
      • [AER-6251] - (UDF) When a record UDF does not pass a predicate expression metadata filter, the server will deadlock. Fixed in version 4.8.0.14.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.8.0.11.
      • [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. Fixed in version 4.8.0.9.
      • [AER-6216] - (KVS) Dynamically increasing service context configuration item service-threads may cause an assert. Fixed in version 4.8.0.9.
    • Enterprise Only
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.8.0.17.
      • [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.8.0.15.
      • [AER-6250] - (UDF) Race between a background UDF scan/query internal transaction and a durable delete may cause a deadlock. Fixed in version 4.8.0.14.
      • [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.8.0.10.
      • [AER-6214] - (SECURITY) Specifying a whitelist with a maximum set of (32) networks causes a stack memory stomp. Fixed in version 4.8.0.9.

    Bug Fixes

    • Enterprise & Community
      • [AER-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive.
      • [AER-6194] - (GEO) For namespaces with data-in-memory true, GeoJSON particles allocate up to 2KB more than the reported particle size.
    • Enterprise Only
      • [AER-6195] - (MIGRATION) Theoretical race condition may cause delta migration to complete without sending all records.

  • 4.8.0.6
    Release Date: February 28, 2020
    • 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
      • 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-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.
      • [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.8.0.19.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.8.0.18.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 4.8.0.17.
      • [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.8.0.17.
      • [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.8.0.15.
      • [AER-6251] - (UDF) When a record UDF does not pass a predicate expression metadata filter, the server will deadlock. Fixed in version 4.8.0.14.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.8.0.11.
      • [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. Fixed in version 4.8.0.9.
      • [AER-6216] - (KVS) Dynamically increasing service context configuration item service-threads may cause an assert. Fixed in version 4.8.0.9.
      • [AER-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.8.0.8.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.8.0.8.
      • [AER-6194] - (GEO) For namespaces with data-in-memory true, GeoJSON particles allocate up to 2KB more than the reported particle size. Fixed in version 4.8.0.8.
    • Enterprise Only
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.8.0.17.
      • [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.8.0.15.
      • [AER-6250] - (UDF) Race between a background UDF scan/query internal transaction and a durable delete may cause a deadlock. Fixed in version 4.8.0.14.
      • [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.8.0.10.
      • [AER-6214] - (SECURITY) Specifying a whitelist with a maximum set of (32) networks causes a stack memory stomp. Fixed in version 4.8.0.9.
      • [AER-6195] - (MIGRATION) Theoretical race condition may cause delta migration to complete without sending all records. Fixed in version 4.8.0.8.

    Bug Fixes

    • Enterprise & Community
      • [AER-6181] - (INFO) Namespace context configuration item enable-benchmarks-ops-sub is not returned by get-config.
      • [AER-6189] - (UDF) List creation via UDF does not initialize list flags, which may inadvertently flag the list as ordered.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF.
    • Enterprise Only
      • [AER-6178] - (STORAGE) Setting storage context configuration item compression dynamically for storage-engine memory namespaces is not prevented and may cause a crash.

  • 4.8.0.5
    Release Date: January 21, 2020
    • 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
      • 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-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.
      • [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.8.0.19.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.8.0.18.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 4.8.0.17.
      • [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.8.0.17.
      • [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.8.0.15.
      • [AER-6251] - (UDF) When a record UDF does not pass a predicate expression metadata filter, the server will deadlock. Fixed in version 4.8.0.14.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.8.0.11.
      • [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. Fixed in version 4.8.0.9.
      • [AER-6216] - (KVS) Dynamically increasing service context configuration item service-threads may cause an assert. Fixed in version 4.8.0.9.
      • [AER-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.8.0.8.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.8.0.8.
      • [AER-6194] - (GEO) For namespaces with data-in-memory true, GeoJSON particles allocate up to 2KB more than the reported particle size. Fixed in version 4.8.0.8.
      • [AER-6181] - (INFO) Namespace context configuration item enable-benchmarks-ops-sub is not returned by get-config. Fixed in version 4.8.0.6.
      • [AER-6189] - (UDF) List creation via UDF does not initialize list flags, which may inadvertently flag the list as ordered. Fixed in version 4.8.0.6.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.8.0.6.
    • Enterprise Only
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.8.0.17.
      • [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.8.0.15.
      • [AER-6250] - (UDF) Race between a background UDF scan/query internal transaction and a durable delete may cause a deadlock. Fixed in version 4.8.0.14.
      • [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.8.0.10.
      • [AER-6214] - (SECURITY) Specifying a whitelist with a maximum set of (32) networks causes a stack memory stomp. Fixed in version 4.8.0.9.
      • [AER-6195] - (MIGRATION) Theoretical race condition may cause delta migration to complete without sending all records. Fixed in version 4.8.0.8.
      • [AER-6178] - (STORAGE) Setting storage context configuration item compression dynamically for storage-engine memory namespaces is not prevented and may cause a crash. Fixed in version 4.8.0.6.

    Bug Fixes

    • Enterprise & Community
      • [AER-6179] - (KVS) When upgrading from version earlier than 4.5.1, pre-existing eviction depth is not used during startup.
    • Enterprise Only
      • [AER-6170] - (XDR) Source node may crash when adding or removing namespaces in a destination cluster.
      • [AER-6172] - (XDR) Increasing datacenter context configuration item dc-connections dynamically may cause crash.

  • 4.8.0.4
    Release Date: January 15, 2020
    • 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
      • 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-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.
      • [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.8.0.19.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.8.0.18.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 4.8.0.17.
      • [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.8.0.17.
      • [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.8.0.15.
      • [AER-6251] - (UDF) When a record UDF does not pass a predicate expression metadata filter, the server will deadlock. Fixed in version 4.8.0.14.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.8.0.11.
      • [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. Fixed in version 4.8.0.9.
      • [AER-6216] - (KVS) Dynamically increasing service context configuration item service-threads may cause an assert. Fixed in version 4.8.0.9.
      • [AER-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.8.0.8.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.8.0.8.
      • [AER-6194] - (GEO) For namespaces with data-in-memory true, GeoJSON particles allocate up to 2KB more than the reported particle size. Fixed in version 4.8.0.8.
      • [AER-6181] - (INFO) Namespace context configuration item enable-benchmarks-ops-sub is not returned by get-config. Fixed in version 4.8.0.6.
      • [AER-6189] - (UDF) List creation via UDF does not initialize list flags, which may inadvertently flag the list as ordered. Fixed in version 4.8.0.6.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.8.0.6.
      • [AER-6179] - (KVS) When upgrading from version earlier than 4.5.1, pre-existing eviction depth is not used during startup. Fixed in version 4.8.0.5.
    • Enterprise Only
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.8.0.17.
      • [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.8.0.15.
      • [AER-6250] - (UDF) Race between a background UDF scan/query internal transaction and a durable delete may cause a deadlock. Fixed in version 4.8.0.14.
      • [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.8.0.10.
      • [AER-6214] - (SECURITY) Specifying a whitelist with a maximum set of (32) networks causes a stack memory stomp. Fixed in version 4.8.0.9.
      • [AER-6195] - (MIGRATION) Theoretical race condition may cause delta migration to complete without sending all records. Fixed in version 4.8.0.8.
      • [AER-6178] - (STORAGE) Setting storage context configuration item compression dynamically for storage-engine memory namespaces is not prevented and may cause a crash. Fixed in version 4.8.0.6.
      • [AER-6172] - (XDR) Increasing datacenter context configuration item dc-connections dynamically may cause crash. Fixed in version 4.8.0.5.
      • [AER-6170] - (XDR) Source node may crash when adding or removing namespaces in a destination cluster. Fixed in version 4.8.0.5.

    Bug Fixes

    • Enterprise Only
      • [AER-6175] - (BALANCE) For strong-consistency namespaces, appeal subsystem leaks memory, and has rare races which may cause crash or deadlock.

  • 4.8.0.3
    Release Date: January 6, 2020
    • 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
      • 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-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.
      • [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.8.0.19.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.8.0.18.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 4.8.0.17.
      • [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.8.0.17.
      • [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.8.0.15.
      • [AER-6251] - (UDF) When a record UDF does not pass a predicate expression metadata filter, the server will deadlock. Fixed in version 4.8.0.14.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.8.0.11.
      • [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. Fixed in version 4.8.0.9.
      • [AER-6216] - (KVS) Dynamically increasing service context configuration item service-threads may cause an assert. Fixed in version 4.8.0.9.
      • [AER-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.8.0.8.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.8.0.8.
      • [AER-6194] - (GEO) For namespaces with data-in-memory true, GeoJSON particles allocate up to 2KB more than the reported particle size. Fixed in version 4.8.0.8.
      • [AER-6181] - (INFO) Namespace context configuration item enable-benchmarks-ops-sub is not returned by get-config. Fixed in version 4.8.0.6.
      • [AER-6189] - (UDF) List creation via UDF does not initialize list flags, which may inadvertently flag the list as ordered. Fixed in version 4.8.0.6.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.8.0.6.
      • [AER-6179] - (KVS) When upgrading from version earlier than 4.5.1, pre-existing eviction depth is not used during startup. Fixed in version 4.8.0.5.
    • Enterprise Only
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.8.0.17.
      • [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.8.0.15.
      • [AER-6250] - (UDF) Race between a background UDF scan/query internal transaction and a durable delete may cause a deadlock. Fixed in version 4.8.0.14.
      • [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.8.0.10.
      • [AER-6214] - (SECURITY) Specifying a whitelist with a maximum set of (32) networks causes a stack memory stomp. Fixed in version 4.8.0.9.
      • [AER-6195] - (MIGRATION) Theoretical race condition may cause delta migration to complete without sending all records. Fixed in version 4.8.0.8.
      • [AER-6178] - (STORAGE) Setting storage context configuration item compression dynamically for storage-engine memory namespaces is not prevented and may cause a crash. Fixed in version 4.8.0.6.
      • [AER-6172] - (XDR) Increasing datacenter context configuration item dc-connections dynamically may cause crash. Fixed in version 4.8.0.5.
      • [AER-6170] - (XDR) Source node may crash when adding or removing namespaces in a destination cluster. Fixed in version 4.8.0.5.
      • [AER-6175] - (BALANCE) For strong-consistency namespaces, appeal subsystem leaks memory, and has rare races which may cause crash or deadlock. Fixed in version 4.8.0.4.

    Bug Fixes

    • Enterprise & Community
      • [AER-6174] - (KVS) For namespaces with data-in-memory true, a delete record op applied to a record with more than one bin may cause a crash.

  • 4.8.0.2
    Release Date: December 16, 2019
    • 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
      • 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-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.
      • [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.8.0.19.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.8.0.18.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 4.8.0.17.
      • [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.8.0.17.
      • [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.8.0.15.
      • [AER-6251] - (UDF) When a record UDF does not pass a predicate expression metadata filter, the server will deadlock. Fixed in version 4.8.0.14.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.8.0.11.
      • [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. Fixed in version 4.8.0.9.
      • [AER-6216] - (KVS) Dynamically increasing service context configuration item service-threads may cause an assert. Fixed in version 4.8.0.9.
      • [AER-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.8.0.8.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.8.0.8.
      • [AER-6194] - (GEO) For namespaces with data-in-memory true, GeoJSON particles allocate up to 2KB more than the reported particle size. Fixed in version 4.8.0.8.
      • [AER-6181] - (INFO) Namespace context configuration item enable-benchmarks-ops-sub is not returned by get-config. Fixed in version 4.8.0.6.
      • [AER-6189] - (UDF) List creation via UDF does not initialize list flags, which may inadvertently flag the list as ordered. Fixed in version 4.8.0.6.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.8.0.6.
      • [AER-6179] - (KVS) When upgrading from version earlier than 4.5.1, pre-existing eviction depth is not used during startup. Fixed in version 4.8.0.5.
      • [AER-6174] - (KVS) For namespaces with data-in-memory true, a delete record op applied to a record with more than one bin may cause a crash. Fixed in version 4.8.0.3.
    • Enterprise Only
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.8.0.17.
      • [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.8.0.15.
      • [AER-6250] - (UDF) Race between a background UDF scan/query internal transaction and a durable delete may cause a deadlock. Fixed in version 4.8.0.14.
      • [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.8.0.10.
      • [AER-6214] - (SECURITY) Specifying a whitelist with a maximum set of (32) networks causes a stack memory stomp. Fixed in version 4.8.0.9.
      • [AER-6195] - (MIGRATION) Theoretical race condition may cause delta migration to complete without sending all records. Fixed in version 4.8.0.8.
      • [AER-6178] - (STORAGE) Setting storage context configuration item compression dynamically for storage-engine memory namespaces is not prevented and may cause a crash. Fixed in version 4.8.0.6.
      • [AER-6172] - (XDR) Increasing datacenter context configuration item dc-connections dynamically may cause crash. Fixed in version 4.8.0.5.
      • [AER-6170] - (XDR) Source node may crash when adding or removing namespaces in a destination cluster. Fixed in version 4.8.0.5.
      • [AER-6175] - (BALANCE) For strong-consistency namespaces, appeal subsystem leaks memory, and has rare races which may cause crash or deadlock. Fixed in version 4.8.0.4.

    Bug Fixes

    • Enterprise Only
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item report-authentication true.

  • 4.8.0.1
    Release Date: December 12, 2019
    • 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
      • 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-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.
      • [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.8.0.19.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.8.0.18.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 4.8.0.17.
      • [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.8.0.17.
      • [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.8.0.15.
      • [AER-6251] - (UDF) When a record UDF does not pass a predicate expression metadata filter, the server will deadlock. Fixed in version 4.8.0.14.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.8.0.11.
      • [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. Fixed in version 4.8.0.9.
      • [AER-6216] - (KVS) Dynamically increasing service context configuration item service-threads may cause an assert. Fixed in version 4.8.0.9.
      • [AER-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.8.0.8.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.8.0.8.
      • [AER-6194] - (GEO) For namespaces with data-in-memory true, GeoJSON particles allocate up to 2KB more than the reported particle size. Fixed in version 4.8.0.8.
      • [AER-6181] - (INFO) Namespace context configuration item enable-benchmarks-ops-sub is not returned by get-config. Fixed in version 4.8.0.6.
      • [AER-6189] - (UDF) List creation via UDF does not initialize list flags, which may inadvertently flag the list as ordered. Fixed in version 4.8.0.6.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.8.0.6.
      • [AER-6179] - (KVS) When upgrading from version earlier than 4.5.1, pre-existing eviction depth is not used during startup. Fixed in version 4.8.0.5.
      • [AER-6174] - (KVS) For namespaces with data-in-memory true, a delete record op applied to a record with more than one bin may cause a crash. Fixed in version 4.8.0.3.
    • Enterprise Only
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.8.0.17.
      • [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.8.0.15.
      • [AER-6250] - (UDF) Race between a background UDF scan/query internal transaction and a durable delete may cause a deadlock. Fixed in version 4.8.0.14.
      • [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.8.0.10.
      • [AER-6214] - (SECURITY) Specifying a whitelist with a maximum set of (32) networks causes a stack memory stomp. Fixed in version 4.8.0.9.
      • [AER-6195] - (MIGRATION) Theoretical race condition may cause delta migration to complete without sending all records. Fixed in version 4.8.0.8.
      • [AER-6178] - (STORAGE) Setting storage context configuration item compression dynamically for storage-engine memory namespaces is not prevented and may cause a crash. Fixed in version 4.8.0.6.
      • [AER-6172] - (XDR) Increasing datacenter context configuration item dc-connections dynamically may cause crash. Fixed in version 4.8.0.5.
      • [AER-6170] - (XDR) Source node may crash when adding or removing namespaces in a destination cluster. Fixed in version 4.8.0.5.
      • [AER-6175] - (BALANCE) For strong-consistency namespaces, appeal subsystem leaks memory, and has rare races which may cause crash or deadlock. Fixed in version 4.8.0.4.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item report-authentication true. Fixed in version 4.8.0.2.

    New Features

    • Enterprise & Community
      • [AER-6145] - (PACKAGING) Added support for CentOS 8.
    • Enterprise Only
      • [AER-6136] - (KVS) Added support for client/server compression.
      • [AER-6164] - (STORAGE) Added value pmem for namespace context configuration item storage-engine, to use persistent memory for data storage.

    Improvements

    • Enterprise & Community
      • [AER-6134] - (KVS) Use separate write buffers for replicated and migrated records, to avoid polluting the post-write queue.
      • [AER-6141] - (KVS) Use keep-alive for client sockets.
      • [AER-6161] - (INFO) Added info command 'sindex-exists' to indicate whether a specified index exists.
      • [AER-6142] - (STATS) Removed 'svc-demarshal' and 'svc-queue' benchmark histograms, and added namespace context batch-sub-prestart benchmark histogram.
    • Enterprise Only
      • [AER-6167] - (DEPLOYMENT) Added pmem feature key to cover both index-type pmem and storage-engine pmem, deprecated 'pmem-index' and 'all-flash' feature keys.
      • [AER-6118] - (LOGGING) Changed warning text for internal user attempting login with external authentication mode to not mention 'ldap'.

    Bug Fixes

    • Enterprise Only
      • [AER-6155] - (XDR) Allow only 'v1' for the datacenter context configuration item http-version to avoid issues in HTTP v2.

    Updates

  • 4.7.0.26
    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-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.7.0.23.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.

    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.7.0.25
    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-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.7.0.26.
      • [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.7.0.23.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.

    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.7.0.23
    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-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.7.0.26.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.

    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.7.0.22
    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-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.7.0.26.
      • [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.7.0.23.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.

    Improvements

    • Enterprise & Community
      • [AER-6312] - (SECONDARY INDEX) When populating secondary indexes at startup, only read records in sets which have indexes.

    Bug Fixes

    • Enterprise & Community
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range.

  • 4.7.0.21
    Release Date: October 14, 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-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.7.0.26.
      • [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.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.

    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.7.0.19
    Release Date: September 18, 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-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.7.0.26.
      • [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.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 4.7.0.21.
      • [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.7.0.21.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.

    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.7.0.18
    Release Date: July 7, 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-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.7.0.26.
      • [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.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 4.7.0.21.
      • [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.7.0.21.
      • [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.7.0.19.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [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.7.0.19.

    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.7.0.17
    Release Date: June 18, 2020
    • 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.

    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-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.7.0.26.
      • [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.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 4.7.0.21.
      • [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.7.0.21.
      • [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.7.0.19.
      • [AER-6251] - (UDF) When a record UDF does not pass a predicate expression metadata filter, the server will deadlock. Fixed in version 4.7.0.18.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [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.7.0.19.
      • [AER-6250] - (UDF) Race between a background UDF scan/query internal transaction and a durable delete may cause a deadlock. Fixed in version 4.7.0.18.

    Improvements

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

  • 4.7.0.15
    Release Date: May 22, 2020
    • 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
      • 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-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.7.0.26.
      • [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.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 4.7.0.21.
      • [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.7.0.21.
      • [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.7.0.19.
      • [AER-6251] - (UDF) When a record UDF does not pass a predicate expression metadata filter, the server will deadlock. Fixed in version 4.7.0.18.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [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.7.0.19.
      • [AER-6250] - (UDF) Race between a background UDF scan/query internal transaction and a durable delete may cause a deadlock. Fixed in version 4.7.0.18.

    Bug Fixes

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

  • 4.7.0.14
    Release Date: May 15, 2020
    • 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
      • 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-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.7.0.26.
      • [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.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 4.7.0.21.
      • [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.7.0.21.
      • [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.7.0.19.
      • [AER-6251] - (UDF) When a record UDF does not pass a predicate expression metadata filter, the server will deadlock. Fixed in version 4.7.0.18.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.7.0.15.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [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.7.0.19.
      • [AER-6250] - (UDF) Race between a background UDF scan/query internal transaction and a durable delete may cause a deadlock. Fixed in version 4.7.0.18.

    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.7.0.13
    Release Date: April 17, 2020
    • 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
      • 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-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.7.0.26.
      • [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.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 4.7.0.21.
      • [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.7.0.21.
      • [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.7.0.19.
      • [AER-6251] - (UDF) When a record UDF does not pass a predicate expression metadata filter, the server will deadlock. Fixed in version 4.7.0.18.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.7.0.15.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [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.7.0.19.
      • [AER-6250] - (UDF) Race between a background UDF scan/query internal transaction and a durable delete may cause a deadlock. Fixed in version 4.7.0.18.
      • [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.7.0.14.

    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.
      • [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.7.0.12
    Release Date: March 19, 2020
    • 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
      • 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-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.7.0.26.
      • [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.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 4.7.0.21.
      • [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.7.0.21.
      • [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.7.0.19.
      • [AER-6251] - (UDF) When a record UDF does not pass a predicate expression metadata filter, the server will deadlock. Fixed in version 4.7.0.18.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.7.0.15.
      • [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. Fixed in version 4.7.0.13.
      • [AER-6216] - (KVS) Dynamically increasing service context configuration item service-threads may cause an assert. Fixed in version 4.7.0.13.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [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.7.0.19.
      • [AER-6250] - (UDF) Race between a background UDF scan/query internal transaction and a durable delete may cause a deadlock. Fixed in version 4.7.0.18.
      • [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.7.0.14.
      • [AER-6214] - (SECURITY) Specifying a whitelist with a maximum set of (32) networks causes a stack memory stomp. Fixed in version 4.7.0.13.

    Bug Fixes

    • Enterprise & Community
      • [AER-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive.
      • [AER-6194] - (GEO) For namespaces with data-in-memory true, GeoJSON particles allocate up to 2KB more than the reported particle size.
    • Enterprise Only
      • [AER-6195] - (MIGRATION) Theoretical race condition may cause delta migration to complete without sending all records.

  • 4.7.0.11
    Release Date: February 28, 2020
    • 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
      • 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-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.7.0.26.
      • [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.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 4.7.0.21.
      • [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.7.0.21.
      • [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.7.0.19.
      • [AER-6251] - (UDF) When a record UDF does not pass a predicate expression metadata filter, the server will deadlock. Fixed in version 4.7.0.18.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.7.0.15.
      • [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. Fixed in version 4.7.0.13.
      • [AER-6216] - (KVS) Dynamically increasing service context configuration item service-threads may cause an assert. Fixed in version 4.7.0.13.
      • [AER-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.7.0.12.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.7.0.12.
      • [AER-6194] - (GEO) For namespaces with data-in-memory true, GeoJSON particles allocate up to 2KB more than the reported particle size. Fixed in version 4.7.0.12.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [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.7.0.19.
      • [AER-6250] - (UDF) Race between a background UDF scan/query internal transaction and a durable delete may cause a deadlock. Fixed in version 4.7.0.18.
      • [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.7.0.14.
      • [AER-6214] - (SECURITY) Specifying a whitelist with a maximum set of (32) networks causes a stack memory stomp. Fixed in version 4.7.0.13.
      • [AER-6195] - (MIGRATION) Theoretical race condition may cause delta migration to complete without sending all records. Fixed in version 4.7.0.12.

    Bug Fixes

    • Enterprise & Community
      • [AER-6181] - (INFO) Namespace context configuration item enable-benchmarks-ops-sub is not returned by get-config.
      • [AER-6189] - (UDF) List creation via UDF does not initialize list flags, which may inadvertently flag the list as ordered.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF.
    • Enterprise Only
      • [AER-6178] - (STORAGE) Setting storage context configuration item compression dynamically for storage-engine memory namespaces is not prevented and may cause a crash.

  • 4.7.0.10
    Release Date: January 21, 2020
    • 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
      • 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-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.7.0.26.
      • [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.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 4.7.0.21.
      • [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.7.0.21.
      • [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.7.0.19.
      • [AER-6251] - (UDF) When a record UDF does not pass a predicate expression metadata filter, the server will deadlock. Fixed in version 4.7.0.18.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.7.0.15.
      • [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. Fixed in version 4.7.0.13.
      • [AER-6216] - (KVS) Dynamically increasing service context configuration item service-threads may cause an assert. Fixed in version 4.7.0.13.
      • [AER-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.7.0.12.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.7.0.12.
      • [AER-6194] - (GEO) For namespaces with data-in-memory true, GeoJSON particles allocate up to 2KB more than the reported particle size. Fixed in version 4.7.0.12.
      • [AER-6181] - (INFO) Namespace context configuration item enable-benchmarks-ops-sub is not returned by get-config. Fixed in version 4.7.0.11.
      • [AER-6189] - (UDF) List creation via UDF does not initialize list flags, which may inadvertently flag the list as ordered. Fixed in version 4.7.0.11.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.7.0.11.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [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.7.0.19.
      • [AER-6250] - (UDF) Race between a background UDF scan/query internal transaction and a durable delete may cause a deadlock. Fixed in version 4.7.0.18.
      • [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.7.0.14.
      • [AER-6214] - (SECURITY) Specifying a whitelist with a maximum set of (32) networks causes a stack memory stomp. Fixed in version 4.7.0.13.
      • [AER-6195] - (MIGRATION) Theoretical race condition may cause delta migration to complete without sending all records. Fixed in version 4.7.0.12.
      • [AER-6178] - (STORAGE) Setting storage context configuration item compression dynamically for storage-engine memory namespaces is not prevented and may cause a crash. Fixed in version 4.7.0.11.

    Bug Fixes

    • Enterprise & Community
      • [AER-6179] - (KVS) When upgrading from version earlier than 4.5.1, pre-existing eviction depth is not used during startup.
    • Enterprise Only
      • [AER-6170] - (XDR) Source node may crash when adding or removing namespaces in a destination cluster.
      • [AER-6172] - (XDR) Increasing datacenter context configuration item dc-connections dynamically may cause crash.

  • 4.7.0.9
    Release Date: January 15, 2020
    • 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
      • 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-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.7.0.26.
      • [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.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 4.7.0.21.
      • [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.7.0.21.
      • [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.7.0.19.
      • [AER-6251] - (UDF) When a record UDF does not pass a predicate expression metadata filter, the server will deadlock. Fixed in version 4.7.0.18.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.7.0.15.
      • [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. Fixed in version 4.7.0.13.
      • [AER-6216] - (KVS) Dynamically increasing service context configuration item service-threads may cause an assert. Fixed in version 4.7.0.13.
      • [AER-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.7.0.12.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.7.0.12.
      • [AER-6194] - (GEO) For namespaces with data-in-memory true, GeoJSON particles allocate up to 2KB more than the reported particle size. Fixed in version 4.7.0.12.
      • [AER-6181] - (INFO) Namespace context configuration item enable-benchmarks-ops-sub is not returned by get-config. Fixed in version 4.7.0.11.
      • [AER-6189] - (UDF) List creation via UDF does not initialize list flags, which may inadvertently flag the list as ordered. Fixed in version 4.7.0.11.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.7.0.11.
      • [AER-6179] - (KVS) When upgrading from version earlier than 4.5.1, pre-existing eviction depth is not used during startup. Fixed in version 4.7.0.10.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [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.7.0.19.
      • [AER-6250] - (UDF) Race between a background UDF scan/query internal transaction and a durable delete may cause a deadlock. Fixed in version 4.7.0.18.
      • [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.7.0.14.
      • [AER-6214] - (SECURITY) Specifying a whitelist with a maximum set of (32) networks causes a stack memory stomp. Fixed in version 4.7.0.13.
      • [AER-6195] - (MIGRATION) Theoretical race condition may cause delta migration to complete without sending all records. Fixed in version 4.7.0.12.
      • [AER-6178] - (STORAGE) Setting storage context configuration item compression dynamically for storage-engine memory namespaces is not prevented and may cause a crash. Fixed in version 4.7.0.11.
      • [AER-6172] - (XDR) Increasing datacenter context configuration item dc-connections dynamically may cause crash. Fixed in version 4.7.0.10.
      • [AER-6170] - (XDR) Source node may crash when adding or removing namespaces in a destination cluster. Fixed in version 4.7.0.10.

    Bug Fixes

    • Enterprise Only
      • [AER-6175] - (BALANCE) For strong-consistency namespaces, appeal subsystem leaks memory, and has rare races which may cause crash or deadlock.

  • 4.7.0.8
    Release Date: January 6, 2020
    • 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
      • 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-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.7.0.26.
      • [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.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 4.7.0.21.
      • [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.7.0.21.
      • [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.7.0.19.
      • [AER-6251] - (UDF) When a record UDF does not pass a predicate expression metadata filter, the server will deadlock. Fixed in version 4.7.0.18.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.7.0.15.
      • [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. Fixed in version 4.7.0.13.
      • [AER-6216] - (KVS) Dynamically increasing service context configuration item service-threads may cause an assert. Fixed in version 4.7.0.13.
      • [AER-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.7.0.12.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.7.0.12.
      • [AER-6194] - (GEO) For namespaces with data-in-memory true, GeoJSON particles allocate up to 2KB more than the reported particle size. Fixed in version 4.7.0.12.
      • [AER-6181] - (INFO) Namespace context configuration item enable-benchmarks-ops-sub is not returned by get-config. Fixed in version 4.7.0.11.
      • [AER-6189] - (UDF) List creation via UDF does not initialize list flags, which may inadvertently flag the list as ordered. Fixed in version 4.7.0.11.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.7.0.11.
      • [AER-6179] - (KVS) When upgrading from version earlier than 4.5.1, pre-existing eviction depth is not used during startup. Fixed in version 4.7.0.10.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [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.7.0.19.
      • [AER-6250] - (UDF) Race between a background UDF scan/query internal transaction and a durable delete may cause a deadlock. Fixed in version 4.7.0.18.
      • [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.7.0.14.
      • [AER-6214] - (SECURITY) Specifying a whitelist with a maximum set of (32) networks causes a stack memory stomp. Fixed in version 4.7.0.13.
      • [AER-6195] - (MIGRATION) Theoretical race condition may cause delta migration to complete without sending all records. Fixed in version 4.7.0.12.
      • [AER-6178] - (STORAGE) Setting storage context configuration item compression dynamically for storage-engine memory namespaces is not prevented and may cause a crash. Fixed in version 4.7.0.11.
      • [AER-6172] - (XDR) Increasing datacenter context configuration item dc-connections dynamically may cause crash. Fixed in version 4.7.0.10.
      • [AER-6170] - (XDR) Source node may crash when adding or removing namespaces in a destination cluster. Fixed in version 4.7.0.10.
      • [AER-6175] - (BALANCE) For strong-consistency namespaces, appeal subsystem leaks memory, and has rare races which may cause crash or deadlock. Fixed in version 4.7.0.9.

    Bug Fixes

    • Enterprise & Community
      • [AER-6174] - (KVS) For namespaces with data-in-memory true, a delete record op applied to a record with more than one bin may cause a crash.

  • 4.7.0.7
    Release Date: December 16, 2019
    • 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
      • 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-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.7.0.26.
      • [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.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 4.7.0.21.
      • [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.7.0.21.
      • [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.7.0.19.
      • [AER-6251] - (UDF) When a record UDF does not pass a predicate expression metadata filter, the server will deadlock. Fixed in version 4.7.0.18.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.7.0.15.
      • [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. Fixed in version 4.7.0.13.
      • [AER-6216] - (KVS) Dynamically increasing service context configuration item service-threads may cause an assert. Fixed in version 4.7.0.13.
      • [AER-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.7.0.12.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.7.0.12.
      • [AER-6194] - (GEO) For namespaces with data-in-memory true, GeoJSON particles allocate up to 2KB more than the reported particle size. Fixed in version 4.7.0.12.
      • [AER-6181] - (INFO) Namespace context configuration item enable-benchmarks-ops-sub is not returned by get-config. Fixed in version 4.7.0.11.
      • [AER-6189] - (UDF) List creation via UDF does not initialize list flags, which may inadvertently flag the list as ordered. Fixed in version 4.7.0.11.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.7.0.11.
      • [AER-6179] - (KVS) When upgrading from version earlier than 4.5.1, pre-existing eviction depth is not used during startup. Fixed in version 4.7.0.10.
      • [AER-6174] - (KVS) For namespaces with data-in-memory true, a delete record op applied to a record with more than one bin may cause a crash. Fixed in version 4.7.0.8.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [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.7.0.19.
      • [AER-6250] - (UDF) Race between a background UDF scan/query internal transaction and a durable delete may cause a deadlock. Fixed in version 4.7.0.18.
      • [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.7.0.14.
      • [AER-6214] - (SECURITY) Specifying a whitelist with a maximum set of (32) networks causes a stack memory stomp. Fixed in version 4.7.0.13.
      • [AER-6195] - (MIGRATION) Theoretical race condition may cause delta migration to complete without sending all records. Fixed in version 4.7.0.12.
      • [AER-6178] - (STORAGE) Setting storage context configuration item compression dynamically for storage-engine memory namespaces is not prevented and may cause a crash. Fixed in version 4.7.0.11.
      • [AER-6172] - (XDR) Increasing datacenter context configuration item dc-connections dynamically may cause crash. Fixed in version 4.7.0.10.
      • [AER-6170] - (XDR) Source node may crash when adding or removing namespaces in a destination cluster. Fixed in version 4.7.0.10.
      • [AER-6175] - (BALANCE) For strong-consistency namespaces, appeal subsystem leaks memory, and has rare races which may cause crash or deadlock. Fixed in version 4.7.0.9.

    Bug Fixes

    • Enterprise Only
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item report-authentication true.

  • 4.7.0.6
    Release Date: December 6, 2019
    • 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
      • 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-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.7.0.26.
      • [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.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 4.7.0.21.
      • [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.7.0.21.
      • [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.7.0.19.
      • [AER-6251] - (UDF) When a record UDF does not pass a predicate expression metadata filter, the server will deadlock. Fixed in version 4.7.0.18.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.7.0.15.
      • [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. Fixed in version 4.7.0.13.
      • [AER-6216] - (KVS) Dynamically increasing service context configuration item service-threads may cause an assert. Fixed in version 4.7.0.13.
      • [AER-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.7.0.12.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.7.0.12.
      • [AER-6194] - (GEO) For namespaces with data-in-memory true, GeoJSON particles allocate up to 2KB more than the reported particle size. Fixed in version 4.7.0.12.
      • [AER-6181] - (INFO) Namespace context configuration item enable-benchmarks-ops-sub is not returned by get-config. Fixed in version 4.7.0.11.
      • [AER-6189] - (UDF) List creation via UDF does not initialize list flags, which may inadvertently flag the list as ordered. Fixed in version 4.7.0.11.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.7.0.11.
      • [AER-6179] - (KVS) When upgrading from version earlier than 4.5.1, pre-existing eviction depth is not used during startup. Fixed in version 4.7.0.10.
      • [AER-6174] - (KVS) For namespaces with data-in-memory true, a delete record op applied to a record with more than one bin may cause a crash. Fixed in version 4.7.0.8.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [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.7.0.19.
      • [AER-6250] - (UDF) Race between a background UDF scan/query internal transaction and a durable delete may cause a deadlock. Fixed in version 4.7.0.18.
      • [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.7.0.14.
      • [AER-6214] - (SECURITY) Specifying a whitelist with a maximum set of (32) networks causes a stack memory stomp. Fixed in version 4.7.0.13.
      • [AER-6195] - (MIGRATION) Theoretical race condition may cause delta migration to complete without sending all records. Fixed in version 4.7.0.12.
      • [AER-6178] - (STORAGE) Setting storage context configuration item compression dynamically for storage-engine memory namespaces is not prevented and may cause a crash. Fixed in version 4.7.0.11.
      • [AER-6172] - (XDR) Increasing datacenter context configuration item dc-connections dynamically may cause crash. Fixed in version 4.7.0.10.
      • [AER-6170] - (XDR) Source node may crash when adding or removing namespaces in a destination cluster. Fixed in version 4.7.0.10.
      • [AER-6175] - (BALANCE) For strong-consistency namespaces, appeal subsystem leaks memory, and has rare races which may cause crash or deadlock. Fixed in version 4.7.0.9.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item report-authentication true. Fixed in version 4.7.0.7.

    Bug Fixes

    • Enterprise & Community
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure.
      • [AER-6159] - (INFO) The thread-traces info command can cause a deadlock.
      • [AER-6165] - (CDT) by_value_list and by_key_list OPs do not accept non-storage tokens such as WILDCARD.
    • Enterprise Only
      • [AER-6163] - (STORAGE) When using compression, migrated, replicated, or duplicate-resolved records may be incorrectly rejected by destination node for being too big.

  • 4.7.0.5
    Release Date: November 14, 2019
    • 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
      • 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-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.7.0.26.
      • [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.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 4.7.0.21.
      • [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.7.0.21.
      • [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.7.0.19.
      • [AER-6251] - (UDF) When a record UDF does not pass a predicate expression metadata filter, the server will deadlock. Fixed in version 4.7.0.18.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.7.0.15.
      • [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. Fixed in version 4.7.0.13.
      • [AER-6216] - (KVS) Dynamically increasing service context configuration item service-threads may cause an assert. Fixed in version 4.7.0.13.
      • [AER-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.7.0.12.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.7.0.12.
      • [AER-6194] - (GEO) For namespaces with data-in-memory true, GeoJSON particles allocate up to 2KB more than the reported particle size. Fixed in version 4.7.0.12.
      • [AER-6181] - (INFO) Namespace context configuration item enable-benchmarks-ops-sub is not returned by get-config. Fixed in version 4.7.0.11.
      • [AER-6189] - (UDF) List creation via UDF does not initialize list flags, which may inadvertently flag the list as ordered. Fixed in version 4.7.0.11.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.7.0.11.
      • [AER-6179] - (KVS) When upgrading from version earlier than 4.5.1, pre-existing eviction depth is not used during startup. Fixed in version 4.7.0.10.
      • [AER-6174] - (KVS) For namespaces with data-in-memory true, a delete record op applied to a record with more than one bin may cause a crash. Fixed in version 4.7.0.8.
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure. Fixed in version 4.7.0.6.
      • [AER-6159] - (INFO) The thread-traces info command can cause a deadlock. Fixed in version 4.7.0.6.
      • [AER-6165] - (CDT) by_value_list and by_key_list OPs do not accept non-storage tokens such as WILDCARD. Fixed in version 4.7.0.6.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [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.7.0.19.
      • [AER-6250] - (UDF) Race between a background UDF scan/query internal transaction and a durable delete may cause a deadlock. Fixed in version 4.7.0.18.
      • [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.7.0.14.
      • [AER-6214] - (SECURITY) Specifying a whitelist with a maximum set of (32) networks causes a stack memory stomp. Fixed in version 4.7.0.13.
      • [AER-6195] - (MIGRATION) Theoretical race condition may cause delta migration to complete without sending all records. Fixed in version 4.7.0.12.
      • [AER-6178] - (STORAGE) Setting storage context configuration item compression dynamically for storage-engine memory namespaces is not prevented and may cause a crash. Fixed in version 4.7.0.11.
      • [AER-6172] - (XDR) Increasing datacenter context configuration item dc-connections dynamically may cause crash. Fixed in version 4.7.0.10.
      • [AER-6170] - (XDR) Source node may crash when adding or removing namespaces in a destination cluster. Fixed in version 4.7.0.10.
      • [AER-6175] - (BALANCE) For strong-consistency namespaces, appeal subsystem leaks memory, and has rare races which may cause crash or deadlock. Fixed in version 4.7.0.9.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item report-authentication true. Fixed in version 4.7.0.7.
      • [AER-6163] - (STORAGE) When using compression, migrated, replicated, or duplicate-resolved records may be incorrectly rejected by destination node for being too big. Fixed in version 4.7.0.6.

    Bug Fixes

    • Enterprise & Community
      • [AER-6146] - (KVS) With debug-allocations enabled, a memory accounting array will eventually overflow and cause a crash.
    • Enterprise Only
      • [AER-6152] - (KVS) With auto-pin numa, namespaces with index-type pmem will assert at startup.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections.

  • 4.7.0.3
    Release Date: November 1, 2019
    • 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
      • 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-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.7.0.26.
      • [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.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 4.7.0.21.
      • [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.7.0.21.
      • [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.7.0.19.
      • [AER-6251] - (UDF) When a record UDF does not pass a predicate expression metadata filter, the server will deadlock. Fixed in version 4.7.0.18.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.7.0.15.
      • [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. Fixed in version 4.7.0.13.
      • [AER-6216] - (KVS) Dynamically increasing service context configuration item service-threads may cause an assert. Fixed in version 4.7.0.13.
      • [AER-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.7.0.12.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.7.0.12.
      • [AER-6194] - (GEO) For namespaces with data-in-memory true, GeoJSON particles allocate up to 2KB more than the reported particle size. Fixed in version 4.7.0.12.
      • [AER-6181] - (INFO) Namespace context configuration item enable-benchmarks-ops-sub is not returned by get-config. Fixed in version 4.7.0.11.
      • [AER-6189] - (UDF) List creation via UDF does not initialize list flags, which may inadvertently flag the list as ordered. Fixed in version 4.7.0.11.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.7.0.11.
      • [AER-6179] - (KVS) When upgrading from version earlier than 4.5.1, pre-existing eviction depth is not used during startup. Fixed in version 4.7.0.10.
      • [AER-6174] - (KVS) For namespaces with data-in-memory true, a delete record op applied to a record with more than one bin may cause a crash. Fixed in version 4.7.0.8.
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure. Fixed in version 4.7.0.6.
      • [AER-6159] - (INFO) The thread-traces info command can cause a deadlock. Fixed in version 4.7.0.6.
      • [AER-6165] - (CDT) by_value_list and by_key_list OPs do not accept non-storage tokens such as WILDCARD. Fixed in version 4.7.0.6.
      • [AER-6146] - (KVS) With debug-allocations enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.7.0.5.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [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.7.0.19.
      • [AER-6250] - (UDF) Race between a background UDF scan/query internal transaction and a durable delete may cause a deadlock. Fixed in version 4.7.0.18.
      • [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.7.0.14.
      • [AER-6214] - (SECURITY) Specifying a whitelist with a maximum set of (32) networks causes a stack memory stomp. Fixed in version 4.7.0.13.
      • [AER-6195] - (MIGRATION) Theoretical race condition may cause delta migration to complete without sending all records. Fixed in version 4.7.0.12.
      • [AER-6178] - (STORAGE) Setting storage context configuration item compression dynamically for storage-engine memory namespaces is not prevented and may cause a crash. Fixed in version 4.7.0.11.
      • [AER-6172] - (XDR) Increasing datacenter context configuration item dc-connections dynamically may cause crash. Fixed in version 4.7.0.10.
      • [AER-6170] - (XDR) Source node may crash when adding or removing namespaces in a destination cluster. Fixed in version 4.7.0.10.
      • [AER-6175] - (BALANCE) For strong-consistency namespaces, appeal subsystem leaks memory, and has rare races which may cause crash or deadlock. Fixed in version 4.7.0.9.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item report-authentication true. Fixed in version 4.7.0.7.
      • [AER-6163] - (STORAGE) When using compression, migrated, replicated, or duplicate-resolved records may be incorrectly rejected by destination node for being too big. Fixed in version 4.7.0.6.
      • [AER-6152] - (KVS) With auto-pin numa, namespaces with index-type pmem will assert at startup. Fixed in version 4.7.0.5.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.7.0.5.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.7.0.5.

    Bug Fixes

    • Enterprise & Community
      • [AER-6140] - (CDT) Map context unwind causes crash for namespaces with data-in-memory true when original map had incomplete order index.
      • [AER-6132] - (CDT) Get or remove by key for map with element count 1 and result type index or rank returns a list instead of a scalar.
    • Enterprise Only
      • [AER-6143] - (BALANCE) For strong-consistency namespaces, if quiescing nodes with non-roster nodes in the cluster, the wrong nodes may quiesce.

  • 4.7.0.2
    Release Date: September 30, 2019

    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-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.7.0.26.
      • [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.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 4.7.0.21.
      • [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.7.0.21.
      • [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.7.0.19.
      • [AER-6251] - (UDF) When a record UDF does not pass a predicate expression metadata filter, the server will deadlock. Fixed in version 4.7.0.18.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.7.0.15.
      • [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. Fixed in version 4.7.0.13.
      • [AER-6216] - (KVS) Dynamically increasing service context configuration item service-threads may cause an assert. Fixed in version 4.7.0.13.
      • [AER-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.7.0.12.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.7.0.12.
      • [AER-6194] - (GEO) For namespaces with data-in-memory true, GeoJSON particles allocate up to 2KB more than the reported particle size. Fixed in version 4.7.0.12.
      • [AER-6181] - (INFO) Namespace context configuration item enable-benchmarks-ops-sub is not returned by get-config. Fixed in version 4.7.0.11.
      • [AER-6189] - (UDF) List creation via UDF does not initialize list flags, which may inadvertently flag the list as ordered. Fixed in version 4.7.0.11.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.7.0.11.
      • [AER-6179] - (KVS) When upgrading from version earlier than 4.5.1, pre-existing eviction depth is not used during startup. Fixed in version 4.7.0.10.
      • [AER-6174] - (KVS) For namespaces with data-in-memory true, a delete record op applied to a record with more than one bin may cause a crash. Fixed in version 4.7.0.8.
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure. Fixed in version 4.7.0.6.
      • [AER-6159] - (INFO) The thread-traces info command can cause a deadlock. Fixed in version 4.7.0.6.
      • [AER-6165] - (CDT) by_value_list and by_key_list OPs do not accept non-storage tokens such as WILDCARD. Fixed in version 4.7.0.6.
      • [AER-6146] - (KVS) With debug-allocations enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.7.0.5.
      • [AER-6140] - (CDT) Map context unwind causes crash for namespaces with data-in-memory true when original map had incomplete order index. Fixed in version 4.7.0.3
      • [AER-6132] - (CDT) Get or remove by key for map with element count 1 and result type index or rank returns a list instead of a scalar. Fixed in version 4.7.0.3
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [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.7.0.19.
      • [AER-6250] - (UDF) Race between a background UDF scan/query internal transaction and a durable delete may cause a deadlock. Fixed in version 4.7.0.18.
      • [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.7.0.14.
      • [AER-6214] - (SECURITY) Specifying a whitelist with a maximum set of (32) networks causes a stack memory stomp. Fixed in version 4.7.0.13.
      • [AER-6195] - (MIGRATION) Theoretical race condition may cause delta migration to complete without sending all records. Fixed in version 4.7.0.12.
      • [AER-6178] - (STORAGE) Setting storage context configuration item compression dynamically for storage-engine memory namespaces is not prevented and may cause a crash. Fixed in version 4.7.0.11.
      • [AER-6172] - (XDR) Increasing datacenter context configuration item dc-connections dynamically may cause crash. Fixed in version 4.7.0.10.
      • [AER-6170] - (XDR) Source node may crash when adding or removing namespaces in a destination cluster. Fixed in version 4.7.0.10.
      • [AER-6175] - (BALANCE) For strong-consistency namespaces, appeal subsystem leaks memory, and has rare races which may cause crash or deadlock. Fixed in version 4.7.0.9.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item report-authentication true. Fixed in version 4.7.0.7.
      • [AER-6163] - (STORAGE) When using compression, migrated, replicated, or duplicate-resolved records may be incorrectly rejected by destination node for being too big. Fixed in version 4.7.0.6.
      • [AER-6152] - (KVS) With auto-pin numa, namespaces with index-type pmem will assert at startup. Fixed in version 4.7.0.5.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.7.0.5.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.7.0.5.
      • [AER-6143] - (BALANCE) For strong-consistency namespaces, if quiescing nodes with non-roster nodes in the cluster, the wrong nodes may quiesce. Fixed in version 4.7.0.3

    New Features

    • Enterprise & Community
      • [AER-6096] - (KVS) Added delete of entire record as an operation (e.g. to enable atomic read then delete).
      • [AER-6101] - (KVS) Added predicate filter support for batch, read, write, delete, and record UDF transactions.
      • [AER-6123] - (KVS) Added support for ADQ.
      • [AER-6109] - (SCAN) Added a new type of background scan and query that performs (write only) operations.
    • Enterprise Only
      • [AER-6124] - (XDR) Added LDAP login support for XDR.

    Improvements

    • Enterprise & Community
      • [AER-6112] - (KVS) Removed service context configuration items transaction-queues and transactions-threads-per-queue, and made service context configuration item service-threads dynamic.
      • [AER-6113] - (KVS) Increased maximum allowed value of storage context configuration item post-write-queue to 8192.
      • [AER-6100] - (SCAN) Scans now use their own thread(s) instead of sharing a thread pool, and are given a record-per-second limit instead of a priority.
      • [AER-6106] - (STATS) Added CPU usage in stats and log ticker.
    • Enterprise Only
      • [AER-6102] - (BALANCE) Changed default setting of namespace context configuration item prefer-uniform-balance to true.
      • [AER-6105] - (XDR) Certificate is presented to http destination when required for mutual authentication.

    Bug Fixes

    • Enterprise & Community
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate.
      • [AER-6128] - (BALANCE) For AP namespaces with prefer-uniform-balance true, non-optimal masters may be selected.

  • 4.6.0.21
    Release Date: September 18, 2020
    • A digitally signed feature key file is now required. (Enterprise Only)
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • For Aerospike Server versions prior to 4.7 XDR does not support LDAP logins.
    • 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-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.7.0.26.
      • [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.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 4.7.0.21.
      • [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.7.0.21.
      • [AER-6159] - (INFO) The thread-traces info command can cause a deadlock. Fixed in version 4.7.0.6.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [AER-6143] - (BALANCE) For strong-consistency namespaces, if quiescing nodes with non-roster nodes in the cluster, the wrong nodes may quiesce. Fixed in version 4.7.0.3.

    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.6.0.20
    Release Date: July 7, 2020
    • A digitally signed feature key file is now required. (Enterprise Only)
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • For Aerospike Server versions prior to 4.7 XDR does not support LDAP logins.
    • 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-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.7.0.26.
      • [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.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 4.7.0.21.
      • [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.7.0.21.
      • [AER-6159] - (INFO) The thread-traces info command can cause a deadlock. Fixed in version 4.7.0.6.
      • [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.6.0.21.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [AER-6143] - (BALANCE) For strong-consistency namespaces, if quiescing nodes with non-roster nodes in the cluster, the wrong nodes may quiesce. Fixed in version 4.7.0.3.
      • [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.6.0.21.

    Bug Fixes

    • Enterprise Only
      • [AER-6250] - (UDF) Race between a background UDF scan/query internal transaction and a durable delete may cause a deadlock.

  • 4.6.0.19
    Release Date: June 18, 2020
    • A digitally signed feature key file is now required. (Enterprise Only)
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • 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.
    • For Aerospike Server versions prior to 4.7 XDR does not support LDAP logins.
    • 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-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.7.0.26.
      • [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.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 4.7.0.21.
      • [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.7.0.21.
      • [AER-6159] - (INFO) The thread-traces info command can cause a deadlock. Fixed in version 4.7.0.6.
      • [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.6.0.21.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [AER-6143] - (BALANCE) For strong-consistency namespaces, if quiescing nodes with non-roster nodes in the cluster, the wrong nodes may quiesce. Fixed in version 4.7.0.3.
      • [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.6.0.21.

    Improvements

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

  • 4.6.0.17
    Release Date: May 22, 2020
    • A digitally signed feature key file is now required. (Enterprise Only)
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • 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.
    • For Aerospike Server versions prior to 4.7 XDR does not support LDAP logins.
    • 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
      • 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-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.7.0.26.
      • [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.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 4.7.0.21.
      • [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.7.0.21.
      • [AER-6159] - (INFO) The thread-traces info command can cause a deadlock. Fixed in version 4.7.0.6.
      • [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.6.0.21.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [AER-6143] - (BALANCE) For strong-consistency namespaces, if quiescing nodes with non-roster nodes in the cluster, the wrong nodes may quiesce. Fixed in version 4.7.0.3.
      • [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.6.0.21.

    Bug Fixes

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

  • 4.6.0.16
    Release Date: May 15, 2020
    • A digitally signed feature key file is now required. (Enterprise Only)
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • 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.
    • For Aerospike Server versions prior to 4.7 XDR does not support LDAP logins.
    • 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
      • 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-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.7.0.26.
      • [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.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 4.7.0.21.
      • [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.7.0.21.
      • [AER-6159] - (INFO) The thread-traces info command can cause a deadlock. Fixed in version 4.7.0.6.
      • [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.6.0.21.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.6.0.17.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [AER-6143] - (BALANCE) For strong-consistency namespaces, if quiescing nodes with non-roster nodes in the cluster, the wrong nodes may quiesce. Fixed in version 4.7.0.3.
      • [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.6.0.21.

    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.6.0.15
    Release Date: April 17, 2020
    • A digitally signed feature key file is now required. (Enterprise Only)
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • 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.
    • For Aerospike Server versions prior to 4.7 XDR does not support LDAP logins.
    • 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
      • 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-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.7.0.26.
      • [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.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 4.7.0.21.
      • [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.7.0.21.
      • [AER-6159] - (INFO) The thread-traces info command can cause a deadlock. Fixed in version 4.7.0.6.
      • [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.6.0.21.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.6.0.17.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [AER-6143] - (BALANCE) For strong-consistency namespaces, if quiescing nodes with non-roster nodes in the cluster, the wrong nodes may quiesce. Fixed in version 4.7.0.3.
      • [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.6.0.21.
      • [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.6.0.16.

    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.
    • Enterprise Only
      • [AER-6214] - (SECURITY) Specifying a whitelist with a maximum set of (32) networks causes a stack memory stomp.

  • 4.6.0.14
    Release Date: March 19, 2020
    • A digitally signed feature key file is now required. (Enterprise Only)
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • 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.
    • For Aerospike Server versions prior to 4.7 XDR does not support LDAP logins.
    • 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
      • 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-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.7.0.26.
      • [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.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 4.7.0.21.
      • [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.7.0.21.
      • [AER-6159] - (INFO) The thread-traces info command can cause a deadlock. Fixed in version 4.7.0.6.
      • [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.6.0.21.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.6.0.17.
      • [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. Fixed in version 4.6.0.15.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [AER-6143] - (BALANCE) For strong-consistency namespaces, if quiescing nodes with non-roster nodes in the cluster, the wrong nodes may quiesce. Fixed in version 4.7.0.3.
      • [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.6.0.21.
      • [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.6.0.16.
      • [AER-6214] - (SECURITY) Specifying a whitelist with a maximum set of (32) networks causes a stack memory stomp. Fixed in version 4.6.0.15.

    Bug Fixes

    • Enterprise & Community
      • [AER-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive.
      • [AER-6194] - (GEO) For namespaces with data-in-memory true, GeoJSON particles allocate up to 2KB more than the reported particle size.
    • Enterprise Only
      • [AER-6195] - (MIGRATION) Theoretical race condition may cause delta migration to complete without sending all records.

  • 4.6.0.13
    Release Date: February 28, 2020
    • A digitally signed feature key file is now required. (Enterprise Only)
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • 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.
    • For Aerospike Server versions prior to 4.7 XDR does not support LDAP logins.
    • 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
      • 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-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.7.0.26.
      • [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.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 4.7.0.21.
      • [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.7.0.21.
      • [AER-6159] - (INFO) The thread-traces info command can cause a deadlock. Fixed in version 4.7.0.6.
      • [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.6.0.21.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.6.0.17.
      • [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. Fixed in version 4.6.0.15.
      • [AER-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.6.0.14.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.6.0.14.
      • [AER-6194] - (GEO) For namespaces with data-in-memory true, GeoJSON particles allocate up to 2KB more than the reported particle size. Fixed in version 4.6.0.14.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [AER-6143] - (BALANCE) For strong-consistency namespaces, if quiescing nodes with non-roster nodes in the cluster, the wrong nodes may quiesce. Fixed in version 4.7.0.3.
      • [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.6.0.21.
      • [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.6.0.16.
      • [AER-6214] - (SECURITY) Specifying a whitelist with a maximum set of (32) networks causes a stack memory stomp. Fixed in version 4.6.0.15.
      • [AER-6195] - (MIGRATION) Theoretical race condition may cause delta migration to complete without sending all records. Fixed in version 4.6.0.14.

    Bug Fixes

    • Enterprise & Community
      • [AER-6189] - (UDF) List creation via UDF does not initialize list flags, which may inadvertently flag the list as ordered.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF.
    • Enterprise Only
      • [AER-6178] - (STORAGE) Setting storage context configuration item compression dynamically for storage-engine memory namespaces is not prevented and may cause a crash.

  • 4.6.0.12
    Release Date: January 21, 2020
    • A digitally signed feature key file is now required. (Enterprise Only)
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • 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.
    • For Aerospike Server versions prior to 4.7 XDR does not support LDAP logins.
    • 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
      • 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-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.7.0.26.
      • [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.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 4.7.0.21.
      • [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.7.0.21.
      • [AER-6159] - (INFO) The thread-traces info command can cause a deadlock. Fixed in version 4.7.0.6.
      • [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.6.0.21.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.6.0.17.
      • [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. Fixed in version 4.6.0.15.
      • [AER-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.6.0.14.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.6.0.14.
      • [AER-6194] - (GEO) For namespaces with data-in-memory true, GeoJSON particles allocate up to 2KB more than the reported particle size. Fixed in version 4.6.0.14.
      • [AER-6189] - (UDF) List creation via UDF does not initialize list flags, which may inadvertently flag the list as ordered. Fixed in version 4.6.0.13.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [AER-6143] - (BALANCE) For strong-consistency namespaces, if quiescing nodes with non-roster nodes in the cluster, the wrong nodes may quiesce. Fixed in version 4.7.0.3.
      • [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.6.0.21.
      • [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.6.0.16.
      • [AER-6214] - (SECURITY) Specifying a whitelist with a maximum set of (32) networks causes a stack memory stomp. Fixed in version 4.6.0.15.
      • [AER-6195] - (MIGRATION) Theoretical race condition may cause delta migration to complete without sending all records. Fixed in version 4.6.0.14.
      • [AER-6178] - (STORAGE) Setting storage context configuration item compression dynamically for storage-engine memory namespaces is not prevented and may cause a crash. Fixed in version 4.6.0.13.

    Bug Fixes

    • Enterprise & Community
      • [AER-6179] - (KVS) When upgrading from version earlier than 4.5.1, pre-existing eviction depth is not used during startup.
    • Enterprise Only
      • [AER-6170] - (XDR) Source node may crash when adding or removing namespaces in a destination cluster.
      • [AER-6172] - (XDR) Increasing datacenter context configuration item dc-connections dynamically may cause crash.

  • 4.6.0.11
    Release Date: January 15, 2020
    • A digitally signed feature key file is now required. (Enterprise Only)
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • 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.
    • For Aerospike Server versions prior to 4.7 XDR does not support LDAP logins.
    • 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
      • 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-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.7.0.26.
      • [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.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 4.7.0.21.
      • [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.7.0.21.
      • [AER-6159] - (INFO) The thread-traces info command can cause a deadlock. Fixed in version 4.7.0.6.
      • [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.6.0.21.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.6.0.17.
      • [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. Fixed in version 4.6.0.15.
      • [AER-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.6.0.14.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.6.0.14.
      • [AER-6194] - (GEO) For namespaces with data-in-memory true, GeoJSON particles allocate up to 2KB more than the reported particle size. Fixed in version 4.6.0.14.
      • [AER-6189] - (UDF) List creation via UDF does not initialize list flags, which may inadvertently flag the list as ordered. Fixed in version 4.6.0.13.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [AER-6179] - (KVS) When upgrading from version earlier than 4.5.1, pre-existing eviction depth is not used during startup. Fixed in version 4.6.0.12.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [AER-6143] - (BALANCE) For strong-consistency namespaces, if quiescing nodes with non-roster nodes in the cluster, the wrong nodes may quiesce. Fixed in version 4.7.0.3.
      • [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.6.0.21.
      • [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.6.0.16.
      • [AER-6214] - (SECURITY) Specifying a whitelist with a maximum set of (32) networks causes a stack memory stomp. Fixed in version 4.6.0.15.
      • [AER-6195] - (MIGRATION) Theoretical race condition may cause delta migration to complete without sending all records. Fixed in version 4.6.0.14.
      • [AER-6178] - (STORAGE) Setting storage context configuration item compression dynamically for storage-engine memory namespaces is not prevented and may cause a crash. Fixed in version 4.6.0.13.
      • [AER-6172] - (XDR) Increasing datacenter context configuration item dc-connections dynamically may cause crash. Fixed in version 4.6.0.12.
      • [AER-6170] - (XDR) Source node may crash when adding or removing namespaces in a destination cluster. Fixed in version 4.6.0.12.

    Bug Fixes

    • Enterprise Only
      • [AER-6175] - (BALANCE) For strong-consistency namespaces, appeal subsystem leaks memory, and has rare races which may cause crash or deadlock.

  • 4.6.0.10
    Release Date: December 16, 2019
    • A digitally signed feature key file is now required. (Enterprise Only)
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • 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.
    • For Aerospike Server versions prior to 4.7 XDR does not support LDAP logins.
    • 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
      • 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-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.7.0.26.
      • [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.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 4.7.0.21.
      • [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.7.0.21.
      • [AER-6159] - (INFO) The thread-traces info command can cause a deadlock. Fixed in version 4.7.0.6.
      • [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.6.0.21.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.6.0.17.
      • [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. Fixed in version 4.6.0.15.
      • [AER-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.6.0.14.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.6.0.14.
      • [AER-6194] - (GEO) For namespaces with data-in-memory true, GeoJSON particles allocate up to 2KB more than the reported particle size. Fixed in version 4.6.0.14.
      • [AER-6189] - (UDF) List creation via UDF does not initialize list flags, which may inadvertently flag the list as ordered. Fixed in version 4.6.0.13.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [AER-6179] - (KVS) When upgrading from version earlier than 4.5.1, pre-existing eviction depth is not used during startup. Fixed in version 4.6.0.12.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [AER-6143] - (BALANCE) For strong-consistency namespaces, if quiescing nodes with non-roster nodes in the cluster, the wrong nodes may quiesce. Fixed in version 4.7.0.3.
      • [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.6.0.21.
      • [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.6.0.16.
      • [AER-6214] - (SECURITY) Specifying a whitelist with a maximum set of (32) networks causes a stack memory stomp. Fixed in version 4.6.0.15.
      • [AER-6195] - (MIGRATION) Theoretical race condition may cause delta migration to complete without sending all records. Fixed in version 4.6.0.14.
      • [AER-6178] - (STORAGE) Setting storage context configuration item compression dynamically for storage-engine memory namespaces is not prevented and may cause a crash. Fixed in version 4.6.0.13.
      • [AER-6172] - (XDR) Increasing datacenter context configuration item dc-connections dynamically may cause crash. Fixed in version 4.6.0.12.
      • [AER-6170] - (XDR) Source node may crash when adding or removing namespaces in a destination cluster. Fixed in version 4.6.0.12.
      • [AER-6175] - (BALANCE) For strong-consistency namespaces, appeal subsystem leaks memory, and has rare races which may cause crash or deadlock. Fixed in version 4.6.0.11.

    Bug Fixes

    • Enterprise Only
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item report-authentication true.

  • 4.6.0.9
    Release Date: December 6, 2019
    • A digitally signed feature key file is now required. (Enterprise Only)
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • 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.
    • For Aerospike Server versions prior to 4.7 XDR does not support LDAP logins.
    • 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
      • 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-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.7.0.26.
      • [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.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 4.7.0.21.
      • [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.7.0.21.
      • [AER-6159] - (INFO) The thread-traces info command can cause a deadlock. Fixed in version 4.7.0.6.
      • [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.6.0.21.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.6.0.17.
      • [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. Fixed in version 4.6.0.15.
      • [AER-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.6.0.14.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.6.0.14.
      • [AER-6194] - (GEO) For namespaces with data-in-memory true, GeoJSON particles allocate up to 2KB more than the reported particle size. Fixed in version 4.6.0.14.
      • [AER-6189] - (UDF) List creation via UDF does not initialize list flags, which may inadvertently flag the list as ordered. Fixed in version 4.6.0.13.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [AER-6179] - (KVS) When upgrading from version earlier than 4.5.1, pre-existing eviction depth is not used during startup. Fixed in version 4.6.0.12.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [AER-6143] - (BALANCE) For strong-consistency namespaces, if quiescing nodes with non-roster nodes in the cluster, the wrong nodes may quiesce. Fixed in version 4.7.0.3.
      • [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.6.0.21.
      • [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.6.0.16.
      • [AER-6214] - (SECURITY) Specifying a whitelist with a maximum set of (32) networks causes a stack memory stomp. Fixed in version 4.6.0.15.
      • [AER-6195] - (MIGRATION) Theoretical race condition may cause delta migration to complete without sending all records. Fixed in version 4.6.0.14.
      • [AER-6178] - (STORAGE) Setting storage context configuration item compression dynamically for storage-engine memory namespaces is not prevented and may cause a crash. Fixed in version 4.6.0.13.
      • [AER-6172] - (XDR) Increasing datacenter context configuration item dc-connections dynamically may cause crash. Fixed in version 4.6.0.12.
      • [AER-6170] - (XDR) Source node may crash when adding or removing namespaces in a destination cluster. Fixed in version 4.6.0.12.
      • [AER-6175] - (BALANCE) For strong-consistency namespaces, appeal subsystem leaks memory, and has rare races which may cause crash or deadlock. Fixed in version 4.6.0.11.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item report-authentication true. Fixed in version 4.6.0.10.

    Bug Fixes

    • Enterprise & Community
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure.
      • [AER-6165] - (CDT) by_value_list and by_key_list OPs do not accept non-storage tokens such as WILDCARD.
    • Enterprise Only
      • [AER-6163] - (STORAGE) When using compression, migrated, replicated, or duplicate-resolved records may be incorrectly rejected by destination node for being too big.

  • 4.6.0.8
    Release Date: November 14, 2019
    • A digitally signed feature key file is now required. (Enterprise Only)
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • 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.
    • For Aerospike Server versions prior to 4.7 XDR does not support LDAP logins.
    • 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
      • 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-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.7.0.26.
      • [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.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 4.7.0.21.
      • [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.7.0.21.
      • [AER-6159] - (INFO) The thread-traces info command can cause a deadlock. Fixed in version 4.7.0.6.
      • [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.6.0.21.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.6.0.17.
      • [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. Fixed in version 4.6.0.15.
      • [AER-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.6.0.14.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.6.0.14.
      • [AER-6194] - (GEO) For namespaces with data-in-memory true, GeoJSON particles allocate up to 2KB more than the reported particle size. Fixed in version 4.6.0.14.
      • [AER-6189] - (UDF) List creation via UDF does not initialize list flags, which may inadvertently flag the list as ordered. Fixed in version 4.6.0.13.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [AER-6179] - (KVS) When upgrading from version earlier than 4.5.1, pre-existing eviction depth is not used during startup. Fixed in version 4.6.0.12.
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure. Fixed in version 4.6.0.9.
      • [AER-6165] - (CDT) by_value_list and by_key_list OPs do not accept non-storage tokens such as WILDCARD. Fixed in version 4.6.0.9.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [AER-6143] - (BALANCE) For strong-consistency namespaces, if quiescing nodes with non-roster nodes in the cluster, the wrong nodes may quiesce. Fixed in version 4.7.0.3.
      • [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.6.0.21.
      • [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.6.0.16.
      • [AER-6214] - (SECURITY) Specifying a whitelist with a maximum set of (32) networks causes a stack memory stomp. Fixed in version 4.6.0.15.
      • [AER-6195] - (MIGRATION) Theoretical race condition may cause delta migration to complete without sending all records. Fixed in version 4.6.0.14.
      • [AER-6178] - (STORAGE) Setting storage context configuration item compression dynamically for storage-engine memory namespaces is not prevented and may cause a crash. Fixed in version 4.6.0.13.
      • [AER-6172] - (XDR) Increasing datacenter context configuration item dc-connections dynamically may cause crash. Fixed in version 4.6.0.12.
      • [AER-6170] - (XDR) Source node may crash when adding or removing namespaces in a destination cluster. Fixed in version 4.6.0.12.
      • [AER-6175] - (BALANCE) For strong-consistency namespaces, appeal subsystem leaks memory, and has rare races which may cause crash or deadlock. Fixed in version 4.6.0.11.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item report-authentication true. Fixed in version 4.6.0.10.
      • [AER-6163] - (STORAGE) When using compression, migrated, replicated, or duplicate-resolved records may be incorrectly rejected by destination node for being too big. Fixed in version 4.6.0.9.

    Bug Fixes

    • Enterprise & Community
      • [AER-6146] - (KVS) With debug-allocations enabled, a memory accounting array will eventually overflow and cause a crash.
    • Enterprise Only
      • [AER-6152] - (KVS) With auto-pin numa, namespaces with index-type pmem will assert at startup.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections.

  • 4.6.0.6
    Release Date: November 1, 2019
    • A digitally signed feature key file is now required. (Enterprise Only)
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • 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.
    • For Aerospike Server versions prior to 4.7 XDR does not support LDAP logins.
    • 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
      • 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-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.7.0.26.
      • [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.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 4.7.0.21.
      • [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.7.0.21.
      • [AER-6159] - (INFO) The thread-traces info command can cause a deadlock. Fixed in version 4.7.0.6.
      • [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.6.0.21.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.6.0.17.
      • [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. Fixed in version 4.6.0.15.
      • [AER-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.6.0.14.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.6.0.14.
      • [AER-6194] - (GEO) For namespaces with data-in-memory true, GeoJSON particles allocate up to 2KB more than the reported particle size. Fixed in version 4.6.0.14.
      • [AER-6189] - (UDF) List creation via UDF does not initialize list flags, which may inadvertently flag the list as ordered. Fixed in version 4.6.0.13.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [AER-6179] - (KVS) When upgrading from version earlier than 4.5.1, pre-existing eviction depth is not used during startup. Fixed in version 4.6.0.12.
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure. Fixed in version 4.6.0.9.
      • [AER-6165] - (CDT) by_value_list and by_key_list OPs do not accept non-storage tokens such as WILDCARD. Fixed in version 4.6.0.9.
      • [AER-6146] - (KVS) With debug-allocations enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.6.0.8.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [AER-6143] - (BALANCE) For strong-consistency namespaces, if quiescing nodes with non-roster nodes in the cluster, the wrong nodes may quiesce. Fixed in version 4.7.0.3.
      • [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.6.0.21.
      • [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.6.0.16.
      • [AER-6214] - (SECURITY) Specifying a whitelist with a maximum set of (32) networks causes a stack memory stomp. Fixed in version 4.6.0.15.
      • [AER-6195] - (MIGRATION) Theoretical race condition may cause delta migration to complete without sending all records. Fixed in version 4.6.0.14.
      • [AER-6178] - (STORAGE) Setting storage context configuration item compression dynamically for storage-engine memory namespaces is not prevented and may cause a crash. Fixed in version 4.6.0.13.
      • [AER-6172] - (XDR) Increasing datacenter context configuration item dc-connections dynamically may cause crash. Fixed in version 4.6.0.12.
      • [AER-6170] - (XDR) Source node may crash when adding or removing namespaces in a destination cluster. Fixed in version 4.6.0.12.
      • [AER-6175] - (BALANCE) For strong-consistency namespaces, appeal subsystem leaks memory, and has rare races which may cause crash or deadlock. Fixed in version 4.6.0.11.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item report-authentication true. Fixed in version 4.6.0.10.
      • [AER-6163] - (STORAGE) When using compression, migrated, replicated, or duplicate-resolved records may be incorrectly rejected by destination node for being too big. Fixed in version 4.6.0.9.
      • [AER-6152] - (KVS) With auto-pin numa, namespaces with index-type pmem will assert at startup. Fixed in version 4.6.0.8.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.6.0.8.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.6.0.8.

    Bug Fixes

    • Enterprise & Community
      • [AER-6140] - (CDT) Map context unwind causes crash for namespaces with data-in-memory true when original map had incomplete order index.
      • [AER-6132] - (CDT) Get or remove by key for map with element count 1 and result type index or rank returns a list instead of a scalar.

  • 4.6.0.5
    Release Date: October 3, 2019
    • A digitally signed feature key file is now required. (Enterprise Only)
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • 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.
    • For Aerospike Server versions prior to 4.7 XDR does not support LDAP logins.
    • 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
      • 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-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.7.0.26.
      • [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.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 4.7.0.21.
      • [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.7.0.21.
      • [AER-6159] - (INFO) The thread-traces info command can cause a deadlock. Fixed in version 4.7.0.6.
      • [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.6.0.21.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.6.0.17.
      • [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. Fixed in version 4.6.0.15.
      • [AER-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.6.0.14.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.6.0.14.
      • [AER-6194] - (GEO) For namespaces with data-in-memory true, GeoJSON particles allocate up to 2KB more than the reported particle size. Fixed in version 4.6.0.14.
      • [AER-6189] - (UDF) List creation via UDF does not initialize list flags, which may inadvertently flag the list as ordered. Fixed in version 4.6.0.13.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [AER-6179] - (KVS) When upgrading from version earlier than 4.5.1, pre-existing eviction depth is not used during startup. Fixed in version 4.6.0.12.
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure. Fixed in version 4.6.0.9.
      • [AER-6165] - (CDT) by_value_list and by_key_list OPs do not accept non-storage tokens such as WILDCARD. Fixed in version 4.6.0.9.
      • [AER-6146] - (KVS) With debug-allocations enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.6.0.8.
      • [AER-6140] - (CDT) Map context unwind causes crash for namespaces with data-in-memory true when original map had incomplete order index. Fixed in version 4.6.0.6.
      • [AER-6132] - (CDT) Get or remove by key for map with element count 1 and result type index or rank returns a list instead of a scalar. Fixed in version 4.6.0.6.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [AER-6143] - (BALANCE) For strong-consistency namespaces, if quiescing nodes with non-roster nodes in the cluster, the wrong nodes may quiesce. Fixed in version 4.7.0.3.
      • [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.6.0.21.
      • [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.6.0.16.
      • [AER-6214] - (SECURITY) Specifying a whitelist with a maximum set of (32) networks causes a stack memory stomp. Fixed in version 4.6.0.15.
      • [AER-6195] - (MIGRATION) Theoretical race condition may cause delta migration to complete without sending all records. Fixed in version 4.6.0.14.
      • [AER-6178] - (STORAGE) Setting storage context configuration item compression dynamically for storage-engine memory namespaces is not prevented and may cause a crash. Fixed in version 4.6.0.13.
      • [AER-6172] - (XDR) Increasing datacenter context configuration item dc-connections dynamically may cause crash. Fixed in version 4.6.0.12.
      • [AER-6170] - (XDR) Source node may crash when adding or removing namespaces in a destination cluster. Fixed in version 4.6.0.12.
      • [AER-6175] - (BALANCE) For strong-consistency namespaces, appeal subsystem leaks memory, and has rare races which may cause crash or deadlock. Fixed in version 4.6.0.11.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item report-authentication true. Fixed in version 4.6.0.10.
      • [AER-6163] - (STORAGE) When using compression, migrated, replicated, or duplicate-resolved records may be incorrectly rejected by destination node for being too big. Fixed in version 4.6.0.9.
      • [AER-6152] - (KVS) With auto-pin numa, namespaces with index-type pmem will assert at startup. Fixed in version 4.6.0.8.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.6.0.8.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.6.0.8.

    Bug Fixes

    • Enterprise & Community
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate.
      • [AER-6128] - (BALANCE) For AP namespaces with prefer-uniform-balance true, non-optimal masters may be selected.

  • 4.6.0.4
    Release Date: August 28, 2019
    • A digitally signed feature key file is now required. (Enterprise Only)
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • 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.
    • For Aerospike Server versions prior to 4.7 XDR does not support LDAP logins.
    • 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
      • 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-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.7.0.26.
      • [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.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 4.7.0.21.
      • [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.7.0.21.
      • [AER-6159] - (INFO) The thread-traces info command can cause a deadlock. Fixed in version 4.7.0.6.
      • [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.6.0.21.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.6.0.17.
      • [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. Fixed in version 4.6.0.15.
      • [AER-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.6.0.14.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.6.0.14.
      • [AER-6194] - (GEO) For namespaces with data-in-memory true, GeoJSON particles allocate up to 2KB more than the reported particle size. Fixed in version 4.6.0.14.
      • [AER-6189] - (UDF) List creation via UDF does not initialize list flags, which may inadvertently flag the list as ordered. Fixed in version 4.6.0.13.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [AER-6179] - (KVS) When upgrading from version earlier than 4.5.1, pre-existing eviction depth is not used during startup. Fixed in version 4.6.0.12.
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure. Fixed in version 4.6.0.9.
      • [AER-6165] - (CDT) by_value_list and by_key_list OPs do not accept non-storage tokens such as WILDCARD. Fixed in version 4.6.0.9.
      • [AER-6146] - (KVS) With debug-allocations enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.6.0.8.
      • [AER-6140] - (CDT) Map context unwind causes crash for namespaces with data-in-memory true when original map had incomplete order index. Fixed in version 4.6.0.6.
      • [AER-6132] - (CDT) Get or remove by key for map with element count 1 and result type index or rank returns a list instead of a scalar. Fixed in version 4.6.0.6.
      • [AER-6128] - (BALANCE) For AP namespaces with prefer-uniform-balance true, non-optimal masters may be selected. Fixed in version 4.6.0.5.
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.6.0.5.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [AER-6143] - (BALANCE) For strong-consistency namespaces, if quiescing nodes with non-roster nodes in the cluster, the wrong nodes may quiesce. Fixed in version 4.7.0.3.
      • [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.6.0.21.
      • [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.6.0.16.
      • [AER-6214] - (SECURITY) Specifying a whitelist with a maximum set of (32) networks causes a stack memory stomp. Fixed in version 4.6.0.15.
      • [AER-6195] - (MIGRATION) Theoretical race condition may cause delta migration to complete without sending all records. Fixed in version 4.6.0.14.
      • [AER-6178] - (STORAGE) Setting storage context configuration item compression dynamically for storage-engine memory namespaces is not prevented and may cause a crash. Fixed in version 4.6.0.13.
      • [AER-6172] - (XDR) Increasing datacenter context configuration item dc-connections dynamically may cause crash. Fixed in version 4.6.0.12.
      • [AER-6170] - (XDR) Source node may crash when adding or removing namespaces in a destination cluster. Fixed in version 4.6.0.12.
      • [AER-6175] - (BALANCE) For strong-consistency namespaces, appeal subsystem leaks memory, and has rare races which may cause crash or deadlock. Fixed in version 4.6.0.11.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item report-authentication true. Fixed in version 4.6.0.10.
      • [AER-6163] - (STORAGE) When using compression, migrated, replicated, or duplicate-resolved records may be incorrectly rejected by destination node for being too big. Fixed in version 4.6.0.9.
      • [AER-6152] - (KVS) With auto-pin numa, namespaces with index-type pmem will assert at startup. Fixed in version 4.6.0.8.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.6.0.8.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.6.0.8.

    Improvements

    • Enterprise Only
      • [AER-6099] - (SECURITY) Allow security module to exchange SMD in a cluster where security is not enabled on all nodes.

    Bug Fixes

    • Enterprise & Community
      • [AER-6097] - (CDT) Improved msgpack comparison and sizing methods to reduce CPU usage.
    • Enterprise Only
      • [AER-6104] - (KVS) For index-type flash, index allocation errors may cause crash.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart.

  • 4.6.0.2
    Release Date: August 9, 2019
    • In server release 4.6.0.2, we have noticed that certain CDT use cases consume more CPU than in previous releases. This has been fixed in 4.6.0.4.

    • A digitally signed feature key file is now required. (Enterprise Only)

      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • 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.
    • For Aerospike Server versions prior to 4.7 XDR does not support LDAP logins.
    • We have added support for Debian 10.
    • We have deprecated support for Debian 7.
    • New API for nested CDT operations.
    • New API for bitwise operations on BLOB particles.
    • When upgrading the Aerospike Server, from a version prior to 4.6, with the security feature enabled, make sure all Aerospike Clients are running a compatible version. (Enterprise Only)
    • 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
      • 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-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.7.0.26.
      • [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.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert. Fixed in version 4.7.0.21.
      • [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.7.0.21.
      • [AER-6159] - (INFO) The thread-traces info command can cause a deadlock. Fixed in version 4.7.0.6.
      • [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.6.0.21.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.6.0.17.
      • [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. Fixed in version 4.6.0.15.
      • [AER-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.6.0.14.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.6.0.14.
      • [AER-6194] - (GEO) For namespaces with data-in-memory true, GeoJSON particles allocate up to 2KB more than the reported particle size. Fixed in version 4.6.0.14.
      • [AER-6189] - (UDF) List creation via UDF does not initialize list flags, which may inadvertently flag the list as ordered. Fixed in version 4.6.0.13.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [AER-6179] - (KVS) When upgrading from version earlier than 4.5.1, pre-existing eviction depth is not used during startup. Fixed in version 4.6.0.12.
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure. Fixed in version 4.6.0.9.
      • [AER-6165] - (CDT) by_value_list and by_key_list OPs do not accept non-storage tokens such as WILDCARD. Fixed in version 4.6.0.9.
      • [AER-6146] - (KVS) With debug-allocations enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.6.0.8.
      • [AER-6140] - (CDT) Map context unwind causes crash for namespaces with data-in-memory true when original map had incomplete order index. Fixed in version 4.6.0.6.
      • [AER-6132] - (CDT) Get or remove by key for map with element count 1 and result type index or rank returns a list instead of a scalar. Fixed in version 4.6.0.6.
      • [AER-6128] - (BALANCE) For AP namespaces with prefer-uniform-balance true, non-optimal masters may be selected. Fixed in version 4.6.0.5.
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.6.0.5.
      • [AER-6097] - (CDT) Improved msgpack comparison and sizing methods to reduce CPU usage. Fixed in version 4.6.0.4.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [AER-6143] - (BALANCE) For strong-consistency namespaces, if quiescing nodes with non-roster nodes in the cluster, the wrong nodes may quiesce. Fixed in version 4.7.0.3.
      • [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.6.0.21.
      • [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.6.0.16.
      • [AER-6214] - (SECURITY) Specifying a whitelist with a maximum set of (32) networks causes a stack memory stomp. Fixed in version 4.6.0.15.
      • [AER-6195] - (MIGRATION) Theoretical race condition may cause delta migration to complete without sending all records. Fixed in version 4.6.0.14.
      • [AER-6178] - (STORAGE) Setting storage context configuration item compression dynamically for storage-engine memory namespaces is not prevented and may cause a crash. Fixed in version 4.6.0.13.
      • [AER-6172] - (XDR) Increasing datacenter context configuration item dc-connections dynamically may cause crash. Fixed in version 4.6.0.12.
      • [AER-6170] - (XDR) Source node may crash when adding or removing namespaces in a destination cluster. Fixed in version 4.6.0.12.
      • [AER-6175] - (BALANCE) For strong-consistency namespaces, appeal subsystem leaks memory, and has rare races which may cause crash or deadlock. Fixed in version 4.6.0.11.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item report-authentication true. Fixed in version 4.6.0.10.
      • [AER-6163] - (STORAGE) When using compression, migrated, replicated, or duplicate-resolved records may be incorrectly rejected by destination node for being too big. Fixed in version 4.6.0.9.
      • [AER-6152] - (KVS) With auto-pin numa, namespaces with index-type pmem will assert at startup. Fixed in version 4.6.0.8.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.6.0.8.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.6.0.8.
      • [AER-6104] - (KVS) For index-type flash, index allocation errors may cause crash. Fixed in version 4.6.0.4.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart. Fixed in version 4.6.0.4.

    New Features

    • Enterprise & Community
      • [AER-6074] - (KVS) Added bitwise BLOB operations.
      • [AER-6092] - (CDT) Added APIs to operate on lists and maps nested within lists and maps.
    • Enterprise Only
      • [AER-6079] - (DEPLOYMENT) Enterprise Edition now requires a feature key.
      • [AER-6065] - (SECURITY) Added predefined 'write' (write only) permission for use in defining custom roles.
      • [AER-6066] - (SECURITY) Added support for specifying network whitelists on custom roles.

    Improvements

    • Enterprise & Community
      • [AER-6062] - (KVS) Added namespace context configuration item truncate-threads to specify the number of threads used by truncations.
      • [AER-6091] - (KVS) Added service context configuration item indent-allocations to enhance double-free detection when debugging the heap.
      • [AER-6061] - (DEPLOYMENT) Increased grace period to 10 minutes before clean shutdowns are aborted, and enhanced logging during shutdown.
      • [AER-6078] - (BALANCE) Working masters (also) report ownership of appropriate replicas in client partition map (e.g. to optimize rack-aware client reads in certain situations).
      • [AER-6085] - (STORAGE) Re-use freed write blocks in the order they were freed (e.g. will allow tomb raider to clear tombstones more effectively).
      • [AER-6058] - (LOGGING) Made improvements to secondary index ('sindex' context) log messages.
      • [AER-6070] - (LOGGING) Added thread count to log message at start of nsup expire and evict cycles.
    • Enterprise Only
      • [AER-6081] - (KVS) For index-type flash and index-type pmem, warn at startup if index devices are not mounted.
      • [AER-6084] - (INFO) Report true default values for storage context configuration item compression-level (if compression zstd is used) and TLS context configuration item protocols.
      • [AER-6080] - (SECURITY) Do not allow logins by external (LDAP) users who have an internal password.

    Bug Fixes

    • Enterprise & Community
      • [AER-6093] - (CDT) Get or remove by rank map operation with return type key or value returning nil element will access uninitialized memory.
      • [AER-6094] - (CDT) Get or remove by key-list ordered map operation with return type index, where key-list elements are not in map returns incomplete response.

    Updates

  • 4.5.3.22
    Release Date: July 7, 2020
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • 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. Fixed in version 4.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [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.7.0.21.
      • [AER-6159] - (INFO) The thread-traces info command can cause a deadlock. Fixed in version 4.7.0.6.
      • [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.6.0.21.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [AER-6143] - (BALANCE) For strong-consistency namespaces, if quiescing nodes with non-roster nodes in the cluster, the wrong nodes may quiesce. Fixed in version 4.7.0.3.
      • [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.6.0.21.

    Bug Fixes

    • Enterprise Only
      • [AER-6250] - (UDF) Race between a background UDF scan/query internal transaction and a durable delete may cause a deadlock.

  • 4.5.3.21
    Release Date: June 18, 2020
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • 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. Fixed in version 4.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [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.7.0.21.
      • [AER-6159] - (INFO) The thread-traces info command can cause a deadlock. Fixed in version 4.7.0.6.
      • [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.6.0.21.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [AER-6143] - (BALANCE) For strong-consistency namespaces, if quiescing nodes with non-roster nodes in the cluster, the wrong nodes may quiesce. Fixed in version 4.7.0.3.
      • [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.6.0.21.

    Improvements

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

  • 4.5.3.19
    Release Date: May 22, 2020
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • 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. Fixed in version 4.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [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.7.0.21.
      • [AER-6159] - (INFO) The thread-traces info command can cause a deadlock. Fixed in version 4.7.0.6.
      • [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.6.0.21.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [AER-6143] - (BALANCE) For strong-consistency namespaces, if quiescing nodes with non-roster nodes in the cluster, the wrong nodes may quiesce. Fixed in version 4.7.0.3.
      • [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.6.0.21.

    Bug Fixes

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

  • 4.5.3.18
    Release Date: May 15, 2020
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • 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. Fixed in version 4.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [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.7.0.21.
      • [AER-6159] - (INFO) The thread-traces info command can cause a deadlock. Fixed in version 4.7.0.6.
      • [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.6.0.21.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.5.3.19.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [AER-6143] - (BALANCE) For strong-consistency namespaces, if quiescing nodes with non-roster nodes in the cluster, the wrong nodes may quiesce. Fixed in version 4.7.0.3.
      • [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.6.0.21.

    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.5.3.17
    Release Date: April 17, 2020
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • 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. Fixed in version 4.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [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.7.0.21.
      • [AER-6159] - (INFO) The thread-traces info command can cause a deadlock. Fixed in version 4.7.0.6.
      • [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.6.0.21.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.5.3.19.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [AER-6143] - (BALANCE) For strong-consistency namespaces, if quiescing nodes with non-roster nodes in the cluster, the wrong nodes may quiesce. Fixed in version 4.7.0.3.
      • [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.6.0.21.
      • [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.5.3.18.

    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.

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

    Known Issues

    • 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. Fixed in version 4.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [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.7.0.21.
      • [AER-6159] - (INFO) The thread-traces info command can cause a deadlock. Fixed in version 4.7.0.6.
      • [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.6.0.21.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.5.3.19.
      • [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. Fixed in version 4.5.3.17.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [AER-6143] - (BALANCE) For strong-consistency namespaces, if quiescing nodes with non-roster nodes in the cluster, the wrong nodes may quiesce. Fixed in version 4.7.0.3.
      • [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.6.0.21.
      • [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.5.3.18.

    Bug Fixes

    • Enterprise & Community
      • [AER-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive.
      • [AER-6194] - (GEO) For namespaces with data-in-memory true, GeoJSON particles allocate up to 2KB more than the reported particle size.
    • Enterprise Only
      • [AER-6195] - (MIGRATION) Theoretical race condition may cause delta migration to complete without sending all records.

  • 4.5.3.15
    Release Date: February 28, 2020
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • 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. Fixed in version 4.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [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.7.0.21.
      • [AER-6159] - (INFO) The thread-traces info command can cause a deadlock. Fixed in version 4.7.0.6.
      • [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.6.0.21.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.5.3.19.
      • [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. Fixed in version 4.5.3.17.
      • [AER-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.3.16.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.3.16.
      • [AER-6194] - (GEO) For namespaces with data-in-memory true, GeoJSON particles allocate up to 2KB more than the reported particle size. Fixed in version 4.5.3.16.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [AER-6143] - (BALANCE) For strong-consistency namespaces, if quiescing nodes with non-roster nodes in the cluster, the wrong nodes may quiesce. Fixed in version 4.7.0.3.
      • [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.6.0.21.
      • [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.5.3.18.
      • [AER-6195] - (MIGRATION) Theoretical race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.3.16.

    Bug Fixes

    • Enterprise & Community
      • [AER-6189] - (UDF) List creation via UDF does not initialize list flags, which may inadvertently flag the list as ordered.
    • Enterprise Only
      • [AER-6178] - (STORAGE) Setting storage context configuration item compression dynamically for storage-engine memory namespaces is not prevented and may cause a crash.

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

    Known Issues

    • 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. Fixed in version 4.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [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.7.0.21.
      • [AER-6159] - (INFO) The thread-traces info command can cause a deadlock. Fixed in version 4.7.0.6.
      • [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.6.0.21.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.5.3.19.
      • [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. Fixed in version 4.5.3.17.
      • [AER-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.3.16.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.3.16.
      • [AER-6194] - (GEO) For namespaces with data-in-memory true, GeoJSON particles allocate up to 2KB more than the reported particle size. Fixed in version 4.5.3.16.
      • [AER-6189] - (UDF) List creation via UDF does not initialize list flags, which may inadvertently flag the list as ordered. Fixed in version 4.5.3.15.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [AER-6143] - (BALANCE) For strong-consistency namespaces, if quiescing nodes with non-roster nodes in the cluster, the wrong nodes may quiesce. Fixed in version 4.7.0.3.
      • [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.6.0.21.
      • [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.5.3.18.
      • [AER-6195] - (MIGRATION) Theoretical race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.3.16.
      • [AER-6178] - (STORAGE) Setting storage context configuration item compression dynamically for storage-engine memory namespaces is not prevented and may cause a crash. Fixed in version 4.5.3.15.

    Bug Fixes

    • Enterprise & Community
      • [AER-6179] - (KVS) When upgrading from version earlier than 4.5.1, pre-existing eviction depth is not used during startup.
    • Enterprise Only
      • [AER-6170] - (XDR) Source node may crash when adding or removing namespaces in a destination cluster.
      • [AER-6172] - (XDR) Increasing datacenter context configuration item dc-connections dynamically may cause crash.

  • 4.5.3.13
    Release Date: January 15, 2020
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • 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. Fixed in version 4.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [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.7.0.21.
      • [AER-6159] - (INFO) The thread-traces info command can cause a deadlock. Fixed in version 4.7.0.6.
      • [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.6.0.21.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.5.3.19.
      • [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. Fixed in version 4.5.3.17.
      • [AER-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.3.16.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.3.16.
      • [AER-6194] - (GEO) For namespaces with data-in-memory true, GeoJSON particles allocate up to 2KB more than the reported particle size. Fixed in version 4.5.3.16.
      • [AER-6189] - (UDF) List creation via UDF does not initialize list flags, which may inadvertently flag the list as ordered. Fixed in version 4.5.3.15.
      • [AER-6179] - (KVS) When upgrading from version earlier than 4.5.1, pre-existing eviction depth is not used during startup. Fixed in version 4.5.3.14.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [AER-6143] - (BALANCE) For strong-consistency namespaces, if quiescing nodes with non-roster nodes in the cluster, the wrong nodes may quiesce. Fixed in version 4.7.0.3.
      • [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.6.0.21.
      • [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.5.3.18.
      • [AER-6195] - (MIGRATION) Theoretical race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.3.16.
      • [AER-6178] - (STORAGE) Setting storage context configuration item compression dynamically for storage-engine memory namespaces is not prevented and may cause a crash. Fixed in version 4.5.3.15.
      • [AER-6172] - (XDR) Increasing datacenter context configuration item dc-connections dynamically may cause crash. Fixed in version 4.5.3.14.
      • [AER-6170] - (XDR) Source node may crash when adding or removing namespaces in a destination cluster. Fixed in version 4.5.3.14.

    Bug Fixes

    • Enterprise Only
      • [AER-6175] - (BALANCE) For strong-consistency namespaces, appeal subsystem leaks memory, and has rare races which may cause crash or deadlock.

  • 4.5.3.12
    Release Date: December 16, 2019
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • 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. Fixed in version 4.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [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.7.0.21.
      • [AER-6159] - (INFO) The thread-traces info command can cause a deadlock. Fixed in version 4.7.0.6.
      • [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.6.0.21.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.5.3.19.
      • [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. Fixed in version 4.5.3.17.
      • [AER-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.3.16.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.3.16.
      • [AER-6194] - (GEO) For namespaces with data-in-memory true, GeoJSON particles allocate up to 2KB more than the reported particle size. Fixed in version 4.5.3.16.
      • [AER-6189] - (UDF) List creation via UDF does not initialize list flags, which may inadvertently flag the list as ordered. Fixed in version 4.5.3.15.
      • [AER-6179] - (KVS) When upgrading from version earlier than 4.5.1, pre-existing eviction depth is not used during startup. Fixed in version 4.5.3.14.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [AER-6143] - (BALANCE) For strong-consistency namespaces, if quiescing nodes with non-roster nodes in the cluster, the wrong nodes may quiesce. Fixed in version 4.7.0.3.
      • [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.6.0.21.
      • [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.5.3.18.
      • [AER-6195] - (MIGRATION) Theoretical race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.3.16.
      • [AER-6178] - (STORAGE) Setting storage context configuration item compression dynamically for storage-engine memory namespaces is not prevented and may cause a crash. Fixed in version 4.5.3.15.
      • [AER-6172] - (XDR) Increasing datacenter context configuration item dc-connections dynamically may cause crash. Fixed in version 4.5.3.14.
      • [AER-6170] - (XDR) Source node may crash when adding or removing namespaces in a destination cluster. Fixed in version 4.5.3.14.
      • [AER-6175] - (BALANCE) For strong-consistency namespaces, appeal subsystem leaks memory, and has rare races which may cause crash or deadlock. Fixed in version 4.5.3.13.

    Bug Fixes

    • Enterprise Only
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item report-authentication true.

  • 4.5.3.11
    Release Date: December 6, 2019
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • 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. Fixed in version 4.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [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.7.0.21.
      • [AER-6159] - (INFO) The thread-traces info command can cause a deadlock. Fixed in version 4.7.0.6.
      • [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.6.0.21.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.5.3.19.
      • [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. Fixed in version 4.5.3.17.
      • [AER-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.3.16.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.3.16.
      • [AER-6194] - (GEO) For namespaces with data-in-memory true, GeoJSON particles allocate up to 2KB more than the reported particle size. Fixed in version 4.5.3.16.
      • [AER-6189] - (UDF) List creation via UDF does not initialize list flags, which may inadvertently flag the list as ordered. Fixed in version 4.5.3.15.
      • [AER-6179] - (KVS) When upgrading from version earlier than 4.5.1, pre-existing eviction depth is not used during startup. Fixed in version 4.5.3.14.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [AER-6143] - (BALANCE) For strong-consistency namespaces, if quiescing nodes with non-roster nodes in the cluster, the wrong nodes may quiesce. Fixed in version 4.7.0.3.
      • [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.6.0.21.
      • [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.5.3.18.
      • [AER-6195] - (MIGRATION) Theoretical race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.3.16.
      • [AER-6178] - (STORAGE) Setting storage context configuration item compression dynamically for storage-engine memory namespaces is not prevented and may cause a crash. Fixed in version 4.5.3.15.
      • [AER-6172] - (XDR) Increasing datacenter context configuration item dc-connections dynamically may cause crash. Fixed in version 4.5.3.14.
      • [AER-6170] - (XDR) Source node may crash when adding or removing namespaces in a destination cluster. Fixed in version 4.5.3.14.
      • [AER-6175] - (BALANCE) For strong-consistency namespaces, appeal subsystem leaks memory, and has rare races which may cause crash or deadlock. Fixed in version 4.5.3.13.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item report-authentication true. Fixed in version 4.5.3.12.

    Bug Fixes

    • Enterprise & Community
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure.
    • Enterprise Only
      • [AER-6163] - (STORAGE) When using compression, migrated, replicated, or duplicate-resolved records may be incorrectly rejected by destination node for being too big.

  • 4.5.3.10
    Release Date: November 14, 2019
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • 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. Fixed in version 4.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [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.7.0.21.
      • [AER-6159] - (INFO) The thread-traces info command can cause a deadlock. Fixed in version 4.7.0.6.
      • [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.6.0.21.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.5.3.19.
      • [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. Fixed in version 4.5.3.17.
      • [AER-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.3.16.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.3.16.
      • [AER-6194] - (GEO) For namespaces with data-in-memory true, GeoJSON particles allocate up to 2KB more than the reported particle size. Fixed in version 4.5.3.16.
      • [AER-6189] - (UDF) List creation via UDF does not initialize list flags, which may inadvertently flag the list as ordered. Fixed in version 4.5.3.15.
      • [AER-6179] - (KVS) When upgrading from version earlier than 4.5.1, pre-existing eviction depth is not used during startup. Fixed in version 4.5.3.14.
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure. Fixed in version 4.5.3.11.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [AER-6143] - (BALANCE) For strong-consistency namespaces, if quiescing nodes with non-roster nodes in the cluster, the wrong nodes may quiesce. Fixed in version 4.7.0.3.
      • [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.6.0.21.
      • [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.5.3.18.
      • [AER-6195] - (MIGRATION) Theoretical race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.3.16.
      • [AER-6178] - (STORAGE) Setting storage context configuration item compression dynamically for storage-engine memory namespaces is not prevented and may cause a crash. Fixed in version 4.5.3.15.
      • [AER-6172] - (XDR) Increasing datacenter context configuration item dc-connections dynamically may cause crash. Fixed in version 4.5.3.14.
      • [AER-6170] - (XDR) Source node may crash when adding or removing namespaces in a destination cluster. Fixed in version 4.5.3.14.
      • [AER-6175] - (BALANCE) For strong-consistency namespaces, appeal subsystem leaks memory, and has rare races which may cause crash or deadlock. Fixed in version 4.5.3.13.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item report-authentication true. Fixed in version 4.5.3.12.
      • [AER-6163] - (STORAGE) When using compression, migrated, replicated, or duplicate-resolved records may be incorrectly rejected by destination node for being too big. Fixed in version 4.5.3.11.

    Bug Fixes

    • Enterprise & Community
      • [AER-6146] - (KVS) With debug-allocations enabled, a memory accounting array will eventually overflow and cause a crash.
    • Enterprise Only
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections.

  • 4.5.3.8
    Release Date: November 1, 2019
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • 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. Fixed in version 4.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [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.7.0.21.
      • [AER-6159] - (INFO) The thread-traces info command can cause a deadlock. Fixed in version 4.7.0.6.
      • [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.6.0.21.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.5.3.19.
      • [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. Fixed in version 4.5.3.17.
      • [AER-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.3.16.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.3.16.
      • [AER-6194] - (GEO) For namespaces with data-in-memory true, GeoJSON particles allocate up to 2KB more than the reported particle size. Fixed in version 4.5.3.16.
      • [AER-6189] - (UDF) List creation via UDF does not initialize list flags, which may inadvertently flag the list as ordered. Fixed in version 4.5.3.15.
      • [AER-6179] - (KVS) When upgrading from version earlier than 4.5.1, pre-existing eviction depth is not used during startup. Fixed in version 4.5.3.14.
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure. Fixed in version 4.5.3.11.
      • [AER-6146] - (KVS) With debug-allocations enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.3.10.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [AER-6143] - (BALANCE) For strong-consistency namespaces, if quiescing nodes with non-roster nodes in the cluster, the wrong nodes may quiesce. Fixed in version 4.7.0.3.
      • [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.6.0.21.
      • [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.5.3.18.
      • [AER-6195] - (MIGRATION) Theoretical race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.3.16.
      • [AER-6178] - (STORAGE) Setting storage context configuration item compression dynamically for storage-engine memory namespaces is not prevented and may cause a crash. Fixed in version 4.5.3.15.
      • [AER-6172] - (XDR) Increasing datacenter context configuration item dc-connections dynamically may cause crash. Fixed in version 4.5.3.14.
      • [AER-6170] - (XDR) Source node may crash when adding or removing namespaces in a destination cluster. Fixed in version 4.5.3.14.
      • [AER-6175] - (BALANCE) For strong-consistency namespaces, appeal subsystem leaks memory, and has rare races which may cause crash or deadlock. Fixed in version 4.5.3.13.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item report-authentication true. Fixed in version 4.5.3.12.
      • [AER-6163] - (STORAGE) When using compression, migrated, replicated, or duplicate-resolved records may be incorrectly rejected by destination node for being too big. Fixed in version 4.5.3.11.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.5.3.10.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.3.10.

    Bug Fixes

    • Enterprise & Community
      • [AER-6132] - (CDT) Get or remove by key for map with element count 1 and result type index or rank returns a list instead of a scalar.

  • 4.5.3.7
    Release Date: October 3, 2019
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • 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. Fixed in version 4.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [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.7.0.21.
      • [AER-6159] - (INFO) The thread-traces info command can cause a deadlock. Fixed in version 4.7.0.6.
      • [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.6.0.21.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.5.3.19.
      • [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. Fixed in version 4.5.3.17.
      • [AER-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.3.16.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.3.16.
      • [AER-6194] - (GEO) For namespaces with data-in-memory true, GeoJSON particles allocate up to 2KB more than the reported particle size. Fixed in version 4.5.3.16.
      • [AER-6189] - (UDF) List creation via UDF does not initialize list flags, which may inadvertently flag the list as ordered. Fixed in version 4.5.3.15.
      • [AER-6179] - (KVS) When upgrading from version earlier than 4.5.1, pre-existing eviction depth is not used during startup. Fixed in version 4.5.3.14.
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure. Fixed in version 4.5.3.11.
      • [AER-6146] - (KVS) With debug-allocations enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.3.10.
      • [AER-6132] - (CDT) Get or remove by key for map with element count 1 and result type index or rank returns a list instead of a scalar. Fixed in version 4.5.3.8.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [AER-6143] - (BALANCE) For strong-consistency namespaces, if quiescing nodes with non-roster nodes in the cluster, the wrong nodes may quiesce. Fixed in version 4.7.0.3.
      • [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.6.0.21.
      • [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.5.3.18.
      • [AER-6195] - (MIGRATION) Theoretical race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.3.16.
      • [AER-6178] - (STORAGE) Setting storage context configuration item compression dynamically for storage-engine memory namespaces is not prevented and may cause a crash. Fixed in version 4.5.3.15.
      • [AER-6172] - (XDR) Increasing datacenter context configuration item dc-connections dynamically may cause crash. Fixed in version 4.5.3.14.
      • [AER-6170] - (XDR) Source node may crash when adding or removing namespaces in a destination cluster. Fixed in version 4.5.3.14.
      • [AER-6175] - (BALANCE) For strong-consistency namespaces, appeal subsystem leaks memory, and has rare races which may cause crash or deadlock. Fixed in version 4.5.3.13.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item report-authentication true. Fixed in version 4.5.3.12.
      • [AER-6163] - (STORAGE) When using compression, migrated, replicated, or duplicate-resolved records may be incorrectly rejected by destination node for being too big. Fixed in version 4.5.3.11.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.5.3.10.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.3.10.

    Bug Fixes

    • Enterprise & Community
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate.
      • [AER-6128] - (BALANCE) For AP namespaces with prefer-uniform-balance true, non-optimal masters may be selected.

  • 4.5.3.6
    Release Date: August 28, 2019
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • 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. Fixed in version 4.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [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.7.0.21.
      • [AER-6159] - (INFO) The thread-traces info command can cause a deadlock. Fixed in version 4.7.0.6.
      • [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.6.0.21.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.5.3.19.
      • [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. Fixed in version 4.5.3.17.
      • [AER-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.3.16.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.3.16.
      • [AER-6194] - (GEO) For namespaces with data-in-memory true, GeoJSON particles allocate up to 2KB more than the reported particle size. Fixed in version 4.5.3.16.
      • [AER-6189] - (UDF) List creation via UDF does not initialize list flags, which may inadvertently flag the list as ordered. Fixed in version 4.5.3.15.
      • [AER-6179] - (KVS) When upgrading from version earlier than 4.5.1, pre-existing eviction depth is not used during startup. Fixed in version 4.5.3.14.
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure. Fixed in version 4.5.3.11.
      • [AER-6146] - (KVS) With debug-allocations enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.3.10.
      • [AER-6132] - (CDT) Get or remove by key for map with element count 1 and result type index or rank returns a list instead of a scalar. Fixed in version 4.5.3.8.
      • [AER-6128] - (BALANCE) For AP namespaces with prefer-uniform-balance true, non-optimal masters may be selected. Fixed in version 4.5.3.7.
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.3.7.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [AER-6143] - (BALANCE) For strong-consistency namespaces, if quiescing nodes with non-roster nodes in the cluster, the wrong nodes may quiesce. Fixed in version 4.7.0.3.
      • [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.6.0.21.
      • [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.5.3.18.
      • [AER-6195] - (MIGRATION) Theoretical race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.3.16.
      • [AER-6178] - (STORAGE) Setting storage context configuration item compression dynamically for storage-engine memory namespaces is not prevented and may cause a crash. Fixed in version 4.5.3.15.
      • [AER-6172] - (XDR) Increasing datacenter context configuration item dc-connections dynamically may cause crash. Fixed in version 4.5.3.14.
      • [AER-6170] - (XDR) Source node may crash when adding or removing namespaces in a destination cluster. Fixed in version 4.5.3.14.
      • [AER-6175] - (BALANCE) For strong-consistency namespaces, appeal subsystem leaks memory, and has rare races which may cause crash or deadlock. Fixed in version 4.5.3.13.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item report-authentication true. Fixed in version 4.5.3.12.
      • [AER-6163] - (STORAGE) When using compression, migrated, replicated, or duplicate-resolved records may be incorrectly rejected by destination node for being too big. Fixed in version 4.5.3.11.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.5.3.10.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.3.10.

    Improvements

    • Enterprise Only
      • [AER-6099] - (SECURITY) Allow security module to exchange SMD in a cluster where security is not enabled on all nodes.

    Bug Fixes

    • Enterprise & Community
      • [AER-6093] - (CDT) Get or remove by rank map operation with return type key or value returning nil element will access uninitialized memory.
      • [AER-6094] - (CDT) Get or remove by key-list ordered map operation with return type index, where key-list elements are not in map returns incomplete response.
    • Enterprise Only
      • [AER-6104] - (KVS) For index-type flash, index allocation errors may cause crash.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart.

  • 4.5.3.5
    Release Date: July 31, 2019
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • 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. Fixed in version 4.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [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.7.0.21.
      • [AER-6159] - (INFO) The thread-traces info command can cause a deadlock. Fixed in version 4.7.0.6.
      • [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.6.0.21.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.5.3.19.
      • [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. Fixed in version 4.5.3.17.
      • [AER-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.3.16.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.3.16.
      • [AER-6194] - (GEO) For namespaces with data-in-memory true, GeoJSON particles allocate up to 2KB more than the reported particle size. Fixed in version 4.5.3.16.
      • [AER-6189] - (UDF) List creation via UDF does not initialize list flags, which may inadvertently flag the list as ordered. Fixed in version 4.5.3.15.
      • [AER-6179] - (KVS) When upgrading from version earlier than 4.5.1, pre-existing eviction depth is not used during startup. Fixed in version 4.5.3.14.
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure. Fixed in version 4.5.3.11.
      • [AER-6146] - (KVS) With debug-allocations enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.3.10.
      • [AER-6132] - (CDT) Get or remove by key for map with element count 1 and result type index or rank returns a list instead of a scalar. Fixed in version 4.5.3.8.
      • [AER-6128] - (BALANCE) For AP namespaces with prefer-uniform-balance true, non-optimal masters may be selected. Fixed in version 4.5.3.7.
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.3.7.
      • [AER-6093] - (CDT) Get or remove by rank map operation with return type key or value returning nil element will access uninitialized memory. Fixed in version 4.5.3.6.
      • [AER-6094] - (CDT) Get or remove by key-list ordered map operation with return type index, where key-list elements are not in map returns incomplete response. Fixed in version 4.5.3.6.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [AER-6143] - (BALANCE) For strong-consistency namespaces, if quiescing nodes with non-roster nodes in the cluster, the wrong nodes may quiesce. Fixed in version 4.7.0.3.
      • [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.6.0.21.
      • [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.5.3.18.
      • [AER-6195] - (MIGRATION) Theoretical race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.3.16.
      • [AER-6178] - (STORAGE) Setting storage context configuration item compression dynamically for storage-engine memory namespaces is not prevented and may cause a crash. Fixed in version 4.5.3.15.
      • [AER-6172] - (XDR) Increasing datacenter context configuration item dc-connections dynamically may cause crash. Fixed in version 4.5.3.14.
      • [AER-6170] - (XDR) Source node may crash when adding or removing namespaces in a destination cluster. Fixed in version 4.5.3.14.
      • [AER-6175] - (BALANCE) For strong-consistency namespaces, appeal subsystem leaks memory, and has rare races which may cause crash or deadlock. Fixed in version 4.5.3.13.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item report-authentication true. Fixed in version 4.5.3.12.
      • [AER-6163] - (STORAGE) When using compression, migrated, replicated, or duplicate-resolved records may be incorrectly rejected by destination node for being too big. Fixed in version 4.5.3.11.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.5.3.10.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.3.10.
      • [AER-6104] - (KVS) For index-type flash, index allocation errors may cause crash. Fixed in version 4.5.3.6.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart. Fixed in version 4.5.3.6.

    Improvements

    • Enterprise Only
      • [AER-6088] - (SECURITY) Added support for LDAPS.

    Bug Fixes

    • Enterprise & Community
      • [AER-6086] - (CDT) Single result operations returning boolean are not translated correctly to integer.
      • [AER-6087] - (CDT) List operations by rank and with return type rank can crash when specifying out of range rank as input.
    • Enterprise Only
      • [AER-6090] - (SECURITY) Batch sub-transactions' digests are not logged in the report-data-op audit trail.
      • [AER-6089] - (XDR) Race condition across multiple connections in libcurl may cause crash.

  • 4.5.3.4
    Release Date: June 28, 2019
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • 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. Fixed in version 4.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [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.7.0.21.
      • [AER-6159] - (INFO) The thread-traces info command can cause a deadlock. Fixed in version 4.7.0.6.
      • [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.6.0.21.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.5.3.19.
      • [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. Fixed in version 4.5.3.17.
      • [AER-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.3.16.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.3.16.
      • [AER-6194] - (GEO) For namespaces with data-in-memory true, GeoJSON particles allocate up to 2KB more than the reported particle size. Fixed in version 4.5.3.16.
      • [AER-6189] - (UDF) List creation via UDF does not initialize list flags, which may inadvertently flag the list as ordered. Fixed in version 4.5.3.15.
      • [AER-6179] - (KVS) When upgrading from version earlier than 4.5.1, pre-existing eviction depth is not used during startup. Fixed in version 4.5.3.14.
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure. Fixed in version 4.5.3.11.
      • [AER-6146] - (KVS) With debug-allocations enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.3.10.
      • [AER-6132] - (CDT) Get or remove by key for map with element count 1 and result type index or rank returns a list instead of a scalar. Fixed in version 4.5.3.8.
      • [AER-6128] - (BALANCE) For AP namespaces with prefer-uniform-balance true, non-optimal masters may be selected. Fixed in version 4.5.3.7.
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.3.7.
      • [AER-6093] - (CDT) Get or remove by rank map operation with return type key or value returning nil element will access uninitialized memory. Fixed in version 4.5.3.6.
      • [AER-6094] - (CDT) Get or remove by key-list ordered map operation with return type index, where key-list elements are not in map returns incomplete response. Fixed in version 4.5.3.6.
      • [AER-6086] - (CDT) Single result operations returning boolean are not translated correctly to integer. Fixed in version 4.5.3.5.
      • [AER-6087] - (CDT) List operations by rank and with return type rank can crash when specifying out of range rank as input. Fixed in version 4.5.3.5.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [AER-6143] - (BALANCE) For strong-consistency namespaces, if quiescing nodes with non-roster nodes in the cluster, the wrong nodes may quiesce. Fixed in version 4.7.0.3.
      • [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.6.0.21.
      • [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.5.3.18.
      • [AER-6195] - (MIGRATION) Theoretical race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.3.16.
      • [AER-6178] - (STORAGE) Setting storage context configuration item compression dynamically for storage-engine memory namespaces is not prevented and may cause a crash. Fixed in version 4.5.3.15.
      • [AER-6172] - (XDR) Increasing datacenter context configuration item dc-connections dynamically may cause crash. Fixed in version 4.5.3.14.
      • [AER-6170] - (XDR) Source node may crash when adding or removing namespaces in a destination cluster. Fixed in version 4.5.3.14.
      • [AER-6175] - (BALANCE) For strong-consistency namespaces, appeal subsystem leaks memory, and has rare races which may cause crash or deadlock. Fixed in version 4.5.3.13.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item report-authentication true. Fixed in version 4.5.3.12.
      • [AER-6163] - (STORAGE) When using compression, migrated, replicated, or duplicate-resolved records may be incorrectly rejected by destination node for being too big. Fixed in version 4.5.3.11.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.5.3.10.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.3.10.
      • [AER-6104] - (KVS) For index-type flash, index allocation errors may cause crash. Fixed in version 4.5.3.6.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart. Fixed in version 4.5.3.6.
      • [AER-6090] - (SECURITY) Batch sub-transactions' digests are not logged in the report-data-op audit trail. Fixed in version 4.5.3.5.
      • [AER-6089] - (XDR) Race condition across multiple connections in libcurl may cause crash. Fixed in version 4.5.3.5.

    Improvements

    • Enterprise & Community
      • [AER-6073] - (KVS) Validate the set name (if sent) in read and delete messages.

    Bug Fixes

    • Enterprise & Community
      • [AER-6077] - (BATCH) For storage-engine memory namespaces, batch transactions unnecessarily return an error if record size exceeds 10MB.
    • Enterprise Only
      • [AER-6072] - (XDR) Crash using multi-handles in curl library when using change notification.
      • [AER-6075] - (XDR) Dynamically setting xdr context configuration items when configuration file has no xdr context causes crash.

  • 4.5.3.3
    Release Date: May 31, 2019
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • 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. Fixed in version 4.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [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.7.0.21.
      • [AER-6159] - (INFO) The thread-traces info command can cause a deadlock. Fixed in version 4.7.0.6.
      • [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.6.0.21.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.5.3.19.
      • [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. Fixed in version 4.5.3.17.
      • [AER-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.3.16.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.3.16.
      • [AER-6194] - (GEO) For namespaces with data-in-memory true, GeoJSON particles allocate up to 2KB more than the reported particle size. Fixed in version 4.5.3.16.
      • [AER-6189] - (UDF) List creation via UDF does not initialize list flags, which may inadvertently flag the list as ordered. Fixed in version 4.5.3.15.
      • [AER-6179] - (KVS) When upgrading from version earlier than 4.5.1, pre-existing eviction depth is not used during startup. Fixed in version 4.5.3.14.
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure. Fixed in version 4.5.3.11.
      • [AER-6146] - (KVS) With debug-allocations enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.3.10.
      • [AER-6132] - (CDT) Get or remove by key for map with element count 1 and result type index or rank returns a list instead of a scalar. Fixed in version 4.5.3.8.
      • [AER-6128] - (BALANCE) For AP namespaces with prefer-uniform-balance true, non-optimal masters may be selected. Fixed in version 4.5.3.7.
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.3.7.
      • [AER-6093] - (CDT) Get or remove by rank map operation with return type key or value returning nil element will access uninitialized memory. Fixed in version 4.5.3.6.
      • [AER-6094] - (CDT) Get or remove by key-list ordered map operation with return type index, where key-list elements are not in map returns incomplete response. Fixed in version 4.5.3.6.
      • [AER-6086] - (CDT) Single result operations returning boolean are not translated correctly to integer. Fixed in version 4.5.3.5.
      • [AER-6087] - (CDT) List operations by rank and with return type rank can crash when specifying out of range rank as input. Fixed in version 4.5.3.5.
      • [AER-6077] - (BATCH) For storage-engine memory namespaces, batch transactions unnecessarily return an error if record size exceeds 10MB. Fixed in version 4.5.3.4.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [AER-6143] - (BALANCE) For strong-consistency namespaces, if quiescing nodes with non-roster nodes in the cluster, the wrong nodes may quiesce. Fixed in version 4.7.0.3.
      • [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.6.0.21.
      • [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.5.3.18.
      • [AER-6195] - (MIGRATION) Theoretical race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.3.16.
      • [AER-6178] - (STORAGE) Setting storage context configuration item compression dynamically for storage-engine memory namespaces is not prevented and may cause a crash. Fixed in version 4.5.3.15.
      • [AER-6172] - (XDR) Increasing datacenter context configuration item dc-connections dynamically may cause crash. Fixed in version 4.5.3.14.
      • [AER-6170] - (XDR) Source node may crash when adding or removing namespaces in a destination cluster. Fixed in version 4.5.3.14.
      • [AER-6175] - (BALANCE) For strong-consistency namespaces, appeal subsystem leaks memory, and has rare races which may cause crash or deadlock. Fixed in version 4.5.3.13.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item report-authentication true. Fixed in version 4.5.3.12.
      • [AER-6163] - (STORAGE) When using compression, migrated, replicated, or duplicate-resolved records may be incorrectly rejected by destination node for being too big. Fixed in version 4.5.3.11.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.5.3.10.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.3.10.
      • [AER-6104] - (KVS) For index-type flash, index allocation errors may cause crash. Fixed in version 4.5.3.6.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart. Fixed in version 4.5.3.6.
      • [AER-6090] - (SECURITY) Batch sub-transactions' digests are not logged in the report-data-op audit trail. Fixed in version 4.5.3.5.
      • [AER-6089] - (XDR) Race condition across multiple connections in libcurl may cause crash. Fixed in version 4.5.3.5.
      • [AER-6072] - (XDR) Crash using multi-handles in curl library when using change notification. Fixed in version 4.5.3.4.
      • [AER-6075] - (XDR) Dynamically setting xdr context configuration items when configuration file has no xdr context causes crash. Fixed in version 4.5.3.4.

    Improvements

    • Enterprise & Community
      • [AER-6057] - (STORAGE) Added storage context configuration item disable-odsync to prevent setting O_DSYNC flag on storage devices.

    Bug Fixes

    • Enterprise & Community
      • [AER-6068] - (LOGGING) Concurrent SIGHUPs to roll log files may race and double close a log sink file descriptor.
    • Enterprise Only
      • [AER-6069] - (SECURITY) Minor memory leak during LDAP login process.

  • 4.5.3.2
    Release Date: May 14, 2019
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • 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. Fixed in version 4.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [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.7.0.21.
      • [AER-6159] - (INFO) The thread-traces info command can cause a deadlock. Fixed in version 4.7.0.6.
      • [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.6.0.21.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.5.3.19.
      • [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. Fixed in version 4.5.3.17.
      • [AER-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.3.16.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.3.16.
      • [AER-6194] - (GEO) For namespaces with data-in-memory true, GeoJSON particles allocate up to 2KB more than the reported particle size. Fixed in version 4.5.3.16.
      • [AER-6189] - (UDF) List creation via UDF does not initialize list flags, which may inadvertently flag the list as ordered. Fixed in version 4.5.3.15.
      • [AER-6179] - (KVS) When upgrading from version earlier than 4.5.1, pre-existing eviction depth is not used during startup. Fixed in version 4.5.3.14.
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure. Fixed in version 4.5.3.11.
      • [AER-6146] - (KVS) With debug-allocations enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.3.10.
      • [AER-6132] - (CDT) Get or remove by key for map with element count 1 and result type index or rank returns a list instead of a scalar. Fixed in version 4.5.3.8
      • [AER-6128] - (BALANCE) For AP namespaces with prefer-uniform-balance true, non-optimal masters may be selected. Fixed in version 4.5.3.7.
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.3.7.
      • [AER-6093] - (CDT) Get or remove by rank map operation with return type key or value returning nil element will access uninitialized memory. Fixed in version 4.5.3.6.
      • [AER-6094] - (CDT) Get or remove by key-list ordered map operation with return type index, where key-list elements are not in map returns incomplete response. Fixed in version 4.5.3.6.
      • [AER-6086] - (CDT) Single result operations returning boolean are not translated correctly to integer. Fixed in version 4.5.3.5.
      • [AER-6087] - (CDT) List operations by rank and with return type rank can crash when specifying out of range rank as input. Fixed in version 4.5.3.5.
      • [AER-6077] - (BATCH) For storage-engine memory namespaces, batch transactions unnecessarily return an error if record size exceeds 10MB. Fixed in version 4.5.3.4.
      • [AER-6068] - (LOGGING) Concurrent SIGHUPs to roll log files may race and double close a log sink file descriptor. Fixed in version 4.5.3.3.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [AER-6143] - (BALANCE) For strong-consistency namespaces, if quiescing nodes with non-roster nodes in the cluster, the wrong nodes may quiesce. Fixed in version 4.7.0.3.
      • [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.6.0.21.
      • [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.5.3.18.
      • [AER-6195] - (MIGRATION) Theoretical race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.3.16.
      • [AER-6178] - (STORAGE) Setting storage context configuration item compression dynamically for storage-engine memory namespaces is not prevented and may cause a crash. Fixed in version 4.5.3.15.
      • [AER-6172] - (XDR) Increasing datacenter context configuration item dc-connections dynamically may cause crash. Fixed in version 4.5.3.14.
      • [AER-6170] - (XDR) Source node may crash when adding or removing namespaces in a destination cluster. Fixed in version 4.5.3.14.
      • [AER-6175] - (BALANCE) For strong-consistency namespaces, appeal subsystem leaks memory, and has rare races which may cause crash or deadlock. Fixed in version 4.5.3.13.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item report-authentication true. Fixed in version 4.5.3.12.
      • [AER-6163] - (STORAGE) When using compression, migrated, replicated, or duplicate-resolved records may be incorrectly rejected by destination node for being too big. Fixed in version 4.5.3.11.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.5.3.10.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.3.10.
      • [AER-6104] - (KVS) For index-type flash, index allocation errors may cause crash. Fixed in version 4.5.3.6.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart. Fixed in version 4.5.3.6.
      • [AER-6090] - (SECURITY) Batch sub-transactions' digests are not logged in the report-data-op audit trail. Fixed in version 4.5.3.5.
      • [AER-6089] - (XDR) Race condition across multiple connections in libcurl may cause crash. Fixed in version 4.5.3.5.
      • [AER-6072] - (XDR) Crash using multi-handles in curl library when using change notification. Fixed in version 4.5.3.4.
      • [AER-6075] - (XDR) Dynamically setting xdr context configuration items when configuration file has no xdr context causes crash. Fixed in version 4.5.3.4.
      • [AER-6069] - (SECURITY) Minor memory leak during LDAP login process. Fixed in version 4.5.3.3.

    Improvements

    • Enterprise & Community
      • [AER-6043] - (KVS) Support aliasing and bonding plus aliases for auto-pin configuration.
      • [AER-6056] - (KVS) For increased efficiency, especially when using compression, flat storage format now also used as wire format for replication, migration, and duplicate resolution.
      • [AER-6055] - (INFO) Added info command thread-traces to show the current call stack for all server threads.
    • Enterprise Only
      • [AER-6027] - (TLS) Removed support for SSLv3.

    Bug Fixes

    • Enterprise & Community
      • [AER-6040] - (DEPLOYMENT) Aerospike will not start under systemd as non-root when using index-type value 'flash' or auto-pin value 'numa'.
      • [AER-6053] - (SCAN) Dynamically decreasing service context configuration items scan-threads or sindex-builder-threads temporarily blocks all (other) dynamic configurations.

    Updates

  • 4.5.2.18
    Release Date: May 15, 2020
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • Aerospike Tools version 3.18.1 dependencies
      • Aerospike Tools 3.18.1 now requires Python version 2.7.
      • Aerospike Tools 3.18.1 now requires Java version 1.8 or newer.

    Known Issues

    • 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. Fixed in version 4.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [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.7.0.21.
      • [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.6.0.21.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.5.3.19.
      • [AER-6128] - (BALANCE) For AP namespaces with prefer-uniform-balance true, non-optimal masters may be selected. Fixed in version 4.5.3.7.
      • [AER-6040] - (DEPLOYMENT) Aerospike will not start under systemd as non-root when using index-type value 'flash' or auto-pin value 'numa'. Fixed in version 4.5.3.2.
      • [AER-6053] - (SCAN) Dynamically decreasing service context configuration items scan-threads or sindex-builder-threads temporarily blocks all (other) dynamic configurations. Fixed in version 4.5.3.2.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [AER-6143] - (BALANCE) For strong-consistency namespaces, if quiescing nodes with non-roster nodes in the cluster, the wrong nodes may quiesce. Fixed in version 4.7.0.3.
      • [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.6.0.21.

    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.5.2.17
    Release Date: April 17, 2020
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • Aerospike Tools version 3.18.1 dependencies
      • Aerospike Tools 3.18.1 now requires Python version 2.7.
      • Aerospike Tools 3.18.1 now requires Java version 1.8 or newer.

    Known Issues

    • 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. Fixed in version 4.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [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.7.0.21.
      • [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.6.0.21.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.5.3.19.
      • [AER-6128] - (BALANCE) For AP namespaces with prefer-uniform-balance true, non-optimal masters may be selected. Fixed in version 4.5.3.7.
      • [AER-6040] - (DEPLOYMENT) Aerospike will not start under systemd as non-root when using index-type value 'flash' or auto-pin value 'numa'. Fixed in version 4.5.3.2.
      • [AER-6053] - (SCAN) Dynamically decreasing service context configuration items scan-threads or sindex-builder-threads temporarily blocks all (other) dynamic configurations. Fixed in version 4.5.3.2.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [AER-6143] - (BALANCE) For strong-consistency namespaces, if quiescing nodes with non-roster nodes in the cluster, the wrong nodes may quiesce. Fixed in version 4.7.0.3.
      • [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.6.0.21.
      • [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.5.2.18.

    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.

  • 4.5.2.16
    Release Date: March 19, 2020
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • Aerospike Tools version 3.18.1 dependencies
      • Aerospike Tools 3.18.1 now requires Python version 2.7.
      • Aerospike Tools 3.18.1 now requires Java version 1.8 or newer.

    Known Issues

    • 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. Fixed in version 4.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [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.7.0.21.
      • [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.6.0.21.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.5.3.19.
      • [AER-6128] - (BALANCE) For AP namespaces with prefer-uniform-balance true, non-optimal masters may be selected. Fixed in version 4.5.3.7.
      • [AER-6040] - (DEPLOYMENT) Aerospike will not start under systemd as non-root when using index-type value 'flash' or auto-pin value 'numa'. Fixed in version 4.5.3.2.
      • [AER-6053] - (SCAN) Dynamically decreasing service context configuration items scan-threads or sindex-builder-threads temporarily blocks all (other) dynamic configurations. Fixed in version 4.5.3.2.
      • [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. Fixed in version 4.5.2.17.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [AER-6143] - (BALANCE) For strong-consistency namespaces, if quiescing nodes with non-roster nodes in the cluster, the wrong nodes may quiesce. Fixed in version 4.7.0.3.
      • [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.6.0.21.
      • [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.5.2.18.

    Bug Fixes

    • Enterprise & Community
      • [AER-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive.
      • [AER-6194] - (GEO) For namespaces with data-in-memory true, GeoJSON particles allocate up to 2KB more than the reported particle size.
    • Enterprise Only
      • [AER-6195] - (MIGRATION) Theoretical race condition may cause delta migration to complete without sending all records.

  • 4.5.2.15
    Release Date: February 28, 2020
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • Aerospike Tools version 3.18.1 dependencies
      • Aerospike Tools 3.18.1 now requires Python version 2.7.
      • Aerospike Tools 3.18.1 now requires Java version 1.8 or newer.

    Known Issues

    • 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. Fixed in version 4.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [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.7.0.21.
      • [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.6.0.21.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.5.3.19.
      • [AER-6128] - (BALANCE) For AP namespaces with prefer-uniform-balance true, non-optimal masters may be selected. Fixed in version 4.5.3.7.
      • [AER-6040] - (DEPLOYMENT) Aerospike will not start under systemd as non-root when using index-type value 'flash' or auto-pin value 'numa'. Fixed in version 4.5.3.2.
      • [AER-6053] - (SCAN) Dynamically decreasing service context configuration items scan-threads or sindex-builder-threads temporarily blocks all (other) dynamic configurations. Fixed in version 4.5.3.2.
      • [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. Fixed in version 4.5.2.17.
      • [AER-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.2.16.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.2.16.
      • [AER-6194] - (GEO) For namespaces with data-in-memory true, GeoJSON particles allocate up to 2KB more than the reported particle size. Fixed in version 4.5.2.16.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [AER-6143] - (BALANCE) For strong-consistency namespaces, if quiescing nodes with non-roster nodes in the cluster, the wrong nodes may quiesce. Fixed in version 4.7.0.3.
      • [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.6.0.21.
      • [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.5.2.18.
      • [AER-6195] - (MIGRATION) Theoretical race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.2.16.

    Bug Fixes

    • Enterprise & Community
      • [AER-6189] - (UDF) List creation via UDF does not initialize list flags, which may inadvertently flag the list as ordered.
    • Enterprise Only
      • [AER-6178] - (STORAGE) Setting storage context configuration item compression dynamically for storage-engine memory namespaces is not prevented and may cause a crash.

  • 4.5.2.14
    Release Date: January 21, 2020
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • Aerospike Tools version 3.18.1 dependencies
      • Aerospike Tools 3.18.1 now requires Python version 2.7.
      • Aerospike Tools 3.18.1 now requires Java version 1.8 or newer.

    Known Issues

    • 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. Fixed in version 4.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [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.7.0.21.
      • [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.6.0.21.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.5.3.19.
      • [AER-6128] - (BALANCE) For AP namespaces with prefer-uniform-balance true, non-optimal masters may be selected. Fixed in version 4.5.3.7.
      • [AER-6040] - (DEPLOYMENT) Aerospike will not start under systemd as non-root when using index-type value 'flash' or auto-pin value 'numa'. Fixed in version 4.5.3.2.
      • [AER-6053] - (SCAN) Dynamically decreasing service context configuration items scan-threads or sindex-builder-threads temporarily blocks all (other) dynamic configurations. Fixed in version 4.5.3.2.
      • [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. Fixed in version 4.5.2.17.
      • [AER-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.2.16.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.2.16.
      • [AER-6194] - (GEO) For namespaces with data-in-memory true, GeoJSON particles allocate up to 2KB more than the reported particle size. Fixed in version 4.5.2.16.
      • [AER-6189] - (UDF) List creation via UDF does not initialize list flags, which may inadvertently flag the list as ordered. Fixed in version 4.5.2.15.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [AER-6143] - (BALANCE) For strong-consistency namespaces, if quiescing nodes with non-roster nodes in the cluster, the wrong nodes may quiesce. Fixed in version 4.7.0.3.
      • [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.6.0.21.
      • [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.5.2.18.
      • [AER-6195] - (MIGRATION) Theoretical race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.2.16.
      • [AER-6178] - (STORAGE) Setting storage context configuration item compression dynamically for storage-engine memory namespaces is not prevented and may cause a crash. Fixed in version 4.5.2.15.

    Bug Fixes

    • Enterprise & Community
      • [AER-6179] - (KVS) When upgrading from version earlier than 4.5.1, pre-existing eviction depth is not used during startup.

  • 4.5.2.13
    Release Date: January 15, 2020
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • Aerospike Tools version 3.18.1 dependencies
      • Aerospike Tools 3.18.1 now requires Python version 2.7.
      • Aerospike Tools 3.18.1 now requires Java version 1.8 or newer.

    Known Issues

    • 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. Fixed in version 4.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [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.7.0.21.
      • [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.6.0.21.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.5.3.19.
      • [AER-6128] - (BALANCE) For AP namespaces with prefer-uniform-balance true, non-optimal masters may be selected. Fixed in version 4.5.3.7.
      • [AER-6040] - (DEPLOYMENT) Aerospike will not start under systemd as non-root when using index-type value 'flash' or auto-pin value 'numa'. Fixed in version 4.5.3.2.
      • [AER-6053] - (SCAN) Dynamically decreasing service context configuration items scan-threads or sindex-builder-threads temporarily blocks all (other) dynamic configurations. Fixed in version 4.5.3.2.
      • [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. Fixed in version 4.5.2.17.
      • [AER-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.2.16.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.2.16.
      • [AER-6194] - (GEO) For namespaces with data-in-memory true, GeoJSON particles allocate up to 2KB more than the reported particle size. Fixed in version 4.5.2.16.
      • [AER-6189] - (UDF) List creation via UDF does not initialize list flags, which may inadvertently flag the list as ordered. Fixed in version 4.5.2.15.
      • [AER-6179] - (KVS) When upgrading from version earlier than 4.5.1, pre-existing eviction depth is not used during startup. Fixed in version 4.5.2.14.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [AER-6143] - (BALANCE) For strong-consistency namespaces, if quiescing nodes with non-roster nodes in the cluster, the wrong nodes may quiesce. Fixed in version 4.7.0.3.
      • [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.6.0.21.
      • [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.5.2.18.
      • [AER-6195] - (MIGRATION) Theoretical race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.2.16.
      • [AER-6178] - (STORAGE) Setting storage context configuration item compression dynamically for storage-engine memory namespaces is not prevented and may cause a crash. Fixed in version 4.5.2.15.

    Bug Fixes

    • Enterprise Only
      • [AER-6175] - (BALANCE) For strong-consistency namespaces, appeal subsystem leaks memory, and has rare races which may cause crash or deadlock.

  • 4.5.2.12
    Release Date: December 16, 2019
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • Aerospike Tools version 3.18.1 dependencies
      • Aerospike Tools 3.18.1 now requires Python version 2.7.
      • Aerospike Tools 3.18.1 now requires Java version 1.8 or newer.

    Known Issues

    • 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. Fixed in version 4.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [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.7.0.21.
      • [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.6.0.21.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.5.3.19.
      • [AER-6128] - (BALANCE) For AP namespaces with prefer-uniform-balance true, non-optimal masters may be selected. Fixed in version 4.5.3.7.
      • [AER-6040] - (DEPLOYMENT) Aerospike will not start under systemd as non-root when using index-type value 'flash' or auto-pin value 'numa'. Fixed in version 4.5.3.2.
      • [AER-6053] - (SCAN) Dynamically decreasing service context configuration items scan-threads or sindex-builder-threads temporarily blocks all (other) dynamic configurations. Fixed in version 4.5.3.2.
      • [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. Fixed in version 4.5.2.17.
      • [AER-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.2.16.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.2.16.
      • [AER-6194] - (GEO) For namespaces with data-in-memory true, GeoJSON particles allocate up to 2KB more than the reported particle size. Fixed in version 4.5.2.16.
      • [AER-6189] - (UDF) List creation via UDF does not initialize list flags, which may inadvertently flag the list as ordered. Fixed in version 4.5.2.15.
      • [AER-6179] - (KVS) When upgrading from version earlier than 4.5.1, pre-existing eviction depth is not used during startup. Fixed in version 4.5.2.14.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [AER-6143] - (BALANCE) For strong-consistency namespaces, if quiescing nodes with non-roster nodes in the cluster, the wrong nodes may quiesce. Fixed in version 4.7.0.3.
      • [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.6.0.21.
      • [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.5.2.18.
      • [AER-6195] - (MIGRATION) Theoretical race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.2.16.
      • [AER-6178] - (STORAGE) Setting storage context configuration item compression dynamically for storage-engine memory namespaces is not prevented and may cause a crash. Fixed in version 4.5.2.15.
      • [AER-6175] - (BALANCE) For strong-consistency namespaces, appeal subsystem leaks memory, and has rare races which may cause crash or deadlock. Fixed in version 4.5.2.13.

    Bug Fixes

    • Enterprise Only
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item report-authentication true.

  • 4.5.2.11
    Release Date: December 6, 2019
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • Aerospike Tools version 3.18.1 dependencies
      • Aerospike Tools 3.18.1 now requires Python version 2.7.
      • Aerospike Tools 3.18.1 now requires Java version 1.8 or newer.

    Known Issues

    • 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. Fixed in version 4.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [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.7.0.21.
      • [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.6.0.21.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.5.3.19.
      • [AER-6128] - (BALANCE) For AP namespaces with prefer-uniform-balance true, non-optimal masters may be selected. Fixed in version 4.5.3.7.
      • [AER-6040] - (DEPLOYMENT) Aerospike will not start under systemd as non-root when using index-type value 'flash' or auto-pin value 'numa'. Fixed in version 4.5.3.2.
      • [AER-6053] - (SCAN) Dynamically decreasing service context configuration items scan-threads or sindex-builder-threads temporarily blocks all (other) dynamic configurations. Fixed in version 4.5.3.2.
      • [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. Fixed in version 4.5.2.17.
      • [AER-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.2.16.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.2.16.
      • [AER-6194] - (GEO) For namespaces with data-in-memory true, GeoJSON particles allocate up to 2KB more than the reported particle size. Fixed in version 4.5.2.16.
      • [AER-6189] - (UDF) List creation via UDF does not initialize list flags, which may inadvertently flag the list as ordered. Fixed in version 4.5.2.15.
      • [AER-6179] - (KVS) When upgrading from version earlier than 4.5.1, pre-existing eviction depth is not used during startup. Fixed in version 4.5.2.14.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [AER-6143] - (BALANCE) For strong-consistency namespaces, if quiescing nodes with non-roster nodes in the cluster, the wrong nodes may quiesce. Fixed in version 4.7.0.3.
      • [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.6.0.21.
      • [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.5.2.18.
      • [AER-6195] - (MIGRATION) Theoretical race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.2.16.
      • [AER-6178] - (STORAGE) Setting storage context configuration item compression dynamically for storage-engine memory namespaces is not prevented and may cause a crash. Fixed in version 4.5.2.15.
      • [AER-6175] - (BALANCE) For strong-consistency namespaces, appeal subsystem leaks memory, and has rare races which may cause crash or deadlock. Fixed in version 4.5.2.13.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item report-authentication true. Fixed in version 4.5.2.12.

    Bug Fixes

    • Enterprise & Community
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure.

  • 4.5.2.10
    Release Date: November 14, 2019
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • Aerospike Tools version 3.18.1 dependencies
      • Aerospike Tools 3.18.1 now requires Python version 2.7.
      • Aerospike Tools 3.18.1 now requires Java version 1.8 or newer.

    Known Issues

    • 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. Fixed in version 4.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [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.7.0.21.
      • [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.6.0.21.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.5.3.19.
      • [AER-6128] - (BALANCE) For AP namespaces with prefer-uniform-balance true, non-optimal masters may be selected. Fixed in version 4.5.3.7.
      • [AER-6040] - (DEPLOYMENT) Aerospike will not start under systemd as non-root when using index-type value 'flash' or auto-pin value 'numa'. Fixed in version 4.5.3.2.
      • [AER-6053] - (SCAN) Dynamically decreasing service context configuration items scan-threads or sindex-builder-threads temporarily blocks all (other) dynamic configurations. Fixed in version 4.5.3.2.
      • [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. Fixed in version 4.5.2.17.
      • [AER-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.2.16.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.2.16.
      • [AER-6194] - (GEO) For namespaces with data-in-memory true, GeoJSON particles allocate up to 2KB more than the reported particle size. Fixed in version 4.5.2.16.
      • [AER-6189] - (UDF) List creation via UDF does not initialize list flags, which may inadvertently flag the list as ordered. Fixed in version 4.5.2.15.
      • [AER-6179] - (KVS) When upgrading from version earlier than 4.5.1, pre-existing eviction depth is not used during startup. Fixed in version 4.5.2.14.
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure. Fixed in version 4.5.2.11.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [AER-6143] - (BALANCE) For strong-consistency namespaces, if quiescing nodes with non-roster nodes in the cluster, the wrong nodes may quiesce. Fixed in version 4.7.0.3.
      • [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.6.0.21.
      • [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.5.2.18.
      • [AER-6195] - (MIGRATION) Theoretical race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.2.16.
      • [AER-6178] - (STORAGE) Setting storage context configuration item compression dynamically for storage-engine memory namespaces is not prevented and may cause a crash. Fixed in version 4.5.2.15.
      • [AER-6175] - (BALANCE) For strong-consistency namespaces, appeal subsystem leaks memory, and has rare races which may cause crash or deadlock. Fixed in version 4.5.2.13.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item report-authentication true. Fixed in version 4.5.2.12.

    Bug Fixes

    • Enterprise & Community
      • [AER-6146] - (KVS) With debug-allocations enabled, a memory accounting array will eventually overflow and cause a crash.
    • Enterprise Only
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections.

  • 4.5.2.8
    Release Date: November 1, 2019
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • Aerospike Tools version 3.18.1 dependencies
      • Aerospike Tools 3.18.1 now requires Python version 2.7.
      • Aerospike Tools 3.18.1 now requires Java version 1.8 or newer.

    Known Issues

    • 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. Fixed in version 4.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [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.7.0.21.
      • [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.6.0.21.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.5.3.19.
      • [AER-6128] - (BALANCE) For AP namespaces with prefer-uniform-balance true, non-optimal masters may be selected. Fixed in version 4.5.3.7.
      • [AER-6040] - (DEPLOYMENT) Aerospike will not start under systemd as non-root when using index-type value 'flash' or auto-pin value 'numa'. Fixed in version 4.5.3.2.
      • [AER-6053] - (SCAN) Dynamically decreasing service context configuration items scan-threads or sindex-builder-threads temporarily blocks all (other) dynamic configurations. Fixed in version 4.5.3.2.
      • [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. Fixed in version 4.5.2.17.
      • [AER-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.2.16.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.2.16.
      • [AER-6194] - (GEO) For namespaces with data-in-memory true, GeoJSON particles allocate up to 2KB more than the reported particle size. Fixed in version 4.5.2.16.
      • [AER-6189] - (UDF) List creation via UDF does not initialize list flags, which may inadvertently flag the list as ordered. Fixed in version 4.5.2.15.
      • [AER-6179] - (KVS) When upgrading from version earlier than 4.5.1, pre-existing eviction depth is not used during startup. Fixed in version 4.5.2.14.
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure. Fixed in version 4.5.2.11.
      • [AER-6146] - (KVS) With debug-allocations enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.2.10.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [AER-6143] - (BALANCE) For strong-consistency namespaces, if quiescing nodes with non-roster nodes in the cluster, the wrong nodes may quiesce. Fixed in version 4.7.0.3.
      • [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.6.0.21.
      • [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.5.2.18.
      • [AER-6195] - (MIGRATION) Theoretical race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.2.16.
      • [AER-6178] - (STORAGE) Setting storage context configuration item compression dynamically for storage-engine memory namespaces is not prevented and may cause a crash. Fixed in version 4.5.2.15.
      • [AER-6175] - (BALANCE) For strong-consistency namespaces, appeal subsystem leaks memory, and has rare races which may cause crash or deadlock. Fixed in version 4.5.2.13.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item report-authentication true. Fixed in version 4.5.2.12.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.5.2.10.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.2.10.

    Bug Fixes

    • Enterprise & Community
      • [AER-6132] - (CDT) Get or remove by key for map with element count 1 and result type index or rank returns a list instead of a scalar.

  • 4.5.2.7
    Release Date: October 3, 2019
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • Aerospike Tools version 3.18.1 dependencies
      • Aerospike Tools 3.18.1 now requires Python version 2.7.
      • Aerospike Tools 3.18.1 now requires Java version 1.8 or newer.

    Known Issues

    • 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. Fixed in version 4.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [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.7.0.21.
      • [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.6.0.21.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.5.3.19.
      • [AER-6128] - (BALANCE) For AP namespaces with prefer-uniform-balance true, non-optimal masters may be selected. Fixed in version 4.5.3.7.
      • [AER-6040] - (DEPLOYMENT) Aerospike will not start under systemd as non-root when using index-type value 'flash' or auto-pin value 'numa'. Fixed in version 4.5.3.2.
      • [AER-6053] - (SCAN) Dynamically decreasing service context configuration items scan-threads or sindex-builder-threads temporarily blocks all (other) dynamic configurations. Fixed in version 4.5.3.2.
      • [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. Fixed in version 4.5.2.17.
      • [AER-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.2.16.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.2.16.
      • [AER-6194] - (GEO) For namespaces with data-in-memory true, GeoJSON particles allocate up to 2KB more than the reported particle size. Fixed in version 4.5.2.16.
      • [AER-6189] - (UDF) List creation via UDF does not initialize list flags, which may inadvertently flag the list as ordered. Fixed in version 4.5.2.15.
      • [AER-6179] - (KVS) When upgrading from version earlier than 4.5.1, pre-existing eviction depth is not used during startup. Fixed in version 4.5.2.14.
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure. Fixed in version 4.5.2.11.
      • [AER-6146] - (KVS) With debug-allocations enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.2.10.
      • [AER-6132] - (CDT) Get or remove by key for map with element count 1 and result type index or rank returns a list instead of a scalar. Fixed in version 4.5.2.8.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [AER-6143] - (BALANCE) For strong-consistency namespaces, if quiescing nodes with non-roster nodes in the cluster, the wrong nodes may quiesce. Fixed in version 4.7.0.3.
      • [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.6.0.21.
      • [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.5.2.18.
      • [AER-6195] - (MIGRATION) Theoretical race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.2.16.
      • [AER-6178] - (STORAGE) Setting storage context configuration item compression dynamically for storage-engine memory namespaces is not prevented and may cause a crash. Fixed in version 4.5.2.15.
      • [AER-6175] - (BALANCE) For strong-consistency namespaces, appeal subsystem leaks memory, and has rare races which may cause crash or deadlock. Fixed in version 4.5.2.13.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item report-authentication true. Fixed in version 4.5.2.12.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.5.2.10.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.2.10.

    Bug Fixes

    • Enterprise & Community
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate.

  • 4.5.2.6
    Release Date: August 28, 2019
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • Aerospike Tools version 3.18.1 dependencies
      • Aerospike Tools 3.18.1 now requires Python version 2.7.
      • Aerospike Tools 3.18.1 now requires Java version 1.8 or newer.

    Known Issues

    • 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. Fixed in version 4.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [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.7.0.21.
      • [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.6.0.21.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.5.3.19.
      • [AER-6128] - (BALANCE) For AP namespaces with prefer-uniform-balance true, non-optimal masters may be selected. Fixed in version 4.5.3.7.
      • [AER-6040] - (DEPLOYMENT) Aerospike will not start under systemd as non-root when using index-type value 'flash' or auto-pin value 'numa'. Fixed in version 4.5.3.2.
      • [AER-6053] - (SCAN) Dynamically decreasing service context configuration items scan-threads or sindex-builder-threads temporarily blocks all (other) dynamic configurations. Fixed in version 4.5.3.2.
      • [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. Fixed in version 4.5.2.17.
      • [AER-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.2.16.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.2.16.
      • [AER-6194] - (GEO) For namespaces with data-in-memory true, GeoJSON particles allocate up to 2KB more than the reported particle size. Fixed in version 4.5.2.16.
      • [AER-6189] - (UDF) List creation via UDF does not initialize list flags, which may inadvertently flag the list as ordered. Fixed in version 4.5.2.15.
      • [AER-6179] - (KVS) When upgrading from version earlier than 4.5.1, pre-existing eviction depth is not used during startup. Fixed in version 4.5.2.14.
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure. Fixed in version 4.5.2.11.
      • [AER-6146] - (KVS) With debug-allocations enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.2.10.
      • [AER-6132] - (CDT) Get or remove by key for map with element count 1 and result type index or rank returns a list instead of a scalar. Fixed in version 4.5.2.8.
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.2.7.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [AER-6143] - (BALANCE) For strong-consistency namespaces, if quiescing nodes with non-roster nodes in the cluster, the wrong nodes may quiesce. Fixed in version 4.7.0.3.
      • [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.6.0.21.
      • [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.5.2.18.
      • [AER-6195] - (MIGRATION) Theoretical race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.2.16.
      • [AER-6178] - (STORAGE) Setting storage context configuration item compression dynamically for storage-engine memory namespaces is not prevented and may cause a crash. Fixed in version 4.5.2.15.
      • [AER-6175] - (BALANCE) For strong-consistency namespaces, appeal subsystem leaks memory, and has rare races which may cause crash or deadlock. Fixed in version 4.5.2.13.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item report-authentication true. Fixed in version 4.5.2.12.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.5.2.10.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.2.10.

    Improvements

    • Enterprise Only
      • [AER-6099] - (SECURITY) Allow security module to exchange SMD in a cluster where security is not enabled on all nodes.

    Bug Fixes

    • Enterprise & Community
      • [AER-6093] - (CDT) Get or remove by rank map operation with return type key or value returning nil element will access uninitialized memory.
      • [AER-6094] - (CDT) Get or remove by key-list ordered map operation with return type index, where key-list elements are not in map returns incomplete response.
    • Enterprise Only
      • [AER-6104] - (KVS) For index-type flash, index allocation errors may cause crash.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart.

  • 4.5.2.5
    Release Date: July 31, 2019
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • Aerospike Tools version 3.18.1 dependencies
      • Aerospike Tools 3.18.1 now requires Python version 2.7.
      • Aerospike Tools 3.18.1 now requires Java version 1.8 or newer.

    Known Issues

    • 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. Fixed in version 4.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [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.7.0.21.
      • [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.6.0.21.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.5.3.19.
      • [AER-6128] - (BALANCE) For AP namespaces with prefer-uniform-balance true, non-optimal masters may be selected. Fixed in version 4.5.3.7.
      • [AER-6040] - (DEPLOYMENT) Aerospike will not start under systemd as non-root when using index-type value 'flash' or auto-pin value 'numa'. Fixed in version 4.5.3.2.
      • [AER-6053] - (SCAN) Dynamically decreasing service context configuration items scan-threads or sindex-builder-threads temporarily blocks all (other) dynamic configurations. Fixed in version 4.5.3.2.
      • [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. Fixed in version 4.5.2.17.
      • [AER-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.2.16.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.2.16.
      • [AER-6194] - (GEO) For namespaces with data-in-memory true, GeoJSON particles allocate up to 2KB more than the reported particle size. Fixed in version 4.5.2.16.
      • [AER-6189] - (UDF) List creation via UDF does not initialize list flags, which may inadvertently flag the list as ordered. Fixed in version 4.5.2.15.
      • [AER-6179] - (KVS) When upgrading from version earlier than 4.5.1, pre-existing eviction depth is not used during startup. Fixed in version 4.5.2.14.
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure. Fixed in version 4.5.2.11.
      • [AER-6146] - (KVS) With debug-allocations enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.2.10.
      • [AER-6132] - (CDT) Get or remove by key for map with element count 1 and result type index or rank returns a list instead of a scalar. Fixed in version 4.5.2.8.
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.2.7.
      • [AER-6093] - (CDT) Get or remove by rank map operation with return type key or value returning nil element will access uninitialized memory. Fixed in version 4.5.2.6.
      • [AER-6094] - (CDT) Get or remove by key-list ordered map operation with return type index, where key-list elements are not in map returns incomplete response. Fixed in version 4.5.2.6.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [AER-6143] - (BALANCE) For strong-consistency namespaces, if quiescing nodes with non-roster nodes in the cluster, the wrong nodes may quiesce. Fixed in version 4.7.0.3.
      • [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.6.0.21.
      • [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.5.2.18.
      • [AER-6195] - (MIGRATION) Theoretical race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.2.16.
      • [AER-6178] - (STORAGE) Setting storage context configuration item compression dynamically for storage-engine memory namespaces is not prevented and may cause a crash. Fixed in version 4.5.2.15.
      • [AER-6175] - (BALANCE) For strong-consistency namespaces, appeal subsystem leaks memory, and has rare races which may cause crash or deadlock. Fixed in version 4.5.2.13.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item report-authentication true. Fixed in version 4.5.2.12.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.5.2.10.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.2.10.
      • [AER-6104] - (KVS) For index-type flash, index allocation errors may cause crash. Fixed in version 4.5.2.6.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart. Fixed in version 4.5.2.6.

    Improvements

    • Enterprise Only
      • [AER-6088] - (SECURITY) Added support for LDAPS.

    Bug Fixes

    • Enterprise & Community
      • [AER-6086] - (CDT) Single result operations returning boolean are not translated correctly to integer.
      • [AER-6087] - (CDT) List operations by rank and with return type rank can crash when specifying out of range rank as input.
    • Enterprise Only
      • [AER-6090] - (SECURITY) Batch sub-transactions' digests are not logged in the report-data-op audit trail.
      • [AER-6089] - (XDR) Race condition across multiple connections in libcurl may cause crash.

  • 4.5.2.4
    Release Date: June 28, 2019
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • Aerospike Tools version 3.18.1 dependencies
      • Aerospike Tools 3.18.1 now requires Python version 2.7.
      • Aerospike Tools 3.18.1 now requires Java version 1.8 or newer.

    Known Issues

    • 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. Fixed in version 4.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [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.7.0.21.
      • [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.6.0.21.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.5.3.19.
      • [AER-6128] - (BALANCE) For AP namespaces with prefer-uniform-balance true, non-optimal masters may be selected. Fixed in version 4.5.3.7.
      • [AER-6040] - (DEPLOYMENT) Aerospike will not start under systemd as non-root when using index-type value 'flash' or auto-pin value 'numa'. Fixed in version 4.5.3.2.
      • [AER-6053] - (SCAN) Dynamically decreasing service context configuration items scan-threads or sindex-builder-threads temporarily blocks all (other) dynamic configurations. Fixed in version 4.5.3.2.
      • [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. Fixed in version 4.5.2.17.
      • [AER-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.2.16.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.2.16.
      • [AER-6194] - (GEO) For namespaces with data-in-memory true, GeoJSON particles allocate up to 2KB more than the reported particle size. Fixed in version 4.5.2.16.
      • [AER-6189] - (UDF) List creation via UDF does not initialize list flags, which may inadvertently flag the list as ordered. Fixed in version 4.5.2.15.
      • [AER-6179] - (KVS) When upgrading from version earlier than 4.5.1, pre-existing eviction depth is not used during startup. Fixed in version 4.5.2.14.
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure. Fixed in version 4.5.2.11.
      • [AER-6146] - (KVS) With debug-allocations enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.2.10.
      • [AER-6132] - (CDT) Get or remove by key for map with element count 1 and result type index or rank returns a list instead of a scalar. Fixed in version 4.5.2.8.
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.2.7.
      • [AER-6093] - (CDT) Get or remove by rank map operation with return type key or value returning nil element will access uninitialized memory. Fixed in version 4.5.2.6.
      • [AER-6094] - (CDT) Get or remove by key-list ordered map operation with return type index, where key-list elements are not in map returns incomplete response. Fixed in version 4.5.2.6.
      • [AER-6086] - (CDT) Single result operations returning boolean are not translated correctly to integer. Fixed in version 4.5.2.5.
      • [AER-6087] - (CDT) List operations by rank and with return type rank can crash when specifying out of range rank as input. Fixed in version 4.5.2.5.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [AER-6143] - (BALANCE) For strong-consistency namespaces, if quiescing nodes with non-roster nodes in the cluster, the wrong nodes may quiesce. Fixed in version 4.7.0.3.
      • [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.6.0.21.
      • [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.5.2.18.
      • [AER-6195] - (MIGRATION) Theoretical race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.2.16.
      • [AER-6178] - (STORAGE) Setting storage context configuration item compression dynamically for storage-engine memory namespaces is not prevented and may cause a crash. Fixed in version 4.5.2.15.
      • [AER-6175] - (BALANCE) For strong-consistency namespaces, appeal subsystem leaks memory, and has rare races which may cause crash or deadlock. Fixed in version 4.5.2.13.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item report-authentication true. Fixed in version 4.5.2.12.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.5.2.10.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.2.10.
      • [AER-6104] - (KVS) For index-type flash, index allocation errors may cause crash. Fixed in version 4.5.2.6.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart. Fixed in version 4.5.2.6.
      • [AER-6090] - (SECURITY) Batch sub-transactions' digests are not logged in the report-data-op audit trail. Fixed in version 4.5.2.5.
      • [AER-6089] - (XDR) Race condition across multiple connections in libcurl may cause crash. Fixed in version 4.5.2.5.

    Improvements

    • Enterprise & Community
      • [AER-6073] - (KVS) Validate the set name (if sent) in read and delete messages.

    Bug Fixes

    • Enterprise & Community
      • [AER-6077] - (BATCH) For storage-engine memory namespaces, batch transactions unnecessarily return an error if record size exceeds 10MB.
    • Enterprise Only
      • [AER-6072] - (XDR) Crash using multi-handles in curl library when using change notification.
      • [AER-6075] - (XDR) Dynamically setting xdr context configuration items when configuration file has no xdr context causes crash.

  • 4.5.2.3
    Release Date: May 31, 2019
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • Aerospike Tools version 3.18.1 dependencies
      • Aerospike Tools 3.18.1 now requires Python version 2.7.
      • Aerospike Tools 3.18.1 now requires Java version 1.8 or newer.

    Known Issues

    • 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. Fixed in version 4.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [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.7.0.21.
      • [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.6.0.21.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.5.3.19.
      • [AER-6128] - (BALANCE) For AP namespaces with prefer-uniform-balance true, non-optimal masters may be selected. Fixed in version 4.5.3.7.
      • [AER-6040] - (DEPLOYMENT) Aerospike will not start under systemd as non-root when using index-type value 'flash' or auto-pin value 'numa'. Fixed in version 4.5.3.2.
      • [AER-6053] - (SCAN) Dynamically decreasing service context configuration items scan-threads or sindex-builder-threads temporarily blocks all (other) dynamic configurations. Fixed in version 4.5.3.2.
      • [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. Fixed in version 4.5.2.17.
      • [AER-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.2.16.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.2.16.
      • [AER-6194] - (GEO) For namespaces with data-in-memory true, GeoJSON particles allocate up to 2KB more than the reported particle size. Fixed in version 4.5.2.16.
      • [AER-6189] - (UDF) List creation via UDF does not initialize list flags, which may inadvertently flag the list as ordered. Fixed in version 4.5.2.15.
      • [AER-6179] - (KVS) When upgrading from version earlier than 4.5.1, pre-existing eviction depth is not used during startup. Fixed in version 4.5.2.14.
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure. Fixed in version 4.5.2.11.
      • [AER-6146] - (KVS) With debug-allocations enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.2.10.
      • [AER-6132] - (CDT) Get or remove by key for map with element count 1 and result type index or rank returns a list instead of a scalar. Fixed in version 4.5.2.8.
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.2.7.
      • [AER-6093] - (CDT) Get or remove by rank map operation with return type key or value returning nil element will access uninitialized memory. Fixed in version 4.5.2.6.
      • [AER-6094] - (CDT) Get or remove by key-list ordered map operation with return type index, where key-list elements are not in map returns incomplete response. Fixed in version 4.5.2.6.
      • [AER-6086] - (CDT) Single result operations returning boolean are not translated correctly to integer. Fixed in version 4.5.2.5.
      • [AER-6087] - (CDT) List operations by rank and with return type rank can crash when specifying out of range rank as input. Fixed in version 4.5.2.5.
      • [AER-6077] - (BATCH) For storage-engine memory namespaces, batch transactions unnecessarily return an error if record size exceeds 10MB. Fixed in version 4.5.2.4.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [AER-6143] - (BALANCE) For strong-consistency namespaces, if quiescing nodes with non-roster nodes in the cluster, the wrong nodes may quiesce. Fixed in version 4.7.0.3.
      • [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.6.0.21.
      • [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.5.2.18.
      • [AER-6195] - (MIGRATION) Theoretical race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.2.16.
      • [AER-6178] - (STORAGE) Setting storage context configuration item compression dynamically for storage-engine memory namespaces is not prevented and may cause a crash. Fixed in version 4.5.2.15.
      • [AER-6175] - (BALANCE) For strong-consistency namespaces, appeal subsystem leaks memory, and has rare races which may cause crash or deadlock. Fixed in version 4.5.2.13.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item report-authentication true. Fixed in version 4.5.2.12.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.5.2.10.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.2.10.
      • [AER-6104] - (KVS) For index-type flash, index allocation errors may cause crash. Fixed in version 4.5.2.6.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart. Fixed in version 4.5.2.6.
      • [AER-6090] - (SECURITY) Batch sub-transactions' digests are not logged in the report-data-op audit trail. Fixed in version 4.5.2.5.
      • [AER-6089] - (XDR) Race condition across multiple connections in libcurl may cause crash. Fixed in version 4.5.2.5.
      • [AER-6072] - (XDR) Crash using multi-handles in curl library when using change notification. Fixed in version 4.5.2.4.
      • [AER-6075] - (XDR) Dynamically setting xdr context configuration items when configuration file has no xdr context causes crash. Fixed in version 4.5.2.4.

    Improvements

    • Enterprise & Community
      • [AER-6057] - (STORAGE) Added storage context configuration item disable-odsync to prevent setting O_DSYNC flag on storage devices.

    Bug Fixes

    • Enterprise & Community
      • [AER-6068] - (LOGGING) Concurrent SIGHUPs to roll log files may race and double close a log sink file descriptor.
    • Enterprise Only
      • [AER-6069] - (SECURITY) Minor memory leak during LDAP login process.

  • 4.5.2.2
    Release Date: April 26, 2019
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • Aerospike Tools version 3.18.1 dependencies
      • Aerospike Tools 3.18.1 now requires Python version 2.7.
      • Aerospike Tools 3.18.1 now requires Java version 1.8 or newer.

    Known Issues

    • 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. Fixed in version 4.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [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.7.0.21.
      • [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.6.0.21.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.5.3.19.
      • [AER-6128] - (BALANCE) For AP namespaces with prefer-uniform-balance true, non-optimal masters may be selected. Fixed in version 4.5.3.7.
      • [AER-6040] - (DEPLOYMENT) Aerospike will not start under systemd as non-root when using index-type value 'flash' or auto-pin value 'numa'. Fixed in version 4.5.3.2.
      • [AER-6053] - (SCAN) Dynamically decreasing service context configuration items scan-threads or sindex-builder-threads temporarily blocks all (other) dynamic configurations. Fixed in version 4.5.3.2.
      • [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. Fixed in version 4.5.2.17.
      • [AER-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.2.16.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.2.16.
      • [AER-6194] - (GEO) For namespaces with data-in-memory true, GeoJSON particles allocate up to 2KB more than the reported particle size. Fixed in version 4.5.2.16.
      • [AER-6189] - (UDF) List creation via UDF does not initialize list flags, which may inadvertently flag the list as ordered. Fixed in version 4.5.2.15.
      • [AER-6179] - (KVS) When upgrading from version earlier than 4.5.1, pre-existing eviction depth is not used during startup. Fixed in version 4.5.2.14.
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure. Fixed in version 4.5.2.11.
      • [AER-6146] - (KVS) With debug-allocations enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.2.10.
      • [AER-6132] - (CDT) Get or remove by key for map with element count 1 and result type index or rank returns a list instead of a scalar. Fixed in version 4.5.2.8.
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.2.7.
      • [AER-6093] - (CDT) Get or remove by rank map operation with return type key or value returning nil element will access uninitialized memory. Fixed in version 4.5.2.6.
      • [AER-6094] - (CDT) Get or remove by key-list ordered map operation with return type index, where key-list elements are not in map returns incomplete response. Fixed in version 4.5.2.6.
      • [AER-6086] - (CDT) Single result operations returning boolean are not translated correctly to integer. Fixed in version 4.5.2.5.
      • [AER-6087] - (CDT) List operations by rank and with return type rank can crash when specifying out of range rank as input. Fixed in version 4.5.2.5.
      • [AER-6077] - (BATCH) For storage-engine memory namespaces, batch transactions unnecessarily return an error if record size exceeds 10MB. Fixed in version 4.5.2.4.
      • [AER-6068] - (LOGGING) Concurrent SIGHUPs to roll log files may race and double close a log sink file descriptor. Fixed in version 4.5.2.3.
    • Enterprise Only
      • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
      • [AER-6143] - (BALANCE) For strong-consistency namespaces, if quiescing nodes with non-roster nodes in the cluster, the wrong nodes may quiesce. Fixed in version 4.7.0.3.
      • [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.6.0.21.
      • [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.5.2.18.
      • [AER-6195] - (MIGRATION) Theoretical race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.2.16.
      • [AER-6178] - (STORAGE) Setting storage context configuration item compression dynamically for storage-engine memory namespaces is not prevented and may cause a crash. Fixed in version 4.5.2.15.
      • [AER-6175] - (BALANCE) For strong-consistency namespaces, appeal subsystem leaks memory, and has rare races which may cause crash or deadlock. Fixed in version 4.5.2.13.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item report-authentication true. Fixed in version 4.5.2.12.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.5.2.10.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.2.10.
      • [AER-6104] - (KVS) For index-type flash, index allocation errors may cause crash. Fixed in version 4.5.2.6.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart. Fixed in version 4.5.2.6.
      • [AER-6090] - (SECURITY) Batch sub-transactions' digests are not logged in the report-data-op audit trail. Fixed in version 4.5.2.5.
      • [AER-6089] - (XDR) Race condition across multiple connections in libcurl may cause crash. Fixed in version 4.5.2.5.
      • [AER-6072] - (XDR) Crash using multi-handles in curl library when using change notification. Fixed in version 4.5.2.4.
      • [AER-6075] - (XDR) Dynamically setting xdr context configuration items when configuration file has no xdr context causes crash. Fixed in version 4.5.2.4.
      • [AER-6069] - (SECURITY) Minor memory leak during LDAP login process. Fixed in version 4.5.2.3.

    Bug Fixes

    • Enterprise & Community
      • [AER-6050] - (CDT) Extremely large unsorted lists or maps that require sorting within an operation may overflow the stack.
    • Enterprise Only
      • [AER-6048] - (STORAGE) Namespaces that use compression and have different write-block-size values may overwrite memory.
      • [AER-6049] - (XDR) May unnecessarily assert when a fresh socket goes bad while shipping to http destinations.

  • 4.5.2.1
    Release Date: April 1, 2019
    • Relaxed Strong Consistency Reads. (Enterprise Only)
    • Bin Shipping per Data Center dc-ship-bins. (Enterprise Only)
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • Aerospike Tools version 3.18.1 dependencies
      • Aerospike Tools 3.18.1 now requires Python version 2.7.
      • Aerospike Tools 3.18.1 now requires Java version 1.8 or newer.

    Known Issues

    • 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. Fixed in version 4.7.0.23.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range. Fixed in version 4.7.0.22.
      • [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.7.0.21.
      • [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.6.0.21.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.5.3.19.
      • [AER-6128] - (BALANCE) For AP namespaces with prefer-uniform-balance true, non-optimal masters may be selected. Fixed in version 4.5.3.7.
      • [AER-6040] - (DEPLOYMENT) Aerospike will not start under systemd as non-root when using index-type value 'flash' or auto-pin value 'numa'. Fixed in version 4.5.3.2.
      • [AER-6053] - (SCAN) Dynamically decreasing service context configuration items scan-threads or sindex-builder-threads temporarily blocks all (other) dynamic configurations. Fixed in version 4.5.3.2.
      • [AER-6211] - (KVS) Dynamically increasing both the system file descriptor limit and service context configuration item