Aerospike Server CE Release Notes

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

    Known Issues

    • Enterprise & Community
      • Record bins containing Complex Data Types (CDTs) 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. This 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 Ordered List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.

    Bug Fixes

    • Enterprise & Community
      • [AER-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) Rare 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.

    Known Issues

    • Enterprise & Community
      • Record bins containing Complex Data Types (CDTs) 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. This 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 Ordered 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-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-6195] - (MIGRATION) Rare 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.

    Known Issues

    • Enterprise & Community
      • Record bins containing Complex Data Types (CDTs) 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. This 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 Ordered 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-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-6195] - (MIGRATION) Rare 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.

    Known Issues

    • Enterprise & Community
      • Record bins containing Complex Data Types (CDTs) 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. This 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 Ordered 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-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-6195] - (MIGRATION) Rare 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.

    Known Issues

    • Enterprise & Community
      • Record bins containing Complex Data Types (CDTs) 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. This 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 Ordered 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-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-6195] - (MIGRATION) Rare 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.

    Known Issues

    • Enterprise & Community
      • Record bins containing Complex Data Types (CDTs) 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. This 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 Ordered 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-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-6195] - (MIGRATION) Rare 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.

    Known Issues

    • Enterprise & Community
      • Record bins containing Complex Data Types (CDTs) 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. This 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 Ordered 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-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-6195] - (MIGRATION) Rare 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.12
    Release Date: March 19, 2020
    • An Enterprise Edition version that includes Kerberos support is available upon request. Interested customers should contact their account representative.
    • 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 Types (CDTs) 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. This 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 Ordered List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • Enterprise Only
      • 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-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) Rare race condition may cause delta migration to complete without sending all records.

  • 4.7.0.11
    Release Date: February 28, 2020
    • An Enterprise Edition version that includes Kerberos support is available upon request. Interested customers should contact their account representative.
    • 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 Types (CDTs) 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. This 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 Ordered 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-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-6195] - (MIGRATION) Rare 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
    • An Enterprise Edition version that includes Kerberos support is available upon request. Interested customers should contact their account representative.
    • 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 Types (CDTs) 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. This 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 Ordered 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-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-6195] - (MIGRATION) Rare 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
    • An Enterprise Edition version that includes Kerberos support is available upon request. Interested customers should contact their account representative.
    • 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 Types (CDTs) 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. This 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 Ordered 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-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-6195] - (MIGRATION) Rare 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
    • An Enterprise Edition version that includes Kerberos support is available upon request. Interested customers should contact their account representative.
    • 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 Types (CDTs) 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. This 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 Ordered 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-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-6195] - (MIGRATION) Rare 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
    • An Enterprise Edition version that includes Kerberos support is available upon request. Interested customers should contact their account representative.
    • 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 Types (CDTs) 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. This 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 Ordered 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-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-6195] - (MIGRATION) Rare 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
    • An Enterprise Edition version that includes Kerberos support is available upon request. Interested customers should contact their account representative.
    • 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 Types (CDTs) 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. This 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 Ordered 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-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-6195] - (MIGRATION) Rare 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
    • An Enterprise Edition version that includes Kerberos support is available upon request. Interested customers should contact their account representative.
    • 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 Types (CDTs) 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. This 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 Ordered 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-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-6195] - (MIGRATION) Rare 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
    • An Enterprise Edition version that includes Kerberos support is available upon request. Interested customers should contact their account representative.
    • 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 Types (CDTs) 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. This 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 Ordered 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-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-6195] - (MIGRATION) Rare 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 Types (CDTs) 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. This 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 Ordered 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-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-6195] - (MIGRATION) Rare 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.14
    Release Date: March 19, 2020
    • A digitally signed feature key file is now required. (Enterprise Only - contact support@aerospike.com).
    • An Enterprise Edition version that includes Kerberos support is available upon request. Interested customers should contact their account representative.
    • 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 Types (CDTs) 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. This 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 Ordered 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-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-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-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) Rare 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 - contact support@aerospike.com).
    • An Enterprise Edition version that includes Kerberos support is available upon request. Interested customers should contact their account representative.
    • 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 Types (CDTs) 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. This 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 Ordered 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-6159] - (INFO) The 'thread-traces' info command can cause a deadlock. Fixed in version 4.7.0.6.
      • [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-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-6195] - (MIGRATION) Rare 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 - contact support@aerospike.com).
    • An Enterprise Edition version that includes Kerberos support is available upon request. Interested customers should contact their account representative.
    • 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 Types (CDTs) 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. This 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 Ordered 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-6159] - (INFO) The 'thread-traces' info command can cause a deadlock. Fixed in version 4.7.0.6.
      • [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-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-6195] - (MIGRATION) Rare 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 - contact support@aerospike.com).
    • An Enterprise Edition version that includes Kerberos support is available upon request. Interested customers should contact their account representative.
    • 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 Types (CDTs) 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. This 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 Ordered 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-6159] - (INFO) The 'thread-traces' info command can cause a deadlock. Fixed in version 4.7.0.6.
      • [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-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-6195] - (MIGRATION) Rare 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 - contact support@aerospike.com).
    • An Enterprise Edition version that includes Kerberos support is available upon request. Interested customers should contact their account representative.
    • 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 Types (CDTs) 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. This 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 Ordered 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-6159] - (INFO) The 'thread-traces' info command can cause a deadlock. Fixed in version 4.7.0.6.
      • [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-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-6195] - (MIGRATION) Rare 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 - contact support@aerospike.com).
    • An Enterprise Edition version that includes Kerberos support is available upon request. Interested customers should contact their account representative.
    • 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 Types (CDTs) 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. This 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 Ordered 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-6159] - (INFO) The 'thread-traces' info command can cause a deadlock. Fixed in version 4.7.0.6.
      • [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-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-6195] - (MIGRATION) Rare 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 - contact support@aerospike.com).
    • An Enterprise Edition version that includes Kerberos support is available upon request. Interested customers should contact their account representative.
    • 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 Types (CDTs) 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. This 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 Ordered 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-6159] - (INFO) The 'thread-traces' info command can cause a deadlock. Fixed in version 4.7.0.6.
      • [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-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-6195] - (MIGRATION) Rare 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 - contact support@aerospike.com).
    • An Enterprise Edition version that includes Kerberos support is available upon request. Interested customers should contact their account representative.
    • 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 Types (CDTs) 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. This 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 Ordered 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-6159] - (INFO) The 'thread-traces' info command can cause a deadlock. Fixed in version 4.7.0.6.
      • [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-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-6195] - (MIGRATION) Rare 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 - contact support@aerospike.com).
    • An Enterprise Edition version that includes Kerberos support is available upon request. Interested customers should contact their account representative.
    • 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 Types (CDTs) 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. This 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 Ordered 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-6159] - (INFO) The 'thread-traces' info command can cause a deadlock. Fixed in version 4.7.0.6.
      • [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-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-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-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-6195] - (MIGRATION) Rare 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 - contact support@aerospike.com).
    • An Enterprise Edition version that includes Kerberos support is available upon request. Interested customers should contact their account representative.
    • 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 Types (CDTs) 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. This 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 Ordered 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-6159] - (INFO) The 'thread-traces' info command can cause a deadlock. Fixed in version 4.7.0.6.
      • [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-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-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-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-6195] - (MIGRATION) Rare 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 - contact support@aerospike.com).

    • 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.
    • An Enterprise Edition version that includes Kerberos support is available upon request. Interested customers should contact their account representative.
    • 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.

    Known Issues

    • Enterprise & Community
      • Record bins containing Complex Data Types (CDTs) 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. This 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 Ordered 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-6159] - (INFO) The 'thread-traces' info command can cause a deadlock. Fixed in version 4.7.0.6.
      • [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-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-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-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-6195] - (MIGRATION) Rare 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.16
    Release Date: March 19, 2020
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • Enterprise & Community
      • [AER-6159] - (INFO) The 'thread-traces' info command can cause a deadlock. Fixed in version 4.7.0.6.
      • [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-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-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) Rare 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-6159] - (INFO) The 'thread-traces' info command can cause a deadlock. Fixed in version 4.7.0.6.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-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-6195] - (MIGRATION) Rare 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-6159] - (INFO) The 'thread-traces' info command can cause a deadlock. Fixed in version 4.7.0.6.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-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-6195] - (MIGRATION) Rare 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-6159] - (INFO) The 'thread-traces' info command can cause a deadlock. Fixed in version 4.7.0.6.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-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-6195] - (MIGRATION) Rare 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-6159] - (INFO) The 'thread-traces' info command can cause a deadlock. Fixed in version 4.7.0.6.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-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-6195] - (MIGRATION) Rare 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-6159] - (INFO) The 'thread-traces' info command can cause a deadlock. Fixed in version 4.7.0.6.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-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-6195] - (MIGRATION) Rare 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-6159] - (INFO) The 'thread-traces' info command can cause a deadlock. Fixed in version 4.7.0.6.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-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-6195] - (MIGRATION) Rare 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-6159] - (INFO) The 'thread-traces' info command can cause a deadlock. Fixed in version 4.7.0.6.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-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-6195] - (MIGRATION) Rare 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-6159] - (INFO) The 'thread-traces' info command can cause a deadlock. Fixed in version 4.7.0.6.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-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-6195] - (MIGRATION) Rare 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-6159] - (INFO) The 'thread-traces' info command can cause a deadlock. Fixed in version 4.7.0.6.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-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-6195] - (MIGRATION) Rare 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-6159] - (INFO) The 'thread-traces' info command can cause a deadlock. Fixed in version 4.7.0.6.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-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-6195] - (MIGRATION) Rare 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-6159] - (INFO) The 'thread-traces' info command can cause a deadlock. Fixed in version 4.7.0.6.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-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-6195] - (MIGRATION) Rare 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-6159] - (INFO) The 'thread-traces' info command can cause a deadlock. Fixed in version 4.7.0.6.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-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-6195] - (MIGRATION) Rare 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-6159] - (INFO) The 'thread-traces' info command can cause a deadlock. Fixed in version 4.7.0.6.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-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-6195] - (MIGRATION) Rare 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.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-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-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-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) Rare 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-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-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-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-6195] - (MIGRATION) Rare 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-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-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-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-6195] - (MIGRATION) Rare 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-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-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-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-6195] - (MIGRATION) Rare 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-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-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-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-6195] - (MIGRATION) Rare 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-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-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-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-6195] - (MIGRATION) Rare 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-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-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-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-6195] - (MIGRATION) Rare 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-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-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-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-6195] - (MIGRATION) Rare 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-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-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-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-6195] - (MIGRATION) Rare 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-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-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-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-6195] - (MIGRATION) Rare 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-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-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-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-6195] - (MIGRATION) Rare 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-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-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-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-6195] - (MIGRATION) Rare 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-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-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-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-6195] - (MIGRATION) Rare 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-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-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-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-6195] - (MIGRATION) Rare 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-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-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.
      • [AER-6050] - (CDT) Extremely large unsorted lists or maps that require sorting within an operation may overflow the stack. Fixed in version 4.5.2.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-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-6195] - (MIGRATION) Rare 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.
      • [AER-6048] - (STORAGE) Namespaces that use compression and have different `write-block-size` values may overwrite memory. Fixed in version 4.5.2.2.
      • [AER-6049] - (XDR) May unnecessarily assert when a fresh socket goes bad while shipping to http destinations. Fixed in version 4.5.2.2.

    New Features

    • Enterprise Only
      • [AER-6037] - (KVS) Added relaxed read modes for `strong-consistency` namespaces.
      • [AER-6025] - (XDR) Added datacenter context configuration item `dc-ship-bins` to allow bin shipping per DC.

    Improvements

    • Enterprise & Community
      • [AER-6013] - (INFO) Added client address to log lines for scan starts, and to job monitor info where appropriate.
      • [AER-6024] - (INFO) Made service context configuration item `info-threads` dynamic.
      • [AER-6030] - (INFO) Added socket timeout to log lines for scan starts, and to job monitor info where appropriate.
      • [AER-6023] - (STORAGE) Optimized hot key writes when record updates do not change stored size.
    • Enterprise Only
      • [AER-6033] - (KVS) For `strong-consistency` namespaces, improved replica write retransmission in various rare situations.
      • [AER-6026] - (BALANCE) Removed info command 'protect-roster-set' - protection is now automatic.

    Bug Fixes

    • Enterprise Only
      • [AER-6035] - (BALANCE) For AP namespaces with `prefer-uniform-balance` true, there may be redundant migrations after shutting down a quiesced node.
      • [AER-6041] - (XDR) Honor compression threshold configuration for http destination.

  • 4.5.1.21
    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-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-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-6035] - (BALANCE) For AP namespaces with `prefer-uniform-balance` true, there may be redundant migrations after shutting down a quiesced node. Fixed in version 4.5.2.1.
      • [AER-6041] - (XDR) Honor compression threshold configuration for http destination. Fixed in version 4.5.2.1.

    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) Rare race condition may cause delta migration to complete without sending all records.

  • 4.5.1.20
    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-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.1.21.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.1.21.
      • [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.1.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-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-6035] - (BALANCE) For AP namespaces with `prefer-uniform-balance` true, there may be redundant migrations after shutting down a quiesced node. Fixed in version 4.5.2.1.
      • [AER-6041] - (XDR) Honor compression threshold configuration for http destination. Fixed in version 4.5.2.1.
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.1.21.

    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.1.19
    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-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.1.21.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.1.21.
      • [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.1.21.
      • [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.1.20.
    • 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-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-6035] - (BALANCE) For AP namespaces with `prefer-uniform-balance` true, there may be redundant migrations after shutting down a quiesced node. Fixed in version 4.5.2.1.
      • [AER-6041] - (XDR) Honor compression threshold configuration for http destination. Fixed in version 4.5.2.1.
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.1.21.
      • [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.1.20.

    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.1.18
    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-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.1.21.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.1.21.
      • [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.1.21.
      • [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.1.20.
      • [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.1.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-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-6035] - (BALANCE) For AP namespaces with `prefer-uniform-balance` true, there may be redundant migrations after shutting down a quiesced node. Fixed in version 4.5.2.1.
      • [AER-6041] - (XDR) Honor compression threshold configuration for http destination. Fixed in version 4.5.2.1.
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.1.21.
      • [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.1.20.

    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.1.17
    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-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.1.21.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.1.21.
      • [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.1.21.
      • [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.1.20.
      • [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.1.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-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-6035] - (BALANCE) For AP namespaces with `prefer-uniform-balance` true, there may be redundant migrations after shutting down a quiesced node. Fixed in version 4.5.2.1.
      • [AER-6041] - (XDR) Honor compression threshold configuration for http destination. Fixed in version 4.5.2.1.
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.1.21.
      • [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.1.20.
      • [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.1.18.

    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.1.16
    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-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.1.21.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.1.21.
      • [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.1.21.
      • [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.1.20.
      • [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.1.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-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-6035] - (BALANCE) For AP namespaces with `prefer-uniform-balance` true, there may be redundant migrations after shutting down a quiesced node. Fixed in version 4.5.2.1.
      • [AER-6041] - (XDR) Honor compression threshold configuration for http destination. Fixed in version 4.5.2.1.
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.1.21.
      • [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.1.20.
      • [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.1.18.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item 'report-authentication' true. Fixed in version 4.5.1.17.

    Bug Fixes

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

  • 4.5.1.15
    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-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.1.21.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.1.21.
      • [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.1.21.
      • [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.1.20.
      • [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.1.19.
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure. Fixed in version 4.5.1.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-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-6035] - (BALANCE) For AP namespaces with `prefer-uniform-balance` true, there may be redundant migrations after shutting down a quiesced node. Fixed in version 4.5.2.1.
      • [AER-6041] - (XDR) Honor compression threshold configuration for http destination. Fixed in version 4.5.2.1.
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.1.21.
      • [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.1.20.
      • [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.1.18.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item 'report-authentication' true. Fixed in version 4.5.1.17.

    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.1.13
    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-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.1.21.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.1.21.
      • [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.1.21.
      • [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.1.20.
      • [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.1.19.
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure. Fixed in version 4.5.1.16.
      • [AER-6146] - (KVS) With 'debug-allocations' enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.1.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-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-6035] - (BALANCE) For AP namespaces with `prefer-uniform-balance` true, there may be redundant migrations after shutting down a quiesced node. Fixed in version 4.5.2.1.
      • [AER-6041] - (XDR) Honor compression threshold configuration for http destination. Fixed in version 4.5.2.1.
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.1.21.
      • [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.1.20.
      • [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.1.18.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item 'report-authentication' true. Fixed in version 4.5.1.17.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.5.1.15.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.1.15.

    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.1.12
    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-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.1.21.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.1.21.
      • [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.1.21.
      • [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.1.20.
      • [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.1.19.
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure. Fixed in version 4.5.1.16.
      • [AER-6146] - (KVS) With 'debug-allocations' enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.1.15.
      • [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.1.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-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-6035] - (BALANCE) For AP namespaces with `prefer-uniform-balance` true, there may be redundant migrations after shutting down a quiesced node. Fixed in version 4.5.2.1.
      • [AER-6041] - (XDR) Honor compression threshold configuration for http destination. Fixed in version 4.5.2.1.
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.1.21.
      • [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.1.20.
      • [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.1.18.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item 'report-authentication' true. Fixed in version 4.5.1.17.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.5.1.15.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.1.15.

    Bug Fixes

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

  • 4.5.1.11
    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-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.1.21.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.1.21.
      • [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.1.21.
      • [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.1.20.
      • [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.1.19.
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure. Fixed in version 4.5.1.16.
      • [AER-6146] - (KVS) With 'debug-allocations' enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.1.15.
      • [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.1.13.
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.1.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-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-6035] - (BALANCE) For AP namespaces with `prefer-uniform-balance` true, there may be redundant migrations after shutting down a quiesced node. Fixed in version 4.5.2.1.
      • [AER-6041] - (XDR) Honor compression threshold configuration for http destination. Fixed in version 4.5.2.1.
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.1.21.
      • [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.1.20.
      • [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.1.18.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item 'report-authentication' true. Fixed in version 4.5.1.17.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.5.1.15.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.1.15.

    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.1.10
    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-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.1.21.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.1.21.
      • [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.1.21.
      • [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.1.20.
      • [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.1.19.
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure. Fixed in version 4.5.1.16.
      • [AER-6146] - (KVS) With 'debug-allocations' enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.1.15.
      • [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.1.13.
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.1.12.
      • [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.1.11.
      • [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.1.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-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-6035] - (BALANCE) For AP namespaces with `prefer-uniform-balance` true, there may be redundant migrations after shutting down a quiesced node. Fixed in version 4.5.2.1.
      • [AER-6041] - (XDR) Honor compression threshold configuration for http destination. Fixed in version 4.5.2.1.
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.1.21.
      • [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.1.20.
      • [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.1.18.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item 'report-authentication' true. Fixed in version 4.5.1.17.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.5.1.15.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.1.15.
      • [AER-6104] - (KVS) For ‘index-type flash’, index allocation errors may cause crash. Fixed in version 4.5.1.11.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart. Fixed in version 4.5.1.11.

    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.1.9
    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-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.1.21.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.1.21.
      • [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.1.21.
      • [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.1.20.
      • [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.1.19.
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure. Fixed in version 4.5.1.16.
      • [AER-6146] - (KVS) With 'debug-allocations' enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.1.15.
      • [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.1.13.
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.1.12.
      • [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.1.11.
      • [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.1.11.
      • [AER-6086] - (CDT) Single result operations returning boolean are not translated correctly to integer. Fixed in version 4.5.1.10.
      • [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.1.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-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-6035] - (BALANCE) For AP namespaces with `prefer-uniform-balance` true, there may be redundant migrations after shutting down a quiesced node. Fixed in version 4.5.2.1.
      • [AER-6041] - (XDR) Honor compression threshold configuration for http destination. Fixed in version 4.5.2.1.
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.1.21.
      • [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.1.20.
      • [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.1.18.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item 'report-authentication' true. Fixed in version 4.5.1.17.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.5.1.15.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.1.15.
      • [AER-6104] - (KVS) For ‘index-type flash’, index allocation errors may cause crash. Fixed in version 4.5.1.11.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart. Fixed in version 4.5.1.11.
      • [AER-6090] - (SECURITY) Batch sub-transactions' digests are not logged in the 'report-data-op' audit trail. Fixed in version 4.5.1.10.
      • [AER-6089] - (XDR) Race condition across multiple connections in libcurl may cause crash. Fixed in version 4.5.1.10.

    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.1.8
    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-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.1.21.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.1.21.
      • [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.1.21.
      • [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.1.20.
      • [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.1.19.
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure. Fixed in version 4.5.1.16.
      • [AER-6146] - (KVS) With 'debug-allocations' enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.1.15.
      • [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.1.13.
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.1.12.
      • [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.1.11.
      • [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.1.11.
      • [AER-6086] - (CDT) Single result operations returning boolean are not translated correctly to integer. Fixed in version 4.5.1.10.
      • [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.1.10.
      • [AER-6077] - (BATCH) For 'storage-engine memory' namespaces, batch transactions unnecessarily return an error if record size exceeds 10MB. Fixed in version 4.5.1.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-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-6035] - (BALANCE) For AP namespaces with `prefer-uniform-balance` true, there may be redundant migrations after shutting down a quiesced node. Fixed in version 4.5.2.1.
      • [AER-6041] - (XDR) Honor compression threshold configuration for http destination. Fixed in version 4.5.2.1.
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.1.21.
      • [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.1.20.
      • [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.1.18.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item 'report-authentication' true. Fixed in version 4.5.1.17.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.5.1.15.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.1.15.
      • [AER-6104] - (KVS) For ‘index-type flash’, index allocation errors may cause crash. Fixed in version 4.5.1.11.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart. Fixed in version 4.5.1.11.
      • [AER-6090] - (SECURITY) Batch sub-transactions' digests are not logged in the 'report-data-op' audit trail. Fixed in version 4.5.1.10.
      • [AER-6089] - (XDR) Race condition across multiple connections in libcurl may cause crash. Fixed in version 4.5.1.10.
      • [AER-6072] - (XDR) Crash using multi-handles in curl library when using change notification. Fixed in version 4.5.1.9.
      • [AER-6075] - (XDR) Dynamically setting xdr context configuration items when configuration file has no xdr context causes crash. Fixed in version 4.5.1.9.

    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.1.7
    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-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.1.21.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.1.21.
      • [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.1.21.
      • [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.1.20.
      • [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.1.19.
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure. Fixed in version 4.5.1.16.
      • [AER-6146] - (KVS) With 'debug-allocations' enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.1.15.
      • [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.1.13.
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.1.12.
      • [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.1.11.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart. Fixed in version 4.5.1.11.
      • [AER-6086] - (CDT) Single result operations returning boolean are not translated correctly to integer. Fixed in version 4.5.1.10.
      • [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.1.10.
      • [AER-6077] - (BATCH) For 'storage-engine memory' namespaces, batch transactions unnecessarily return an error if record size exceeds 10MB. Fixed in version 4.5.1.9.
      • [AER-6068] - (LOGGING) Concurrent SIGHUPs to roll log files may race and double close a log sink file descriptor. Fixed in version 4.5.1.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-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-6035] - (BALANCE) For AP namespaces with `prefer-uniform-balance` true, there may be redundant migrations after shutting down a quiesced node. Fixed in version 4.5.2.1.
      • [AER-6041] - (XDR) Honor compression threshold configuration for http destination. Fixed in version 4.5.2.1.
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.1.21.
      • [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.1.20.
      • [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.1.18.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item 'report-authentication' true. Fixed in version 4.5.1.17.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.5.1.15.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.1.15.
      • [AER-6104] - (KVS) For ‘index-type flash’, index allocation errors may cause crash. Fixed in version 4.5.1.11.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart. Fixed in version 4.5.1.11.
      • [AER-6090] - (SECURITY) Batch sub-transactions' digests are not logged in the 'report-data-op' audit trail. Fixed in version 4.5.1.10.
      • [AER-6089] - (XDR) Race condition across multiple connections in libcurl may cause crash. Fixed in version 4.5.1.10.
      • [AER-6072] - (XDR) Crash using multi-handles in curl library when using change notification. Fixed in version 4.5.1.9.
      • [AER-6075] - (XDR) Dynamically setting xdr context configuration items when configuration file has no xdr context causes crash. Fixed in version 4.5.1.9.
      • [AER-6069] - (SECURITY) Minor memory leak during LDAP login process. Fixed in version 4.5.1.8.

    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.1.6
    Release Date: March 25, 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-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.1.21.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.1.21.
      • [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.1.21.
      • [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.1.20.
      • [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.1.19.
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure. Fixed in version 4.5.1.16.
      • [AER-6146] - (KVS) With 'debug-allocations' enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.1.15.
      • [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.1.13.
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.1.12.
      • [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.1.11.
      • [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.1.11.
      • [AER-6086] - (CDT) Single result operations returning boolean are not translated correctly to integer. Fixed in version 4.5.1.10.
      • [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.1.10.
      • [AER-6077] - (BATCH) For 'storage-engine memory' namespaces, batch transactions unnecessarily return an error if record size exceeds 10MB. Fixed in version 4.5.1.9.
      • [AER-6068] - (LOGGING) Concurrent SIGHUPs to roll log files may race and double close a log sink file descriptor. Fixed in version 4.5.1.8.
      • [AER-6050] - (CDT) Extremely large unsorted lists or maps that require sorting within an operation may overflow the stack. Fixed in version 4.5.1.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-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-6035] - (BALANCE) For AP namespaces with `prefer-uniform-balance` true, there may be redundant migrations after shutting down a quiesced node. Fixed in version 4.5.2.1.
      • [AER-6041] - (XDR) Honor compression threshold configuration for http destination. Fixed in version 4.5.2.1.
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.1.21.
      • [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.1.20.
      • [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.1.18.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item 'report-authentication' true. Fixed in version 4.5.1.17.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.5.1.15.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.1.15.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart. Fixed in version 4.5.1.11.
      • [AER-6090] - (SECURITY) Batch sub-transactions' digests are not logged in the 'report-data-op' audit trail. Fixed in version 4.5.1.10.
      • [AER-6089] - (XDR) Race condition across multiple connections in libcurl may cause crash. Fixed in version 4.5.1.10.
      • [AER-6072] - (XDR) Crash using multi-handles in curl library when using change notification. Fixed in version 4.5.1.9.
      • [AER-6075] - (XDR) Dynamically setting xdr context configuration items when configuration file has no xdr context causes crash. Fixed in version 4.5.1.9.
      • [AER-6069] - (SECURITY) Minor memory leak during LDAP login process. Fixed in version 4.5.1.8.
      • [AER-6048] - (STORAGE) Namespaces that use compression and have different `write-block-size` values may overwrite memory. Fixed in version 4.5.1.7.
      • [AER-6049] - (XDR) May unnecessarily assert when a fresh socket goes bad while shipping to http destinations. Fixed in version 4.5.1.7.

    Improvements

    • Enterprise Only
      • [AER-6036] - (TLS) Do not block a TLS socket for a full second, for example when non-TLS connections are attempted.

    Bug Fixes

    • Enterprise & Community
      • [AER-6028] - (KVS) Proxied requests are failed by destination node before its first rebalance instead of returned to sender for retry.
      • [AER-6034] - (SCAN) Scans with a socket timeout of zero (meaning never time out) inadvertently time out.
      • [AER-6029] - (FABRIC) Load balance counter for send threads does not decrement correctly in certain rare circumstances.
    • Enterprise Only
      • [AER-6031] - (KVS) For 'strong-consistency' namespaces, replications may unnecessarily assert when they are concurrent with non-durable deletes.

  • 4.5.1.5
    Release Date: February 26, 2019
    • System Metadata (SMD) Protocol Change
      • When upgrading the Aerospike Server, from a version prior to 4.5.1, follow the 4.5 special upgrade document 4.5.1+ SMD protocol change.
    • 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-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.1.21.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.1.21.
      • [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.1.21.
      • [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.1.20.
      • [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.1.19.
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure. Fixed in version 4.5.1.16.
      • [AER-6146] - (KVS) With 'debug-allocations' enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.1.15.
      • [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.1.13.
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.1.12.
      • [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.1.11.
      • [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.1.11.
      • [AER-6086] - (CDT) Single result operations returning boolean are not translated correctly to integer. Fixed in version 4.5.1.10.
      • [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.1.10.
      • [AER-6077] - (BATCH) For 'storage-engine memory' namespaces, batch transactions unnecessarily return an error if record size exceeds 10MB. Fixed in version 4.5.1.9.
      • [AER-6068] - (LOGGING) Concurrent SIGHUPs to roll log files may race and double close a log sink file descriptor. Fixed in version 4.5.1.8.
      • [AER-6050] - (CDT) Extremely large unsorted lists or maps that require sorting within an operation may overflow the stack. Fixed in version 4.5.1.7.
      • [AER-6028] - (KVS) Proxied requests are failed by destination node before its first rebalance instead of returned to sender for retry. Fixed in version 4.5.1.6.
      • [AER-6034] - (SCAN) Scans with a socket timeout of zero (meaning never time out) inadvertently time out. Fixed in version 4.5.1.6.
      • [AER-6029] - (FABRIC) Load balance counter for send threads does not decrement correctly in certain rare circumstances. Fixed in version 4.5.1.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-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-6035] - (BALANCE) For AP namespaces with `prefer-uniform-balance` true, there may be redundant migrations after shutting down a quiesced node. Fixed in version 4.5.2.1.
      • [AER-6041] - (XDR) Honor compression threshold configuration for http destination. Fixed in version 4.5.2.1.
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.1.21.
      • [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.1.20.
      • [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.1.18.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item 'report-authentication' true. Fixed in version 4.5.1.17.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.5.1.15.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.1.15.
      • [AER-6104] - (KVS) For ‘index-type flash’, index allocation errors may cause crash. Fixed in version 4.5.1.11.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart. Fixed in version 4.5.1.11.
      • [AER-6090] - (SECURITY) Batch sub-transactions' digests are not logged in the 'report-data-op' audit trail. Fixed in version 4.5.1.10.
      • [AER-6089] - (XDR) Race condition across multiple connections in libcurl may cause crash. Fixed in version 4.5.1.10.
      • [AER-6072] - (XDR) Crash using multi-handles in curl library when using change notification. Fixed in version 4.5.1.9.
      • [AER-6075] - (XDR) Dynamically setting xdr context configuration items when configuration file has no xdr context causes crash. Fixed in version 4.5.1.9.
      • [AER-6069] - (SECURITY) Minor memory leak during LDAP login process. Fixed in version 4.5.1.8.
      • [AER-6048] - (STORAGE) Namespaces that use compression and have different `write-block-size` values may overwrite memory. Fixed in version 4.5.1.7.
      • [AER-6049] - (XDR) May unnecessarily assert when a fresh socket goes bad while shipping to http destinations. Fixed in version 4.5.1.7.
      • [AER-6031] - (KVS) For 'strong-consistency' namespaces, replications may unnecessarily assert when they are concurrent with non-durable deletes. Fixed in version 4.5.1.6.

    Improvements

    • Enterprise & Community
      • [AER-6000] - (KVS) Redesigned namespace supervisor (nsup), featuring expiration and eviction without transactions, and per-namespace control.
      • [AER-6011] - (KVS) Deprecated namespace context configuration items 'max-ttl' and 'cold-start-evict-ttl'.
      • [AER-5999] - (SMD) Redesigned SMD layer to be more efficient and robust.
      • [AER-6008] - (LOGGING) Eliminated excessive error logging to /tmp/aerospike-console when rolling log file.
      • [AER-5980] - (STATS) Added detailed 'from_proxy' stats, for transactions proxied from another node.
    • Enterprise Only
      • [AER-6010] - (TLS) Changed three 'info' level logs that appeared with every new TLS connection to 'detail' level.
      • [AER-6004] - (MIGRATION) Support `strong-consistency` clusters with a mixture of `storage-engine` values ('memory' and 'device').

    Updates

  • 4.5.0.24
    Release Date: March 19, 2020
    • The CentOS 7 RPM packages are built with OpenSSL 1.0.2, which is the current shipping package version. If you are running on an older version of CentOS 7 which uses OpenSSL 1.0.1, the installation will not succeed due to a dependency mismatch. Please resolve by either updating CentOS patches (security or whole release) to a point where OpenSSL 1.0.2 is used, or install OpenSSL 1.0.2 using "yum update openssl".
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • Enterprise & Community
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-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-6035] - (BALANCE) For AP namespaces with `prefer-uniform-balance` true, there may be redundant migrations after shutting down a quiesced node. Fixed in version 4.5.2.1.
      • [AER-6041] - (XDR) Honor compression threshold configuration for http destination. Fixed in version 4.5.2.1.

    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) Rare race condition may cause delta migration to complete without sending all records.

  • 4.5.0.23
    Release Date: February 28, 2020
    • The CentOS 7 RPM packages are built with OpenSSL 1.0.2, which is the current shipping package version. If you are running on an older version of CentOS 7 which uses OpenSSL 1.0.1, the installation will not succeed due to a dependency mismatch. Please resolve by either updating CentOS patches (security or whole release) to a point where OpenSSL 1.0.2 is used, or install OpenSSL 1.0.2 using "yum update openssl".
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • Enterprise & Community
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.0.24.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.0.24.
      • [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.0.24.
    • 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-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-6035] - (BALANCE) For AP namespaces with `prefer-uniform-balance` true, there may be redundant migrations after shutting down a quiesced node. Fixed in version 4.5.2.1.
      • [AER-6041] - (XDR) Honor compression threshold configuration for http destination. Fixed in version 4.5.2.1.
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.0.24.

    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.0.22
    Release Date: January 15, 2020
    • The CentOS 7 RPM packages are built with OpenSSL 1.0.2, which is the current shipping package version. If you are running on an older version of CentOS 7 which uses OpenSSL 1.0.1, the installation will not succeed due to a dependency mismatch. Please resolve by either updating CentOS patches (security or whole release) to a point where OpenSSL 1.0.2 is used, or install OpenSSL 1.0.2 using "yum update openssl".
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • Enterprise & Community
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.0.24.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.0.24.
      • [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.0.24.
      • [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.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.
      • [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-6035] - (BALANCE) For AP namespaces with `prefer-uniform-balance` true, there may be redundant migrations after shutting down a quiesced node. Fixed in version 4.5.2.1.
      • [AER-6041] - (XDR) Honor compression threshold configuration for http destination. Fixed in version 4.5.2.1.
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.0.24.
      • [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.0.23.

    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.0.21
    Release Date: December 16, 2019
    • The CentOS 7 RPM packages are built with OpenSSL 1.0.2, which is the current shipping package version. If you are running on an older version of CentOS 7 which uses OpenSSL 1.0.1, the installation will not succeed due to a dependency mismatch. Please resolve by either updating CentOS patches (security or whole release) to a point where OpenSSL 1.0.2 is used, or install OpenSSL 1.0.2 using "yum update openssl".
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • Enterprise & Community
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.0.24.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.0.24.
      • [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.0.24.
      • [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.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.
      • [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-6035] - (BALANCE) For AP namespaces with `prefer-uniform-balance` true, there may be redundant migrations after shutting down a quiesced node. Fixed in version 4.5.2.1.
      • [AER-6041] - (XDR) Honor compression threshold configuration for http destination. Fixed in version 4.5.2.1.
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.0.24.
      • [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.0.23.
      • [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.0.22.

    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.0.20
    Release Date: December 6, 2019
    • The CentOS 7 RPM packages are built with OpenSSL 1.0.2, which is the current shipping package version. If you are running on an older version of CentOS 7 which uses OpenSSL 1.0.1, the installation will not succeed due to a dependency mismatch. Please resolve by either updating CentOS patches (security or whole release) to a point where OpenSSL 1.0.2 is used, or install OpenSSL 1.0.2 using "yum update openssl".
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • Enterprise & Community
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.0.24.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.0.24.
      • [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.0.24.
      • [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.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.
      • [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-6035] - (BALANCE) For AP namespaces with `prefer-uniform-balance` true, there may be redundant migrations after shutting down a quiesced node. Fixed in version 4.5.2.1.
      • [AER-6041] - (XDR) Honor compression threshold configuration for http destination. Fixed in version 4.5.2.1.
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.0.24.
      • [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.0.23.
      • [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.0.22.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item 'report-authentication' true. Fixed in version 4.5.0.21.

    Bug Fixes

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

  • 4.5.0.19
    Release Date: November 14, 2019
    • The CentOS 7 RPM packages are built with OpenSSL 1.0.2, which is the current shipping package version. If you are running on an older version of CentOS 7 which uses OpenSSL 1.0.1, the installation will not succeed due to a dependency mismatch. Please resolve by either updating CentOS patches (security or whole release) to a point where OpenSSL 1.0.2 is used, or install OpenSSL 1.0.2 using "yum update openssl".
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • Enterprise & Community
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.0.24.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.0.24.
      • [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.0.24.
      • [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.0.23.
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure. Fixed in version 4.5.0.20.
    • 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-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-6035] - (BALANCE) For AP namespaces with `prefer-uniform-balance` true, there may be redundant migrations after shutting down a quiesced node. Fixed in version 4.5.2.1.
      • [AER-6041] - (XDR) Honor compression threshold configuration for http destination. Fixed in version 4.5.2.1.
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.0.24.
      • [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.0.23.
      • [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.0.22.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item 'report-authentication' true. Fixed in version 4.5.0.21.

    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.0.17
    Release Date: November 1, 2019
    • The CentOS 7 RPM packages are built with OpenSSL 1.0.2, which is the current shipping package version. If you are running on an older version of CentOS 7 which uses OpenSSL 1.0.1, the installation will not succeed due to a dependency mismatch. Please resolve by either updating CentOS patches (security or whole release) to a point where OpenSSL 1.0.2 is used, or install OpenSSL 1.0.2 using "yum update openssl".
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • Enterprise & Community
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.0.24.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.0.24.
      • [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.0.24.
      • [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.0.23.
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure. Fixed in version 4.5.0.20.
      • [AER-6146] - (KVS) With 'debug-allocations' enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.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-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-6035] - (BALANCE) For AP namespaces with `prefer-uniform-balance` true, there may be redundant migrations after shutting down a quiesced node. Fixed in version 4.5.2.1.
      • [AER-6041] - (XDR) Honor compression threshold configuration for http destination. Fixed in version 4.5.2.1.
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.0.24.
      • [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.0.23.
      • [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.0.22.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item 'report-authentication' true. Fixed in version 4.5.0.21.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.5.0.19.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.0.19.

    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.0.16
    Release Date: October 3, 2019
    • The CentOS 7 RPM packages are built with OpenSSL 1.0.2, which is the current shipping package version. If you are running on an older version of CentOS 7 which uses OpenSSL 1.0.1, the installation will not succeed due to a dependency mismatch. Please resolve by either updating CentOS patches (security or whole release) to a point where OpenSSL 1.0.2 is used, or install OpenSSL 1.0.2 using "yum update openssl".
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • Enterprise & Community
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.0.24.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.0.24.
      • [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.0.24.
      • [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.0.23.
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure. Fixed in version 4.5.0.20.
      • [AER-6146] - (KVS) With 'debug-allocations' enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.0.19.
      • [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.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-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-6035] - (BALANCE) For AP namespaces with `prefer-uniform-balance` true, there may be redundant migrations after shutting down a quiesced node. Fixed in version 4.5.2.1.
      • [AER-6041] - (XDR) Honor compression threshold configuration for http destination. Fixed in version 4.5.2.1.
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.0.24.
      • [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.0.23.
      • [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.0.22.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item 'report-authentication' true. Fixed in version 4.5.0.21.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.5.0.19.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.0.19.

    Bug Fixes

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

  • 4.5.0.15
    Release Date: August 28, 2019
    • The CentOS 7 RPM packages are built with OpenSSL 1.0.2, which is the current shipping package version. If you are running on an older version of CentOS 7 which uses OpenSSL 1.0.1, the installation will not succeed due to a dependency mismatch. Please resolve by either updating CentOS patches (security or whole release) to a point where OpenSSL 1.0.2 is used, or install OpenSSL 1.0.2 using "yum update openssl".
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • Enterprise & Community
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.0.24.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.0.24.
      • [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.0.24.
      • [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.0.23.
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure. Fixed in version 4.5.0.20.
      • [AER-6146] - (KVS) With 'debug-allocations' enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.0.19.
      • [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.0.17.
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.0.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-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-6035] - (BALANCE) For AP namespaces with `prefer-uniform-balance` true, there may be redundant migrations after shutting down a quiesced node. Fixed in version 4.5.2.1.
      • [AER-6041] - (XDR) Honor compression threshold configuration for http destination. Fixed in version 4.5.2.1.
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.0.24.
      • [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.0.23.
      • [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.0.22.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item 'report-authentication' true. Fixed in version 4.5.0.21.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.5.0.19.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.0.19.

    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.0.14
    Release Date: July 31, 2019
    • The CentOS 7 RPM packages are built with OpenSSL 1.0.2, which is the current shipping package version. If you are running on an older version of CentOS 7 which uses OpenSSL 1.0.1, the installation will not succeed due to a dependency mismatch. Please resolve by either updating CentOS patches (security or whole release) to a point where OpenSSL 1.0.2 is used, or install OpenSSL 1.0.2 using "yum update openssl".
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • Enterprise & Community
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.0.24.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.0.24.
      • [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.0.24.
      • [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.0.23.
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure. Fixed in version 4.5.0.20.
      • [AER-6146] - (KVS) With 'debug-allocations' enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.0.19.
      • [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.0.17.
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.0.16.
      • [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.0.15.
      • [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.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-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-6035] - (BALANCE) For AP namespaces with `prefer-uniform-balance` true, there may be redundant migrations after shutting down a quiesced node. Fixed in version 4.5.2.1.
      • [AER-6041] - (XDR) Honor compression threshold configuration for http destination. Fixed in version 4.5.2.1.
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.0.24.
      • [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.0.23.
      • [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.0.22.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item 'report-authentication' true. Fixed in version 4.5.0.21.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.5.0.19.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.0.19.
      • [AER-6104] - (KVS) For ‘index-type flash’, index allocation errors may cause crash. Fixed in version 4.5.0.15.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart. Fixed in version 4.5.0.15.

    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.0.13
    Release Date: June 28, 2019
    • The CentOS 7 RPM packages are built with OpenSSL 1.0.2, which is the current shipping package version. If you are running on an older version of CentOS 7 which uses OpenSSL 1.0.1, the installation will not succeed due to a dependency mismatch. Please resolve by either updating CentOS patches (security or whole release) to a point where OpenSSL 1.0.2 is used, or install OpenSSL 1.0.2 using "yum update openssl".
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • Enterprise & Community
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.0.24.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.0.24.
      • [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.0.24.
      • [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.0.23.
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure. Fixed in version 4.5.0.20.
      • [AER-6146] - (KVS) With 'debug-allocations' enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.0.19.
      • [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.0.17.
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.0.16.
      • [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.0.15.
      • [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.0.15.
      • [AER-6086] - (CDT) Single result operations returning boolean are not translated correctly to integer. Fixed in version 4.5.0.14.
      • [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.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-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-6035] - (BALANCE) For AP namespaces with `prefer-uniform-balance` true, there may be redundant migrations after shutting down a quiesced node. Fixed in version 4.5.2.1.
      • [AER-6041] - (XDR) Honor compression threshold configuration for http destination. Fixed in version 4.5.2.1.
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.0.24.
      • [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.0.23.
      • [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.0.22.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item 'report-authentication' true. Fixed in version 4.5.0.21.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.5.0.19.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.0.19.
      • [AER-6104] - (KVS) For ‘index-type flash’, index allocation errors may cause crash. Fixed in version 4.5.0.15.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart. Fixed in version 4.5.0.15.
      • [AER-6090] - (SECURITY) Batch sub-transactions' digests are not logged in the 'report-data-op' audit trail. Fixed in version 4.5.0.14.
      • [AER-6089] - (XDR) Race condition across multiple connections in libcurl may cause crash. Fixed in version 4.5.0.14.

    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.0.12
    Release Date: May 31, 2019
    • The CentOS 7 RPM packages are built with OpenSSL 1.0.2, which is the current shipping package version. If you are running on an older version of CentOS 7 which uses OpenSSL 1.0.1, the installation will not succeed due to a dependency mismatch. Please resolve by either updating CentOS patches (security or whole release) to a point where OpenSSL 1.0.2 is used, or install OpenSSL 1.0.2 using "yum update openssl".
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • Enterprise & Community
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.0.24.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.0.24.
      • [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.0.24.
      • [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.0.23.
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure. Fixed in version 4.5.0.20.
      • [AER-6146] - (KVS) With 'debug-allocations' enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.0.19.
      • [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.0.17.
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.0.16.
      • [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.0.15.
      • [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.0.15.
      • [AER-6086] - (CDT) Single result operations returning boolean are not translated correctly to integer. Fixed in version 4.5.0.14.
      • [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.0.14.
      • [AER-6077] - (BATCH) For 'storage-engine memory' namespaces, batch transactions unnecessarily return an error if record size exceeds 10MB. Fixed in version 4.5.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-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-6035] - (BALANCE) For AP namespaces with `prefer-uniform-balance` true, there may be redundant migrations after shutting down a quiesced node. Fixed in version 4.5.2.1.
      • [AER-6041] - (XDR) Honor compression threshold configuration for http destination. Fixed in version 4.5.2.1.
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.0.24.
      • [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.0.23.
      • [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.0.22.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item 'report-authentication' true. Fixed in version 4.5.0.21.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.5.0.19.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.0.19.
      • [AER-6104] - (KVS) For ‘index-type flash’, index allocation errors may cause crash. Fixed in version 4.5.0.15.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart. Fixed in version 4.5.0.15.
      • [AER-6090] - (SECURITY) Batch sub-transactions' digests are not logged in the 'report-data-op' audit trail. Fixed in version 4.5.0.14.
      • [AER-6089] - (XDR) Race condition across multiple connections in libcurl may cause crash. Fixed in version 4.5.0.14.
      • [AER-6072] - (XDR) Crash using multi-handles in curl library when using change notification. Fixed in version 4.5.0.13.
      • [AER-6075] - (XDR) Dynamically setting xdr context configuration items when configuration file has no xdr context causes crash. Fixed in version 4.5.0.13.

    Improvements

    • Enterprise & Community
      • [AER-6057] - (STORAGE) Added storage context configuration item `disable-odsync` to prevent setting O_DSYNC flag on storage devices.
      • [AER-6008] - (LOGGING) Eliminated excessive error logging to /tmp/aerospike-console when rolling log file.

    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.0.11
    Release Date: April 26, 2019
    • The CentOS 7 RPM packages are built with OpenSSL 1.0.2, which is the current shipping package version. If you are running on an older version of CentOS 7 which uses OpenSSL 1.0.1, the installation will not succeed due to a dependency mismatch. Please resolve by either updating CentOS patches (security or whole release) to a point where OpenSSL 1.0.2 is used, or install OpenSSL 1.0.2 using "yum update openssl".
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • Enterprise & Community
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.0.24.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.0.24.
      • [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.0.24.
      • [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.0.23.
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure. Fixed in version 4.5.0.20.
      • [AER-6146] - (KVS) With 'debug-allocations' enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.0.19.
      • [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.0.17.
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.0.16.
      • [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.0.15.
      • [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.0.15.
      • [AER-6086] - (CDT) Single result operations returning boolean are not translated correctly to integer. Fixed in version 4.5.0.14.
      • [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.0.14.
      • [AER-6077] - (BATCH) For 'storage-engine memory' namespaces, batch transactions unnecessarily return an error if record size exceeds 10MB. Fixed in version 4.5.0.13.
      • [AER-6068] - (LOGGING) Concurrent SIGHUPs to roll log files may race and double close a log sink file descriptor. Fixed in version 4.5.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-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-6035] - (BALANCE) For AP namespaces with `prefer-uniform-balance` true, there may be redundant migrations after shutting down a quiesced node. Fixed in version 4.5.2.1.
      • [AER-6041] - (XDR) Honor compression threshold configuration for http destination. Fixed in version 4.5.2.1.
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.0.24.
      • [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.0.23.
      • [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.0.22.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item 'report-authentication' true. Fixed in version 4.5.0.21.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.5.0.19.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.0.19.
      • [AER-6104] - (KVS) For ‘index-type flash’, index allocation errors may cause crash. Fixed in version 4.5.0.15.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart. Fixed in version 4.5.0.15.
      • [AER-6090] - (SECURITY) Batch sub-transactions' digests are not logged in the 'report-data-op' audit trail. Fixed in version 4.5.0.14.
      • [AER-6089] - (XDR) Race condition across multiple connections in libcurl may cause crash. Fixed in version 4.5.0.14.
      • [AER-6072] - (XDR) Crash using multi-handles in curl library when using change notification. Fixed in version 4.5.0.13.
      • [AER-6075] - (XDR) Dynamically setting xdr context configuration items when configuration file has no xdr context causes crash. Fixed in version 4.5.0.13.
      • [AER-6069] - (SECURITY) Minor memory leak during LDAP login process. Fixed in version 4.5.0.12.

    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.0.10
    Release Date: April 5, 2019
    • The CentOS 7 RPM packages are built with OpenSSL 1.0.2, which is the current shipping package version. If you are running on an older version of CentOS 7 which uses OpenSSL 1.0.1, the installation will not succeed due to a dependency mismatch. Please resolve by either updating CentOS patches (security or whole release) to a point where OpenSSL 1.0.2 is used, or install OpenSSL 1.0.2 using "yum update openssl".
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • Enterprise & Community
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.0.24.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.0.24.
      • [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.0.24.
      • [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.0.23.
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure. Fixed in version 4.5.0.20.
      • [AER-6146] - (KVS) With 'debug-allocations' enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.0.19.
      • [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.0.17.
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.0.16.
      • [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.0.15.
      • [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.0.15.
      • [AER-6086] - (CDT) Single result operations returning boolean are not translated correctly to integer. Fixed in version 4.5.0.14.
      • [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.0.14.
      • [AER-6077] - (BATCH) For 'storage-engine memory' namespaces, batch transactions unnecessarily return an error if record size exceeds 10MB. Fixed in version 4.5.0.13.
      • [AER-6068] - (LOGGING) Concurrent SIGHUPs to roll log files may race and double close a log sink file descriptor. Fixed in version 4.5.0.12.
      • [AER-6050] - (CDT) Extremely large unsorted lists or maps that require sorting within an operation may overflow the stack. Fixed in version 4.5.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-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-6035] - (BALANCE) For AP namespaces with `prefer-uniform-balance` true, there may be redundant migrations after shutting down a quiesced node. Fixed in version 4.5.2.1.
      • [AER-6041] - (XDR) Honor compression threshold configuration for http destination. Fixed in version 4.5.2.1.
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.0.24.
      • [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.0.23.
      • [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.0.22.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item 'report-authentication' true. Fixed in version 4.5.0.21.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.5.0.19.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.0.19.
      • [AER-6104] - (KVS) For ‘index-type flash’, index allocation errors may cause crash. Fixed in version 4.5.0.15.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart. Fixed in version 4.5.0.15.
      • [AER-6090] - (SECURITY) Batch sub-transactions' digests are not logged in the 'report-data-op' audit trail. Fixed in version 4.5.0.14.
      • [AER-6089] - (XDR) Race condition across multiple connections in libcurl may cause crash. Fixed in version 4.5.0.14.
      • [AER-6072] - (XDR) Crash using multi-handles in curl library when using change notification. Fixed in version 4.5.0.13.
      • [AER-6075] - (XDR) Dynamically setting xdr context configuration items when configuration file has no xdr context causes crash. Fixed in version 4.5.0.13.
      • [AER-6069] - (SECURITY) Minor memory leak during LDAP login process. Fixed in version 4.5.0.12.
      • [AER-6048] - (STORAGE) Namespaces that use compression and have different `write-block-size` values may overwrite memory. Fixed in version 4.5.0.11.
      • [AER-6049] - (XDR) May unnecessarily assert when a fresh socket goes bad while shipping to http destinations. Fixed in version 4.5.0.11.

    Improvements

    • Enterprise & Community
      • [AER-6042] - (KVS) When service context configuration item 'prole-extra-ttl' is set, delete all eligible expired non-master replicas during each nsup cycle.

  • 4.5.0.9
    Release Date: March 25, 2019
    • The CentOS 7 RPM packages are built with OpenSSL 1.0.2, which is the current shipping package version. If you are running on an older version of CentOS 7 which uses OpenSSL 1.0.1, the installation will not succeed due to a dependency mismatch. Please resolve by either updating CentOS patches (security or whole release) to a point where OpenSSL 1.0.2 is used, or install OpenSSL 1.0.2 using "yum update openssl".
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • Enterprise & Community
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.0.24.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.0.24.
      • [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.0.24.
      • [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.0.23.
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure. Fixed in version 4.5.0.20.
      • [AER-6146] - (KVS) With 'debug-allocations' enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.0.19.
      • [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.0.17.
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.0.16.
      • [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.0.15.
      • [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.0.15.
      • [AER-6086] - (CDT) Single result operations returning boolean are not translated correctly to integer. Fixed in version 4.5.0.14.
      • [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.0.14.
      • [AER-6077] - (BATCH) For 'storage-engine memory' namespaces, batch transactions unnecessarily return an error if record size exceeds 10MB. Fixed in version 4.5.0.13.
      • [AER-6068] - (LOGGING) Concurrent SIGHUPs to roll log files may race and double close a log sink file descriptor. Fixed in version 4.5.0.12.
      • [AER-6050] - (CDT) Extremely large unsorted lists or maps that require sorting within an operation may overflow the stack. Fixed in version 4.5.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-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-6035] - (BALANCE) For AP namespaces with `prefer-uniform-balance` true, there may be redundant migrations after shutting down a quiesced node. Fixed in version 4.5.2.1.
      • [AER-6041] - (XDR) Honor compression threshold configuration for http destination. Fixed in version 4.5.2.1.
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.0.24.
      • [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.0.23.
      • [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.0.22.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item 'report-authentication' true. Fixed in version 4.5.0.21.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.5.0.19.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.0.19.
      • [AER-6104] - (KVS) For ‘index-type flash’, index allocation errors may cause crash. Fixed in version 4.5.0.15.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart. Fixed in version 4.5.0.15.
      • [AER-6090] - (SECURITY) Batch sub-transactions' digests are not logged in the 'report-data-op' audit trail. Fixed in version 4.5.0.14.
      • [AER-6089] - (XDR) Race condition across multiple connections in libcurl may cause crash. Fixed in version 4.5.0.14.
      • [AER-6072] - (XDR) Crash using multi-handles in curl library when using change notification. Fixed in version 4.5.0.13.
      • [AER-6075] - (XDR) Dynamically setting xdr context configuration items when configuration file has no xdr context causes crash. Fixed in version 4.5.0.13.
      • [AER-6069] - (SECURITY) Minor memory leak during LDAP login process. Fixed in version 4.5.0.12.
      • [AER-6048] - (STORAGE) Namespaces that use compression and have different `write-block-size` values may overwrite memory. Fixed in version 4.5.0.11.
      • [AER-6049] - (XDR) May unnecessarily assert when a fresh socket goes bad while shipping to http destinations. Fixed in version 4.5.0.11.

    Improvements

    • Enterprise Only
      • [AER-6036] - (TLS) Do not block a TLS socket for a full second, for example when non-TLS connections are attempted.

    Bug Fixes

    • Enterprise & Community
      • [AER-6028] - (KVS) Proxied requests are failed by destination node before its first rebalance instead of returned to sender for retry.
      • [AER-6034] - (SCAN) Scans with a socket timeout of zero (meaning never time out) inadvertently time out.
      • [AER-6029] - (FABRIC) Load balance counter for send threads does not decrement correctly in certain rare circumstances.
    • Enterprise Only
      • [AER-6031] - (KVS) For 'strong-consistency' namespaces, replications may unnecessarily assert when they are concurrent with non-durable deletes.

  • 4.5.0.8
    Release Date: February 26, 2019
    • The CentOS 7 RPM packages are built with OpenSSL 1.0.2, which is the current shipping package version. If you are running on an older version of CentOS 7 which uses OpenSSL 1.0.1, the installation will not succeed due to a dependency mismatch. Please resolve by either updating CentOS patches (security or whole release) to a point where OpenSSL 1.0.2 is used, or install OpenSSL 1.0.2 using "yum update openssl".
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • Enterprise & Community
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.0.24.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.0.24.
      • [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.0.24.
      • [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.0.23.
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure. Fixed in version 4.5.0.20.
      • [AER-6146] - (KVS) With 'debug-allocations' enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.0.19.
      • [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.0.17.
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.0.16.
      • [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.0.15.
      • [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.0.15.
      • [AER-6086] - (CDT) Single result operations returning boolean are not translated correctly to integer. Fixed in version 4.5.0.14.
      • [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.0.14.
      • [AER-6077] - (BATCH) For 'storage-engine memory' namespaces, batch transactions unnecessarily return an error if record size exceeds 10MB. Fixed in version 4.5.0.13.
      • [AER-6068] - (LOGGING) Concurrent SIGHUPs to roll log files may race and double close a log sink file descriptor. Fixed in version 4.5.0.12.
      • [AER-6050] - (CDT) Extremely large unsorted lists or maps that require sorting within an operation may overflow the stack. Fixed in version 4.5.0.11.
      • [AER-6028] - (KVS) Proxied requests are failed by destination node before its first rebalance instead of returned to sender for retry. Fixed in version 4.5.0.9.
      • [AER-6034] - (SCAN) Scans with a socket timeout of zero (meaning never time out) inadvertently time out. Fixed in version 4.5.0.9.
      • [AER-6029] - (FABRIC) Load balance counter for send threads does not decrement correctly in certain rare circumstances. Fixed in version 4.5.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-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-6035] - (BALANCE) For AP namespaces with `prefer-uniform-balance` true, there may be redundant migrations after shutting down a quiesced node. Fixed in version 4.5.2.1.
      • [AER-6041] - (XDR) Honor compression threshold configuration for http destination. Fixed in version 4.5.2.1.
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.0.24.
      • [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.0.23.
      • [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.0.22.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item 'report-authentication' true. Fixed in version 4.5.0.21.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.5.0.19.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.0.19.
      • [AER-6104] - (KVS) For ‘index-type flash’, index allocation errors may cause crash. Fixed in version 4.5.0.15.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart. Fixed in version 4.5.0.15.
      • [AER-6090] - (SECURITY) Batch sub-transactions' digests are not logged in the 'report-data-op' audit trail. Fixed in version 4.5.0.14.
      • [AER-6089] - (XDR) Race condition across multiple connections in libcurl may cause crash. Fixed in version 4.5.0.14.
      • [AER-6072] - (XDR) Crash using multi-handles in curl library when using change notification. Fixed in version 4.5.0.13.
      • [AER-6075] - (XDR) Dynamically setting xdr context configuration items when configuration file has no xdr context causes crash. Fixed in version 4.5.0.13.
      • [AER-6069] - (SECURITY) Minor memory leak during LDAP login process. Fixed in version 4.5.0.12.
      • [AER-6048] - (STORAGE) Namespaces that use compression and have different `write-block-size` values may overwrite memory. Fixed in version 4.5.0.11.
      • [AER-6049] - (XDR) May unnecessarily assert when a fresh socket goes bad while shipping to http destinations. Fixed in version 4.5.0.11.
      • [AER-6031] - (KVS) For 'strong-consistency' namespaces, replications may unnecessarily assert when they are concurrent with non-durable deletes. Fixed in version 4.5.0.9.

    Bug Fixes

    • Enterprise Only
      • [AER-6022] - (KVS) May unnecessarily assert when fast restarting after a shutdown that left a ref-counted record (for reduce, e.g. scan) that was deleted.

  • 4.5.0.7
    Release Date: February 25, 2019
    • The CentOS 7 RPM packages are built with OpenSSL 1.0.2, which is the current shipping package version. If you are running on an older version of CentOS 7 which uses OpenSSL 1.0.1, the installation will not succeed due to a dependency mismatch. Please resolve by either updating CentOS patches (security or whole release) to a point where OpenSSL 1.0.2 is used, or install OpenSSL 1.0.2 using "yum update openssl".
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • Enterprise & Community
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.0.24.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.0.24.
      • [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.0.24.
      • [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.0.23.
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure. Fixed in version 4.5.0.20.
      • [AER-6146] - (KVS) With 'debug-allocations' enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.0.19.
      • [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.0.17.
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.0.16.
      • [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.0.15.
      • [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.0.15.
      • [AER-6086] - (CDT) Single result operations returning boolean are not translated correctly to integer. Fixed in version 4.5.0.14.
      • [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.0.14.
      • [AER-6077] - (BATCH) For 'storage-engine memory' namespaces, batch transactions unnecessarily return an error if record size exceeds 10MB. Fixed in version 4.5.0.13.
      • [AER-6068] - (LOGGING) Concurrent SIGHUPs to roll log files may race and double close a log sink file descriptor. Fixed in version 4.5.0.12.
      • [AER-6050] - (CDT) Extremely large unsorted lists or maps that require sorting within an operation may overflow the stack. Fixed in version 4.5.0.11.
      • [AER-6028] - (KVS) Proxied requests are failed by destination node before its first rebalance instead of returned to sender for retry. Fixed in version 4.5.0.9.
      • [AER-6034] - (SCAN) Scans with a socket timeout of zero (meaning never time out) inadvertently time out. Fixed in version 4.5.0.9.
      • [AER-6029] - (FABRIC) Load balance counter for send threads does not decrement correctly in certain rare circumstances. Fixed in version 4.5.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-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-6035] - (BALANCE) For AP namespaces with `prefer-uniform-balance` true, there may be redundant migrations after shutting down a quiesced node. Fixed in version 4.5.2.1.
      • [AER-6041] - (XDR) Honor compression threshold configuration for http destination. Fixed in version 4.5.2.1.
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.0.24.
      • [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.0.23.
      • [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.0.22.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item 'report-authentication' true. Fixed in version 4.5.0.21.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.5.0.19.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.0.19.
      • [AER-6104] - (KVS) For ‘index-type flash’, index allocation errors may cause crash. Fixed in version 4.5.0.15.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart. Fixed in version 4.5.0.15.
      • [AER-6090] - (SECURITY) Batch sub-transactions' digests are not logged in the 'report-data-op' audit trail. Fixed in version 4.5.0.14.
      • [AER-6089] - (XDR) Race condition across multiple connections in libcurl may cause crash. Fixed in version 4.5.0.14.
      • [AER-6072] - (XDR) Crash using multi-handles in curl library when using change notification. Fixed in version 4.5.0.13.
      • [AER-6075] - (XDR) Dynamically setting xdr context configuration items when configuration file has no xdr context causes crash. Fixed in version 4.5.0.13.
      • [AER-6069] - (SECURITY) Minor memory leak during LDAP login process. Fixed in version 4.5.0.12.
      • [AER-6048] - (STORAGE) Namespaces that use compression and have different `write-block-size` values may overwrite memory. Fixed in version 4.5.0.11.
      • [AER-6049] - (XDR) May unnecessarily assert when a fresh socket goes bad while shipping to http destinations. Fixed in version 4.5.0.11.
      • [AER-6031] - (KVS) For 'strong-consistency' namespaces, replications may unnecessarily assert when they are concurrent with non-durable deletes. Fixed in version 4.5.0.9.
      • [AER-6022] - (KVS) May unnecessarily assert when fast restarting after a shutdown that left a ref-counted record (for reduce, e.g. scan) that was deleted. Fixed in version 4.5.0.8.

    Improvements

    • Enterprise Only
      • [AER-6014] - (XDR) Ensure info commands that get XDR stats are non-blocking.

    Bug Fixes

    • Enterprise & Community
      • [AER-6020] - (NETWORK) The heartbeat context configuration item 'mesh-seed-address-port' is limited to 64 characters when using DNS.
    • Enterprise Only
      • [AER-5746] - (XDR) Time lag value can be incorrect. Supplements fix done in 4.1.0.1.

  • 4.5.0.6
    Release Date: February 20, 2019
    • The CentOS 7 RPM packages are built with OpenSSL 1.0.2, which is the current shipping package version. If you are running on an older version of CentOS 7 which uses OpenSSL 1.0.1, the installation will not succeed due to a dependency mismatch. Please resolve by either updating CentOS patches (security or whole release) to a point where OpenSSL 1.0.2 is used, or install OpenSSL 1.0.2 using "yum update openssl".
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • Enterprise & Community
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.0.24.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.0.24.
      • [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.0.24.
      • [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.0.23.
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure. Fixed in version 4.5.0.20.
      • [AER-6146] - (KVS) With 'debug-allocations' enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.0.19.
      • [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.0.17.
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.0.16.
      • [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.0.15.
      • [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.0.15.
      • [AER-6086] - (CDT) Single result operations returning boolean are not translated correctly to integer. Fixed in version 4.5.0.14.
      • [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.0.14.
      • [AER-6077] - (BATCH) For 'storage-engine memory' namespaces, batch transactions unnecessarily return an error if record size exceeds 10MB. Fixed in version 4.5.0.13.
      • [AER-6068] - (LOGGING) Concurrent SIGHUPs to roll log files may race and double close a log sink file descriptor. Fixed in version 4.5.0.12.
      • [AER-6050] - (CDT) Extremely large unsorted lists or maps that require sorting within an operation may overflow the stack. Fixed in version 4.5.0.11.
      • [AER-6028] - (KVS) Proxied requests are failed by destination node before its first rebalance instead of returned to sender for retry. Fixed in version 4.5.0.9.
      • [AER-6034] - (SCAN) Scans with a socket timeout of zero (meaning never time out) inadvertently time out. Fixed in version 4.5.0.9.
      • [AER-6029] - (FABRIC) Load balance counter for send threads does not decrement correctly in certain rare circumstances. Fixed in version 4.5.0.9.
      • [AER-6020] - (NETWORK) The heartbeat context configuration item 'mesh-seed-address-port' is limited to 64 characters when using DNS. Fixed in version 4.5.0.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-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-6035] - (BALANCE) For AP namespaces with `prefer-uniform-balance` true, there may be redundant migrations after shutting down a quiesced node. Fixed in version 4.5.2.1.
      • [AER-6041] - (XDR) Honor compression threshold configuration for http destination. Fixed in version 4.5.2.1.
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.0.24.
      • [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.0.23.
      • [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.0.22.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item 'report-authentication' true. Fixed in version 4.5.0.21.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.5.0.19.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.0.19.
      • [AER-6104] - (KVS) For ‘index-type flash’, index allocation errors may cause crash. Fixed in version 4.5.0.15.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart. Fixed in version 4.5.0.15.
      • [AER-6090] - (SECURITY) Batch sub-transactions' digests are not logged in the 'report-data-op' audit trail. Fixed in version 4.5.0.14.
      • [AER-6089] - (XDR) Race condition across multiple connections in libcurl may cause crash. Fixed in version 4.5.0.14.
      • [AER-6072] - (XDR) Crash using multi-handles in curl library when using change notification. Fixed in version 4.5.0.13.
      • [AER-6075] - (XDR) Dynamically setting xdr context configuration items when configuration file has no xdr context causes crash. Fixed in version 4.5.0.13.
      • [AER-6069] - (SECURITY) Minor memory leak during LDAP login process. Fixed in version 4.5.0.12.
      • [AER-6048] - (STORAGE) Namespaces that use compression and have different `write-block-size` values may overwrite memory. Fixed in version 4.5.0.11.
      • [AER-6049] - (XDR) May unnecessarily assert when a fresh socket goes bad while shipping to http destinations. Fixed in version 4.5.0.11.
      • [AER-6031] - (KVS) For 'strong-consistency' namespaces, replications may unnecessarily assert when they are concurrent with non-durable deletes. Fixed in version 4.5.0.9.
      • [AER-6022] - (KVS) May unnecessarily assert when fast restarting after a shutdown that left a ref-counted record (for reduce, e.g. scan) that was deleted. Fixed in version 4.5.0.8.

    Improvements

    Bug Fixes

    • Enterprise Only
      • [AER-6012] - (MIGRATION) For AP namespaces, there may be redundant migrations when quiescing multiple nodes at once and later shutting them down one by one.
      • [AER-6016] - (XDR) May miss records when a destination cluster is down, especially if there is only one destination.

  • 4.5.0.5
    Release Date: January 25, 2019
    • The CentOS 7 RPM packages are built with OpenSSL 1.0.2, which is the current shipping package version. If you are running on an older version of CentOS 7 which uses OpenSSL 1.0.1, the installation will not succeed due to a dependency mismatch. Please resolve by either updating CentOS patches (security or whole release) to a point where OpenSSL 1.0.2 is used, or install OpenSSL 1.0.2 using "yum update openssl".
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • Enterprise & Community
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.0.24.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.0.24.
      • [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.0.24.
      • [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.0.23.
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure. Fixed in version 4.5.0.20.
      • [AER-6146] - (KVS) With 'debug-allocations' enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.0.19.
      • [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.0.17.
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.0.16.
      • [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.0.15.
      • [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.0.15.
      • [AER-6086] - (CDT) Single result operations returning boolean are not translated correctly to integer. Fixed in version 4.5.0.14.
      • [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.0.14.
      • [AER-6077] - (BATCH) For 'storage-engine memory' namespaces, batch transactions unnecessarily return an error if record size exceeds 10MB. Fixed in version 4.5.0.13.
      • [AER-6068] - (LOGGING) Concurrent SIGHUPs to roll log files may race and double close a log sink file descriptor. Fixed in version 4.5.0.12.
      • [AER-6050] - (CDT) Extremely large unsorted lists or maps that require sorting within an operation may overflow the stack. Fixed in version 4.5.0.11.
      • [AER-6028] - (KVS) Proxied requests are failed by destination node before its first rebalance instead of returned to sender for retry. Fixed in version 4.5.0.9.
      • [AER-6034] - (SCAN) Scans with a socket timeout of zero (meaning never time out) inadvertently time out. Fixed in version 4.5.0.9.
      • [AER-6029] - (FABRIC) Load balance counter for send threads does not decrement correctly in certain rare circumstances. Fixed in version 4.5.0.9.
      • [AER-6020] - (NETWORK) The heartbeat context configuration item 'mesh-seed-address-port' is limited to 64 characters when using DNS. Fixed in version 4.5.0.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-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-6035] - (BALANCE) For AP namespaces with `prefer-uniform-balance` true, there may be redundant migrations after shutting down a quiesced node. Fixed in version 4.5.2.1.
      • [AER-6041] - (XDR) Honor compression threshold configuration for http destination. Fixed in version 4.5.2.1.
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.0.24.
      • [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.0.23.
      • [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.0.22.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item 'report-authentication' true. Fixed in version 4.5.0.21.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.5.0.19.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.0.19.
      • [AER-6104] - (KVS) For ‘index-type flash’, index allocation errors may cause crash. Fixed in version 4.5.0.15.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart. Fixed in version 4.5.0.15.
      • [AER-6090] - (SECURITY) Batch sub-transactions' digests are not logged in the 'report-data-op' audit trail. Fixed in version 4.5.0.14.
      • [AER-6089] - (XDR) Race condition across multiple connections in libcurl may cause crash. Fixed in version 4.5.0.14.
      • [AER-6072] - (XDR) Crash using multi-handles in curl library when using change notification. Fixed in version 4.5.0.13.
      • [AER-6075] - (XDR) Dynamically setting xdr context configuration items when configuration file has no xdr context causes crash. Fixed in version 4.5.0.13.
      • [AER-6069] - (SECURITY) Minor memory leak during LDAP login process. Fixed in version 4.5.0.12.
      • [AER-6048] - (STORAGE) Namespaces that use compression and have different `write-block-size` values may overwrite memory. Fixed in version 4.5.0.11.
      • [AER-6049] - (XDR) May unnecessarily assert when a fresh socket goes bad while shipping to http destinations. Fixed in version 4.5.0.11.
      • [AER-6031] - (KVS) For 'strong-consistency' namespaces, replications may unnecessarily assert when they are concurrent with non-durable deletes. Fixed in version 4.5.0.9.
      • [AER-6022] - (KVS) May unnecessarily assert when fast restarting after a shutdown that left a ref-counted record (for reduce, e.g. scan) that was deleted. Fixed in version 4.5.0.8.
      • [AER-6012] - (MIGRATION) For AP namespaces, there may be redundant migrations when quiescing multiple nodes at once and later shutting them down one by one. Fixed in version 4.5.0.6.
      • [AER-6016] - (XDR) May miss records when a destination cluster is down, especially if there is only one destination. Fixed in version 4.5.0.6.

    Bug Fixes

    • Enterprise & Community
      • [AER-6007] - (CDT) Map operations that add items and use both the DO_PARTIAL and NO_FAIL error policies may overwrite memory.
    • Enterprise Only
      • [AER-6006] - (KVS) For `strong-consistency` namespaces, re-replications may unnecessarily assert in very rare situations.
      • [AER-6002] - (BALANCE) For `strong-consistency` namespaces with `replication-factor` 1, removing node(s) from roster may cause crash.
      • [AER-5984] - (TLS) Small memory leak when logging a new TLS connection.

  • 4.5.0.4
    Release Date: January 10, 2019
    • The CentOS 7 RPM packages are built with OpenSSL 1.0.2, which is the current shipping package version. If you are running on an older version of CentOS 7 which uses OpenSSL 1.0.1, the installation will not succeed due to a dependency mismatch. Please resolve by either updating CentOS patches (security or whole release) to a point where OpenSSL 1.0.2 is used, or install OpenSSL 1.0.2 using "yum update openssl".
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • Enterprise & Community
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.0.24.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.0.24.
      • [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.0.24.
      • [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.0.23.
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure. Fixed in version 4.5.0.20.
      • [AER-6146] - (KVS) With 'debug-allocations' enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.0.19.
      • [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.0.17.
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.0.16.
      • [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.0.15.
      • [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.0.15.
      • [AER-6086] - (CDT) Single result operations returning boolean are not translated correctly to integer. Fixed in version 4.5.0.14.
      • [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.0.14.
      • [AER-6077] - (BATCH) For 'storage-engine memory' namespaces, batch transactions unnecessarily return an error if record size exceeds 10MB. Fixed in version 4.5.0.13.
      • [AER-6068] - (LOGGING) Concurrent SIGHUPs to roll log files may race and double close a log sink file descriptor. Fixed in version 4.5.0.12.
      • [AER-6050] - (CDT) Extremely large unsorted lists or maps that require sorting within an operation may overflow the stack. Fixed in version 4.5.0.11.
      • [AER-6028] - (KVS) Proxied requests are failed by destination node before its first rebalance instead of returned to sender for retry. Fixed in version 4.5.0.9.
      • [AER-6034] - (SCAN) Scans with a socket timeout of zero (meaning never time out) inadvertently time out. Fixed in version 4.5.0.9.
      • [AER-6029] - (FABRIC) Load balance counter for send threads does not decrement correctly in certain rare circumstances. Fixed in version 4.5.0.9.
      • [AER-6020] - (NETWORK) The heartbeat context configuration item 'mesh-seed-address-port' is limited to 64 characters when using DNS. Fixed in version 4.5.0.7.
      • [AER-6007] - (CDT) Map operations that add items and use both the DO_PARTIAL and NO_FAIL error policies may overwrite memory. Fixed in version 4.5.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-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-6035] - (BALANCE) For AP namespaces with `prefer-uniform-balance` true, there may be redundant migrations after shutting down a quiesced node. Fixed in version 4.5.2.1.
      • [AER-6041] - (XDR) Honor compression threshold configuration for http destination. Fixed in version 4.5.2.1.
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.0.24.
      • [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.0.23.
      • [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.0.22.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item 'report-authentication' true. Fixed in version 4.5.0.21.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.5.0.19.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.0.19.
      • [AER-6104] - (KVS) For ‘index-type flash’, index allocation errors may cause crash. Fixed in version 4.5.0.15.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart. Fixed in version 4.5.0.15.
      • [AER-6090] - (SECURITY) Batch sub-transactions' digests are not logged in the 'report-data-op' audit trail. Fixed in version 4.5.0.14.
      • [AER-6089] - (XDR) Race condition across multiple connections in libcurl may cause crash. Fixed in version 4.5.0.14.
      • [AER-6072] - (XDR) Crash using multi-handles in curl library when using change notification. Fixed in version 4.5.0.13.
      • [AER-6075] - (XDR) Dynamically setting xdr context configuration items when configuration file has no xdr context causes crash. Fixed in version 4.5.0.13.
      • [AER-6069] - (SECURITY) Minor memory leak during LDAP login process. Fixed in version 4.5.0.12.
      • [AER-6048] - (STORAGE) Namespaces that use compression and have different `write-block-size` values may overwrite memory. Fixed in version 4.5.0.11.
      • [AER-6049] - (XDR) May unnecessarily assert when a fresh socket goes bad while shipping to http destinations. Fixed in version 4.5.0.11.
      • [AER-6031] - (KVS) For 'strong-consistency' namespaces, replications may unnecessarily assert when they are concurrent with non-durable deletes. Fixed in version 4.5.0.9.
      • [AER-6022] - (KVS) May unnecessarily assert when fast restarting after a shutdown that left a ref-counted record (for reduce, e.g. scan) that was deleted. Fixed in version 4.5.0.8.
      • [AER-6012] - (MIGRATION) For AP namespaces, there may be redundant migrations when quiescing multiple nodes at once and later shutting them down one by one. Fixed in version 4.5.0.6.
      • [AER-6016] - (XDR) May miss records when a destination cluster is down, especially if there is only one destination. Fixed in version 4.5.0.6.
      • [AER-6006] - (KVS) For 'strong-consistency' namespaces, re-replications may unnecessarily assert in very rare situations. Fixed in version 4.5.0.5.
      • [AER-6002] - (BALANCE) For 'strong-consistency' namespaces with 'replication-factor' 1, removing node(s) from roster may cause crash. Fixed in version 4.5.0.5.
      • [AER-5984] - (TLS) Small memory leak when logging a new TLS connection. Fixed in version 4.5.0.5.

    Bug Fixes

    • Enterprise & Community
      • [AER-5996] - (KVS) Regression - service context configuration item `auto-pin` values `cpu` and `numa` do not pin service threads to CPUs.
      • [AER-5997] - (MIGRATION) Rare race condition causes `migrate_signals_remaining` stat to underflow.
    • Enterprise Only

  • 4.5.0.3
    Release Date: December 17, 2018
    • The CentOS 7 RPM packages are built with OpenSSL 1.0.2, which is the current shipping package version. If you are running on an older version of CentOS 7 which uses OpenSSL 1.0.1, the installation will not succeed due to a dependency mismatch. Please resolve by either updating CentOS patches (security or whole release) to a point where OpenSSL 1.0.2 is used, or install OpenSSL 1.0.2 using "yum update openssl".
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • Enterprise & Community
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.0.24.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.0.24.
      • [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.0.24.
      • [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.0.23.
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure. Fixed in version 4.5.0.20.
      • [AER-6146] - (KVS) With 'debug-allocations' enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.0.19.
      • [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.0.17.
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.0.16.
      • [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.0.15.
      • [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.0.15.
      • [AER-6086] - (CDT) Single result operations returning boolean are not translated correctly to integer. Fixed in version 4.5.0.14.
      • [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.0.14.
      • [AER-6077] - (BATCH) For 'storage-engine memory' namespaces, batch transactions unnecessarily return an error if record size exceeds 10MB. Fixed in version 4.5.0.13.
      • [AER-6068] - (LOGGING) Concurrent SIGHUPs to roll log files may race and double close a log sink file descriptor. Fixed in version 4.5.0.12.
      • [AER-6050] - (CDT) Extremely large unsorted lists or maps that require sorting within an operation may overflow the stack. Fixed in version 4.5.0.11.
      • [AER-6028] - (KVS) Proxied requests are failed by destination node before its first rebalance instead of returned to sender for retry. Fixed in version 4.5.0.9.
      • [AER-6034] - (SCAN) Scans with a socket timeout of zero (meaning never time out) inadvertently time out. Fixed in version 4.5.0.9.
      • [AER-6029] - (FABRIC) Load balance counter for send threads does not decrement correctly in certain rare circumstances. Fixed in version 4.5.0.9.
      • [AER-6020] - (NETWORK) The heartbeat context configuration item 'mesh-seed-address-port' is limited to 64 characters when using DNS. Fixed in version 4.5.0.7.
      • [AER-6007] - (CDT) Map operations that add items and use both the DO_PARTIAL and NO_FAIL error policies may overwrite memory. Fixed in version 4.5.0.5.
      • [AER-5996] - (KVS) Regression - service context configuration item `auto-pin` values `cpu` and `numa` do not pin service threads to CPUs. Fixed in version 4.5.0.4.
      • [AER-5997] - (MIGRATION) Rare race condition causes `migrate_signals_remaining` stat to underflow. Fixed in version 4.5.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-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-6035] - (BALANCE) For AP namespaces with `prefer-uniform-balance` true, there may be redundant migrations after shutting down a quiesced node. Fixed in version 4.5.2.1.
      • [AER-6041] - (XDR) Honor compression threshold configuration for http destination. Fixed in version 4.5.2.1.
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.0.24.
      • [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.0.23.
      • [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.0.22.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item 'report-authentication' true. Fixed in version 4.5.0.21.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.5.0.19.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.0.19.
      • [AER-6104] - (KVS) For ‘index-type flash’, index allocation errors may cause crash. Fixed in version 4.5.0.15.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart. Fixed in version 4.5.0.15.
      • [AER-6090] - (SECURITY) Batch sub-transactions' digests are not logged in the 'report-data-op' audit trail. Fixed in version 4.5.0.14.
      • [AER-6089] - (XDR) Race condition across multiple connections in libcurl may cause crash. Fixed in version 4.5.0.14.
      • [AER-6072] - (XDR) Crash using multi-handles in curl library when using change notification. Fixed in version 4.5.0.13.
      • [AER-6075] - (XDR) Dynamically setting xdr context configuration items when configuration file has no xdr context causes crash. Fixed in version 4.5.0.13.
      • [AER-6069] - (SECURITY) Minor memory leak during LDAP login process. Fixed in version 4.5.0.12.
      • [AER-6048] - (STORAGE) Namespaces that use compression and have different `write-block-size` values may overwrite memory. Fixed in version 4.5.0.11.
      • [AER-6049] - (XDR) May unnecessarily assert when a fresh socket goes bad while shipping to http destinations. Fixed in version 4.5.0.11.
      • [AER-6031] - (KVS) For 'strong-consistency' namespaces, replications may unnecessarily assert when they are concurrent with non-durable deletes. Fixed in version 4.5.0.9.
      • [AER-6022] - (KVS) May unnecessarily assert when fast restarting after a shutdown that left a ref-counted record (for reduce, e.g. scan) that was deleted. Fixed in version 4.5.0.8.
      • [AER-6012] - (MIGRATION) For AP namespaces, there may be redundant migrations when quiescing multiple nodes at once and later shutting them down one by one. Fixed in version 4.5.0.6.
      • [AER-6016] - (XDR) May miss records when a destination cluster is down, especially if there is only one destination. Fixed in version 4.5.0.6.
      • [AER-6006] - (KVS) For 'strong-consistency' namespaces, re-replications may unnecessarily assert in very rare situations. Fixed in version 4.5.0.5.
      • [AER-6002] - (BALANCE) For 'strong-consistency' namespaces with 'replication-factor' 1, removing node(s) from roster may cause crash. Fixed in version 4.5.0.5.
      • [AER-5984] - (TLS) Small memory leak when logging a new TLS connection. Fixed in version 4.5.0.5.
      • [AER-5995] - (BALANCE) For `strong-consistency` namespaces, if nodes are quiesced, `migrate-fill-delay` does not work properly. Fixed in version 4.5.0.4.

    Bug Fixes

    • Enterprise & Community
      • [AER-5985] - (STORAGE) Improper handling of dropped keys when replicating or migrating records.
    • Enterprise Only
      • [AER-5990] - (INFO) Service context configuration item `migrate-fill-delay` does not take time units when set dynamically.

  • 4.5.0.2
    Release Date: December 13, 2018
    • The CentOS 7 RPM packages are built with OpenSSL 1.0.2, which is the current shipping package version. If you are running on an older version of CentOS 7 which uses OpenSSL 1.0.1, the installation will not succeed due to a dependency mismatch. Please resolve by either updating CentOS patches (security or whole release) to a point where OpenSSL 1.0.2 is used, or install OpenSSL 1.0.2 using "yum update openssl".
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • Enterprise & Community
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.0.24.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.0.24.
      • [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.0.24.
      • [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.0.23.
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure. Fixed in version 4.5.0.20.
      • [AER-6146] - (KVS) With 'debug-allocations' enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.0.19.
      • [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.0.17.
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.0.16.
      • [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.0.15.
      • [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.0.15.
      • [AER-6086] - (CDT) Single result operations returning boolean are not translated correctly to integer. Fixed in version 4.5.0.14.
      • [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.0.14.
      • [AER-6077] - (BATCH) For 'storage-engine memory' namespaces, batch transactions unnecessarily return an error if record size exceeds 10MB. Fixed in version 4.5.0.13.
      • [AER-6068] - (LOGGING) Concurrent SIGHUPs to roll log files may race and double close a log sink file descriptor. Fixed in version 4.5.0.12.
      • [AER-6050] - (CDT) Extremely large unsorted lists or maps that require sorting within an operation may overflow the stack. Fixed in version 4.5.0.11.
      • [AER-6028] - (KVS) Proxied requests are failed by destination node before its first rebalance instead of returned to sender for retry. Fixed in version 4.5.0.9.
      • [AER-6034] - (SCAN) Scans with a socket timeout of zero (meaning never time out) inadvertently time out. Fixed in version 4.5.0.9.
      • [AER-6029] - (FABRIC) Load balance counter for send threads does not decrement correctly in certain rare circumstances. Fixed in version 4.5.0.9.
      • [AER-6020] - (NETWORK) The heartbeat context configuration item 'mesh-seed-address-port' is limited to 64 characters when using DNS. Fixed in version 4.5.0.7.
      • [AER-6007] - (CDT) Map operations that add items and use both the DO_PARTIAL and NO_FAIL error policies may overwrite memory. Fixed in version 4.5.0.5.
      • [AER-5996] - (KVS) Regression - service context configuration item `auto-pin` values `cpu` and `numa` do not pin service threads to CPUs. Fixed in version 4.5.0.4.
      • [AER-5997] - (MIGRATION) Rare race condition causes `migrate_signals_remaining` stat to underflow. Fixed in version 4.5.0.4.
      • [AER-5985] - (STORAGE) Improper handling of dropped keys when replicating or migrating records. Fixed in version 4.5.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-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-6035] - (BALANCE) For AP namespaces with `prefer-uniform-balance` true, there may be redundant migrations after shutting down a quiesced node. Fixed in version 4.5.2.1.
      • [AER-6041] - (XDR) Honor compression threshold configuration for http destination. Fixed in version 4.5.2.1.
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.0.24.
      • [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.0.23.
      • [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.0.22.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item 'report-authentication' true. Fixed in version 4.5.0.21.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.5.0.19.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.0.19.
      • [AER-6104] - (KVS) For ‘index-type flash’, index allocation errors may cause crash. Fixed in version 4.5.0.15.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart. Fixed in version 4.5.0.15.
      • [AER-6090] - (SECURITY) Batch sub-transactions' digests are not logged in the 'report-data-op' audit trail. Fixed in version 4.5.0.14.
      • [AER-6089] - (XDR) Race condition across multiple connections in libcurl may cause crash. Fixed in version 4.5.0.14.
      • [AER-6072] - (XDR) Crash using multi-handles in curl library when using change notification. Fixed in version 4.5.0.13.
      • [AER-6075] - (XDR) Dynamically setting xdr context configuration items when configuration file has no xdr context causes crash. Fixed in version 4.5.0.13.
      • [AER-6069] - (SECURITY) Minor memory leak during LDAP login process. Fixed in version 4.5.0.12.
      • [AER-6048] - (STORAGE) Namespaces that use compression and have different `write-block-size` values may overwrite memory. Fixed in version 4.5.0.11.
      • [AER-6049] - (XDR) May unnecessarily assert when a fresh socket goes bad while shipping to http destinations. Fixed in version 4.5.0.11.
      • [AER-6031] - (KVS) For 'strong-consistency' namespaces, replications may unnecessarily assert when they are concurrent with non-durable deletes. Fixed in version 4.5.0.9.
      • [AER-6022] - (KVS) May unnecessarily assert when fast restarting after a shutdown that left a ref-counted record (for reduce, e.g. scan) that was deleted. Fixed in version 4.5.0.8.
      • [AER-6012] - (MIGRATION) For AP namespaces, there may be redundant migrations when quiescing multiple nodes at once and later shutting them down one by one. Fixed in version 4.5.0.6.
      • [AER-6016] - (XDR) May miss records when a destination cluster is down, especially if there is only one destination. Fixed in version 4.5.0.6.
      • [AER-6006] - (KVS) For 'strong-consistency' namespaces, re-replications may unnecessarily assert in very rare situations. Fixed in version 4.5.0.5.
      • [AER-6002] - (BALANCE) For 'strong-consistency' namespaces with 'replication-factor' 1, removing node(s) from roster may cause crash. Fixed in version 4.5.0.5.
      • [AER-5984] - (TLS) Small memory leak when logging a new TLS connection. Fixed in version 4.5.0.5.
      • [AER-5995] - (BALANCE) For `strong-consistency` namespaces, if nodes are quiesced, `migrate-fill-delay` does not work properly. Fixed in version 4.5.0.4.
      • [AER-5990] - (INFO) Service context configuration item `migrate-fill-delay` does not take time units when set dynamically. Fixed in version 4.5.0.3.

    Bug Fixes

    • Enterprise Only
      • [AER-5982] - (XDR) Some records may get stuck in flight to http server when the load stops.

  • 4.5.0.1
    Release Date: December 12, 2018
    • The CentOS 7 RPM packages are built with OpenSSL 1.0.2, which is the current shipping package version. If you are running on an older version of CentOS 7 which uses OpenSSL 1.0.1, the installation will not succeed due to a dependency mismatch. Please resolve by either updating CentOS patches (security or whole release) to a point where OpenSSL 1.0.2 is used, or install OpenSSL 1.0.2 using "yum update openssl".
    • Index in Persistent Memory is an Enterprise Edition only feature requiring an additional license. Existing Aerospike Enterprise customers should contact their account representative for a trial license.
    • Support for Record Storage Compression (Enterprise Only).
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • Enterprise & Community
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.0.24.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.0.24.
      • [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.0.24.
      • [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.0.23.
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure. Fixed in version 4.5.0.20.
      • [AER-6146] - (KVS) With 'debug-allocations' enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.0.19.
      • [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.0.17.
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.0.16.
      • [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.0.15.
      • [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.0.15.
      • [AER-6086] - (CDT) Single result operations returning boolean are not translated correctly to integer. Fixed in version 4.5.0.14.
      • [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.0.14.
      • [AER-6077] - (BATCH) For 'storage-engine memory' namespaces, batch transactions unnecessarily return an error if record size exceeds 10MB. Fixed in version 4.5.0.13.
      • [AER-6068] - (LOGGING) Concurrent SIGHUPs to roll log files may race and double close a log sink file descriptor. Fixed in version 4.5.0.12.
      • [AER-6050] - (CDT) Extremely large unsorted lists or maps that require sorting within an operation may overflow the stack. Fixed in version 4.5.0.11.
      • [AER-6028] - (KVS) Proxied requests are failed by destination node before its first rebalance instead of returned to sender for retry. Fixed in version 4.5.0.9.
      • [AER-6034] - (SCAN) Scans with a socket timeout of zero (meaning never time out) inadvertently time out. Fixed in version 4.5.0.9.
      • [AER-6029] - (FABRIC) Load balance counter for send threads does not decrement correctly in certain rare circumstances. Fixed in version 4.5.0.9.
      • [AER-6020] - (NETWORK) The heartbeat context configuration item 'mesh-seed-address-port' is limited to 64 characters when using DNS. Fixed in version 4.5.0.7.
      • [AER-6007] - (CDT) Map operations that add items and use both the DO_PARTIAL and NO_FAIL error policies may overwrite memory. Fixed in version 4.5.0.5.
      • [AER-5996] - (KVS) Regression - service context configuration item `auto-pin` values `cpu` and `numa` do not pin service threads to CPUs. Fixed in version 4.5.0.4.
      • [AER-5997] - (MIGRATION) Rare race condition causes `migrate_signals_remaining` stat to underflow. Fixed in version 4.5.0.4.
      • [AER-5985] - (STORAGE) Improper handling of dropped keys when replicating or migrating records. Fixed in version 4.5.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-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-6035] - (BALANCE) For AP namespaces with `prefer-uniform-balance` true, there may be redundant migrations after shutting down a quiesced node. Fixed in version 4.5.2.1.
      • [AER-6041] - (XDR) Honor compression threshold configuration for http destination. Fixed in version 4.5.2.1.
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.0.24.
      • [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.0.23.
      • [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.0.22.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item 'report-authentication' true. Fixed in version 4.5.0.21.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.5.0.19.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.0.19.
      • [AER-6104] - (KVS) For ‘index-type flash’, index allocation errors may cause crash. Fixed in version 4.5.0.15.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart. Fixed in version 4.5.0.15.
      • [AER-6090] - (SECURITY) Batch sub-transactions' digests are not logged in the 'report-data-op' audit trail. Fixed in version 4.5.0.14.
      • [AER-6089] - (XDR) Race condition across multiple connections in libcurl may cause crash. Fixed in version 4.5.0.14.
      • [AER-6072] - (XDR) Crash using multi-handles in curl library when using change notification. Fixed in version 4.5.0.13.
      • [AER-6075] - (XDR) Dynamically setting xdr context configuration items when configuration file has no xdr context causes crash. Fixed in version 4.5.0.13.
      • [AER-6069] - (SECURITY) Minor memory leak during LDAP login process. Fixed in version 4.5.0.12.
      • [AER-6048] - (STORAGE) Namespaces that use compression and have different `write-block-size` values may overwrite memory. Fixed in version 4.5.0.11.
      • [AER-6049] - (XDR) May unnecessarily assert when a fresh socket goes bad while shipping to http destinations. Fixed in version 4.5.0.11.
      • [AER-6031] - (KVS) For 'strong-consistency' namespaces, replications may unnecessarily assert when they are concurrent with non-durable deletes. Fixed in version 4.5.0.9.
      • [AER-6022] - (KVS) May unnecessarily assert when fast restarting after a shutdown that left a ref-counted record (for reduce, e.g. scan) that was deleted. Fixed in version 4.5.0.8.
      • [AER-6012] - (MIGRATION) For AP namespaces, there may be redundant migrations when quiescing multiple nodes at once and later shutting them down one by one. Fixed in version 4.5.0.6.
      • [AER-6016] - (XDR) May miss records when a destination cluster is down, especially if there is only one destination. Fixed in version 4.5.0.6.
      • [AER-6006] - (KVS) For 'strong-consistency' namespaces, re-replications may unnecessarily assert in very rare situations. Fixed in version 4.5.0.5.
      • [AER-6002] - (BALANCE) For 'strong-consistency' namespaces with 'replication-factor' 1, removing node(s) from roster may cause crash. Fixed in version 4.5.0.5.
      • [AER-5984] - (TLS) Small memory leak when logging a new TLS connection. Fixed in version 4.5.0.5.
      • [AER-5995] - (BALANCE) For `strong-consistency` namespaces, if nodes are quiesced, `migrate-fill-delay` does not work properly. Fixed in version 4.5.0.4.
      • [AER-5990] - (INFO) Service context configuration item `migrate-fill-delay` does not take time units when set dynamically. Fixed in version 4.5.0.3.
      • [AER-5982] - (XDR) Some records may get stuck in flight to http server when the load stops. Fixed in version 4.5.0.2.

    New Features

    • Enterprise Only
      • [AER-5967] - (KVS) Added value `pmem` for namespace context configuration item `index-type`, to use persistent memory for primary index.
      • [AER-5968] - (STORAGE) Added storage context configuration items `compression` and `compression-level`, to enable data compression on storage devices.

    Improvements

    • Enterprise Only
      • [AER-5962] - (STORAGE) Added storage context configuration item `encryption` to specify the algorithm used by encryption at rest.

    Bug Fixes

    • Enterprise & Community
      • [AER-5966] - (CDT) Memory leak in non-recursive deeply nested list/map comparisons.
    • Enterprise Only
      • [AER-5971] - (XDR) The `dc-security-config-file` item is not shown in `get-dc-config` info.
      • [AER-5973] - (XDR) Dissociating a DC during active link down session does not abort link down thread.

  • 4.4.0.15
    Release Date: April 26, 2019
    • The CentOS 7 RPM packages are built with OpenSSL 1.0.2, which is the current shipping package version. If you are running on an older version of CentOS 7 which uses OpenSSL 1.0.1, the installation will not succeed due to a dependency mismatch. Please resolve by either updating CentOS patches (security or whole release) to a point where OpenSSL 1.0.2 is used, or install OpenSSL 1.0.2 using "yum update openssl".
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • Enterprise & Community
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.0.24.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.0.24.
      • [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.0.24.
      • [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.0.23.
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure. Fixed in version 4.5.0.20.
      • [AER-6146] - (KVS) With 'debug-allocations' enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.0.19.
      • [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.0.17.
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.0.16.
      • [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.0.15.
      • [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.0.15.
      • [AER-6086] - (CDT) Single result operations returning boolean are not translated correctly to integer. Fixed in version 4.5.0.14.
      • [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.0.14.
      • [AER-6077] - (BATCH) For 'storage-engine memory' namespaces, batch transactions unnecessarily return an error if record size exceeds 10MB. Fixed in version 4.5.0.13.
      • [AER-6068] - (LOGGING) Concurrent SIGHUPs to roll log files may race and double close a log sink file descriptor. Fixed in version 4.5.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-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-6035] - (BALANCE) For AP namespaces with `prefer-uniform-balance` true, there may be redundant migrations after shutting down a quiesced node. Fixed in version 4.5.2.1.
      • [AER-6041] - (XDR) Honor compression threshold configuration for http destination. Fixed in version 4.5.2.1.
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.0.24.
      • [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.0.22.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item 'report-authentication' true. Fixed in version 4.5.0.21.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.5.0.19.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.0.19.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart. Fixed in version 4.5.0.15.
      • [AER-6089] - (XDR) Race condition across multiple connections in libcurl may cause crash. Fixed in version 4.5.0.14.
      • [AER-6090] - (SECURITY) Batch sub-transactions' digests are not logged in the 'report-data-op' audit trail. Fixed in version 4.5.0.14.
      • [AER-6072] - (XDR) Crash using multi-handles in curl library when using change notification. Fixed in version 4.5.0.13.
      • [AER-6075] - (XDR) Dynamically setting xdr context configuration items when configuration file has no xdr context causes crash. Fixed in version 4.5.0.13.
      • [AER-6069] - (SECURITY) Minor memory leak during LDAP login process. Fixed in version 4.5.0.12.

    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-6049] - (XDR) May unnecessarily assert when a fresh socket goes bad while shipping to http destinations.

  • 4.4.0.14
    Release Date: March 25, 2019
    • The CentOS 7 RPM packages are built with OpenSSL 1.0.2, which is the current shipping package version. If you are running on an older version of CentOS 7 which uses OpenSSL 1.0.1, the installation will not succeed due to a dependency mismatch. Please resolve by either updating CentOS patches (security or whole release) to a point where OpenSSL 1.0.2 is used, or install OpenSSL 1.0.2 using "yum update openssl".
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • Enterprise & Community
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.0.24.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.0.24.
      • [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.0.24.
      • [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.0.23.
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure. Fixed in version 4.5.0.20.
      • [AER-6146] - (KVS) With 'debug-allocations' enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.0.19.
      • [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.0.17
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.0.16.
      • [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.0.15.
      • [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.0.15.
      • [AER-6086] - (CDT) Single result operations returning boolean are not translated correctly to integer. Fixed in version 4.5.0.14.
      • [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.0.14.
      • [AER-6077] - (BATCH) For 'storage-engine memory' namespaces, batch transactions unnecessarily return an error if record size exceeds 10MB. Fixed in version 4.5.0.13.
      • [AER-6068] - (LOGGING) Concurrent SIGHUPs to roll log files may race and double close a log sink file descriptor. Fixed in version 4.5.0.12.
      • [AER-6050] - (CDT) Extremely large unsorted lists or maps that require sorting within an operation may overflow the stack. Fixed in version 4.4.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-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-6035] - (BALANCE) For AP namespaces with `prefer-uniform-balance` true, there may be redundant migrations after shutting down a quiesced node. Fixed in version 4.5.2.1.
      • [AER-6041] - (XDR) Honor compression threshold configuration for http destination. Fixed in version 4.5.2.1.
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.0.24.
      • [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.0.22.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item 'report-authentication' true. Fixed in version 4.5.0.21.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.5.0.19.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.0.19.
      • [AER-6089] - (XDR) Race condition across multiple connections in libcurl may cause crash. Fixed in version 4.5.0.14.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart. Fixed in version 4.5.0.15.
      • [AER-6090] - (SECURITY) Batch sub-transactions' digests are not logged in the 'report-data-op' audit trail. Fixed in version 4.5.0.14.
      • [AER-6072] - (XDR) Crash using multi-handles in curl library when using change notification. Fixed in version 4.5.0.13.
      • [AER-6075] - (XDR) Dynamically setting xdr context configuration items when configuration file has no xdr context causes crash. Fixed in version 4.5.0.13.
      • [AER-6069] - (SECURITY) Minor memory leak during LDAP login process. Fixed in version 4.5.0.12.
      • [AER-6049] - (XDR) May unnecessarily assert when a fresh socket goes bad while shipping to http destinations. Fixed in version 4.4.0.15.

    Improvements

    • Enterprise Only
      • [AER-6036] - (TLS) Do not block a TLS socket for a full second, for example when non-TLS connections are attempted.

    Bug Fixes

    • Enterprise & Community
      • [AER-6028] - (KVS) Proxied requests are failed by destination node before its first rebalance instead of returned to sender for retry.
      • [AER-6034] - (SCAN) Scans with a socket timeout of zero (meaning never time out) inadvertently time out.
      • [AER-6029] - (FABRIC) Load balance counter for send threads does not decrement correctly in certain rare circumstances.
    • Enterprise Only
      • [AER-6031] - (KVS) For 'strong-consistency' namespaces, replications may unnecessarily assert when they are concurrent with non-durable deletes.

  • 4.4.0.13
    Release Date: February 26, 2019
    • The CentOS 7 RPM packages are built with OpenSSL 1.0.2, which is the current shipping package version. If you are running on an older version of CentOS 7 which uses OpenSSL 1.0.1, the installation will not succeed due to a dependency mismatch. Please resolve by either updating CentOS patches (security or whole release) to a point where OpenSSL 1.0.2 is used, or install OpenSSL 1.0.2 using "yum update openssl".
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • Enterprise & Community
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.0.24.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.0.24.
      • [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.0.24.
      • [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.0.23.
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure. Fixed in version 4.5.0.20.
      • [AER-6146] - (KVS) With 'debug-allocations' enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.0.19.
      • [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.0.17
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.0.16.
      • [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.0.15.
      • [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.0.15.
      • [AER-6086] - (CDT) Single result operations returning boolean are not translated correctly to integer. Fixed in version 4.5.0.14.
      • [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.0.14.
      • [AER-6077] - (BATCH) For 'storage-engine memory' namespaces, batch transactions unnecessarily return an error if record size exceeds 10MB. Fixed in version 4.5.0.13.
      • [AER-6068] - (LOGGING) Concurrent SIGHUPs to roll log files may race and double close a log sink file descriptor. Fixed in version 4.5.0.12.
      • [AER-6050] - (CDT) Extremely large unsorted lists or maps that require sorting within an operation may overflow the stack. Fixed in version 4.4.0.15.
      • [AER-6028] - (KVS) Proxied requests are failed by destination node before its first rebalance instead of returned to sender for retry. Fixed in version 4.4.0.14
      • [AER-6034] - (SCAN) Scans with a socket timeout of zero (meaning never time out) inadvertently time out. Fixed in version 4.4.0.14.
      • [AER-6029] - (FABRIC) Load balance counter for send threads does not decrement correctly in certain rare circumstances. Fixed in version 4.4.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-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-6035] - (BALANCE) For AP namespaces with `prefer-uniform-balance` true, there may be redundant migrations after shutting down a quiesced node. Fixed in version 4.5.2.1.
      • [AER-6041] - (XDR) Honor compression threshold configuration for http destination. Fixed in version 4.5.2.1.
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.0.24.
      • [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.0.22.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item 'report-authentication' true. Fixed in version 4.5.0.21.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.5.0.19.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.0.19.
      • [AER-6089] - (XDR) Race condition across multiple connections in libcurl may cause crash. Fixed in version 4.5.0.14.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart. Fixed in version 4.5.0.15.
      • [AER-6090] - (SECURITY) Batch sub-transactions' digests are not logged in the 'report-data-op' audit trail. Fixed in version 4.5.0.14.
      • [AER-6072] - (XDR) Crash using multi-handles in curl library when using change notification. Fixed in version 4.5.0.13.
      • [AER-6075] - (XDR) Dynamically setting xdr context configuration items when configuration file has no xdr context causes crash. Fixed in version 4.5.0.13.
      • [AER-6069] - (SECURITY) Minor memory leak during LDAP login process. Fixed in version 4.5.0.12.
      • [AER-6049] - (XDR) May unnecessarily assert when a fresh socket goes bad while shipping to http destinations. Fixed in version 4.4.0.15.
      • [AER-6031] - (KVS) For 'strong-consistency' namespaces, replications may unnecessarily assert when they are concurrent with non-durable deletes. Fixed in version 4.4.0.14.

    Improvements

    • Enterprise Only
      • [AER-6014] - (XDR) Ensure info commands that get XDR stats are non-blocking.

    Bug Fixes

    • Enterprise & Community
      • [AER-6020] - (NETWORK) The heartbeat context configuration item 'mesh-seed-address-port' is limited to 64 characters when using DNS.
    • Enterprise Only
      • [AER-6022] - (KVS) May unnecessarily assert when fast restarting after a shutdown that left a ref-counted record (for reduce, e.g. scan) that was deleted.
      • [AER-5746] - (XDR) Time lag value can be incorrect. Supplements fix done in 4.1.0.1.

  • 4.4.0.11
    Release Date: February 20, 2019
    • The CentOS 7 RPM packages are built with OpenSSL 1.0.2, which is the current shipping package version. If you are running on an older version of CentOS 7 which uses OpenSSL 1.0.1, the installation will not succeed due to a dependency mismatch. Please resolve by either updating CentOS patches (security or whole release) to a point where OpenSSL 1.0.2 is used, or install OpenSSL 1.0.2 using "yum update openssl".
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • Enterprise & Community
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.0.24.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.0.24.
      • [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.0.24.
      • [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.0.23.
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure. Fixed in version 4.5.0.20.
      • [AER-6146] - (KVS) With 'debug-allocations' enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.0.19.
      • [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.0.17
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.0.16.
      • [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.0.15.
      • [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.0.15.
      • [AER-6086] - (CDT) Single result operations returning boolean are not translated correctly to integer. Fixed in version 4.5.0.14.
      • [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.0.14.
      • [AER-6077] - (BATCH) For 'storage-engine memory' namespaces, batch transactions unnecessarily return an error if record size exceeds 10MB. Fixed in version 4.5.0.13.
      • [AER-6068] - (LOGGING) Concurrent SIGHUPs to roll log files may race and double close a log sink file descriptor. Fixed in version 4.5.0.12.
      • [AER-6050] - (CDT) Extremely large unsorted lists or maps that require sorting within an operation may overflow the stack. Fixed in version 4.4.0.15.
      • [AER-6028] - (KVS) Proxied requests are failed by destination node before its first rebalance instead of returned to sender for retry. Fixed in version 4.4.0.14
      • [AER-6034] - (SCAN) Scans with a socket timeout of zero (meaning never time out) inadvertently time out. Fixed in version 4.4.0.14.
      • [AER-6029] - (FABRIC) Load balance counter for send threads does not decrement correctly in certain rare circumstances. Fixed in version 4.4.0.14.
      • [AER-6020] - (NETWORK) The heartbeat context configuration item 'mesh-seed-address-port' is limited to 64 characters when using DNS. Fixed in version 4.4.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-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-6035] - (BALANCE) For AP namespaces with `prefer-uniform-balance` true, there may be redundant migrations after shutting down a quiesced node. Fixed in version 4.5.2.1.
      • [AER-6041] - (XDR) Honor compression threshold configuration for http destination. Fixed in version 4.5.2.1.
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.0.24.
      • [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.0.22.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item 'report-authentication' true. Fixed in version 4.5.0.21.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.5.0.19.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.0.19.
      • [AER-6089] - (XDR) Race condition across multiple connections in libcurl may cause crash. Fixed in version 4.5.0.14.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart. Fixed in version 4.5.0.15.
      • [AER-6090] - (SECURITY) Batch sub-transactions' digests are not logged in the 'report-data-op' audit trail. Fixed in version 4.5.0.14.
      • [AER-6072] - (XDR) Crash using multi-handles in curl library when using change notification. Fixed in version 4.5.0.13.
      • [AER-6075] - (XDR) Dynamically setting xdr context configuration items when configuration file has no xdr context causes crash. Fixed in version 4.5.0.13.
      • [AER-6069] - (SECURITY) Minor memory leak during LDAP login process. Fixed in version 4.5.0.12.
      • [AER-6049] - (XDR) May unnecessarily assert when a fresh socket goes bad while shipping to http destinations. Fixed in version 4.4.0.15.
      • [AER-6031] - (KVS) For 'strong-consistency' namespaces, replications may unnecessarily assert when they are concurrent with non-durable deletes. Fixed in version 4.4.0.14.
      • [AER-6022] - (KVS) May unnecessarily assert when fast restarting after a shutdown that left a ref-counted record (for reduce, e.g. scan) that was deleted. Fixed in version 4.4.0.13.

    Improvements

    Bug Fixes

    • Enterprise Only
      • [AER-6012] - (MIGRATION) For AP namespaces, there may be redundant migrations when quiescing multiple nodes at once and later shutting them down one by one.
      • [AER-6016] - (XDR) May miss records when a destination cluster is down, especially if there is only one destination.

  • 4.4.0.10
    Release Date: January 25, 2019
    • The CentOS 7 RPM packages are built with OpenSSL 1.0.2, which is the current shipping package version. If you are running on an older version of CentOS 7 which uses OpenSSL 1.0.1, the installation will not succeed due to a dependency mismatch. Please resolve by either updating CentOS patches (security or whole release) to a point where OpenSSL 1.0.2 is used, or install OpenSSL 1.0.2 using "yum update openssl".
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • Enterprise & Community
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.0.24.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.0.24.
      • [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.0.24.
      • [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.0.23.
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure. Fixed in version 4.5.0.20.
      • [AER-6146] - (KVS) With 'debug-allocations' enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.0.19.
      • [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.0.17
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.0.16.
      • [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.0.15.
      • [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.0.15.
      • [AER-6086] - (CDT) Single result operations returning boolean are not translated correctly to integer. Fixed in version 4.5.0.14.
      • [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.0.14.
      • [AER-6077] - (BATCH) For 'storage-engine memory' namespaces, batch transactions unnecessarily return an error if record size exceeds 10MB. Fixed in version 4.5.0.13.
      • [AER-6068] - (LOGGING) Concurrent SIGHUPs to roll log files may race and double close a log sink file descriptor. Fixed in version 4.5.0.12.
      • [AER-6050] - (CDT) Extremely large unsorted lists or maps that require sorting within an operation may overflow the stack. Fixed in version 4.4.0.15.
      • [AER-6028] - (KVS) Proxied requests are failed by destination node before its first rebalance instead of returned to sender for retry. Fixed in version 4.4.0.14
      • [AER-6034] - (SCAN) Scans with a socket timeout of zero (meaning never time out) inadvertently time out. Fixed in version 4.4.0.14.
      • [AER-6029] - (FABRIC) Load balance counter for send threads does not decrement correctly in certain rare circumstances. Fixed in version 4.4.0.14.
      • [AER-6020] - (NETWORK) The heartbeat context configuration item 'mesh-seed-address-port' is limited to 64 characters when using DNS. Fixed in version 4.4.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-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-6035] - (BALANCE) For AP namespaces with `prefer-uniform-balance` true, there may be redundant migrations after shutting down a quiesced node. Fixed in version 4.5.2.1.
      • [AER-6041] - (XDR) Honor compression threshold configuration for http destination. Fixed in version 4.5.2.1.
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.0.24.
      • [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.0.22.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item 'report-authentication' true. Fixed in version 4.5.0.21.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.5.0.19.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.0.19.
      • [AER-6089] - (XDR) Race condition across multiple connections in libcurl may cause crash. Fixed in version 4.5.0.14
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart. Fixed in version 4.5.0.15.
      • [AER-6090] - (SECURITY) Batch sub-transactions' digests are not logged in the 'report-data-op' audit trail. Fixed in version 4.5.0.14.
      • [AER-6072] - (XDR) Crash using multi-handles in curl library when using change notification. Fixed in version 4.5.0.13.
      • [AER-6075] - (XDR) Dynamically setting xdr context configuration items when configuration file has no xdr context causes crash. Fixed in version 4.5.0.13.
      • [AER-6069] - (SECURITY) Minor memory leak during LDAP login process. Fixed in version 4.5.0.12.
      • [AER-6049] - (XDR) May unnecessarily assert when a fresh socket goes bad while shipping to http destinations. Fixed in version 4.4.0.15.
      • [AER-6031] - (KVS) For 'strong-consistency' namespaces, replications may unnecessarily assert when they are concurrent with non-durable deletes. Fixed in version 4.4.0.14.
      • [AER-6022] - (KVS) May unnecessarily assert when fast restarting after a shutdown that left a ref-counted record (for reduce, e.g. scan) that was deleted. Fixed in version 4.4.0.13.
      • [AER-6012] - (MIGRATION) For AP namespaces, there may be redundant migrations when quiescing multiple nodes at once and later shutting them down one by one. Fixed in version 4.4.0.11.
      • [AER-6016] - (XDR) May miss records when a destination cluster is down, especially if there is only one destination. Fixed in version 4.4.0.11.

    Bug Fixes

    • Enterprise & Community
      • [AER-6007] - (CDT) Map operations that add items and use both the DO_PARTIAL and NO_FAIL error policies may overwrite memory.
    • Enterprise Only
      • [AER-6006] - (KVS) For `strong-consistency` namespaces, re-replications may unnecessarily assert in very rare situations.
      • [AER-6002] - (BALANCE) For `strong-consistency` namespaces with `replication-factor` 1, removing node(s) from roster may cause crash.
      • [AER-5984] - (TLS) Small memory leak when logging a new TLS connection.

  • 4.4.0.9
    Release Date: January 10, 2019
    • The CentOS 7 RPM packages are built with OpenSSL 1.0.2, which is the current shipping package version. If you are running on an older version of CentOS 7 which uses OpenSSL 1.0.1, the installation will not succeed due to a dependency mismatch. Please resolve by either updating CentOS patches (security or whole release) to a point where OpenSSL 1.0.2 is used, or install OpenSSL 1.0.2 using "yum update openssl".
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • Enterprise & Community
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.0.24.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.0.24.
      • [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.0.24.
      • [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.0.23.
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure. Fixed in version 4.5.0.20.
      • [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.0.17
      • [AER-6146] - (KVS) With 'debug-allocations' enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.0.19.
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.0.16.
      • [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.0.15.
      • [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.0.15.
      • [AER-6086] - (CDT) Single result operations returning boolean are not translated correctly to integer. Fixed in version 4.5.0.14.
      • [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.0.14.
      • [AER-6077] - (BATCH) For 'storage-engine memory' namespaces, batch transactions unnecessarily return an error if record size exceeds 10MB. Fixed in version 4.5.0.13.
      • [AER-6068] - (LOGGING) Concurrent SIGHUPs to roll log files may race and double close a log sink file descriptor. Fixed in version 4.5.0.12.
      • [AER-6050] - (CDT) Extremely large unsorted lists or maps that require sorting within an operation may overflow the stack. Fixed in version 4.4.0.15.
      • [AER-6028] - (KVS) Proxied requests are failed by destination node before its first rebalance instead of returned to sender for retry. Fixed in version 4.4.0.14
      • [AER-6034] - (SCAN) Scans with a socket timeout of zero (meaning never time out) inadvertently time out. Fixed in version 4.4.0.14.
      • [AER-6029] - (FABRIC) Load balance counter for send threads does not decrement correctly in certain rare circumstances. Fixed in version 4.4.0.14.
      • [AER-6020] - (NETWORK) The heartbeat context configuration item 'mesh-seed-address-port' is limited to 64 characters when using DNS. Fixed in version 4.4.0.13.
      • [AER-6007] - (CDT) Map operations that add items and use both the DO_PARTIAL and NO_FAIL error policies may overwrite memory. Fixed in version 4.4.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-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-6035] - (BALANCE) For AP namespaces with `prefer-uniform-balance` true, there may be redundant migrations after shutting down a quiesced node. Fixed in version 4.5.2.1.
      • [AER-6041] - (XDR) Honor compression threshold configuration for http destination. Fixed in version 4.5.2.1.
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.0.24.
      • [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.0.22.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item 'report-authentication' true. Fixed in version 4.5.0.21.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.5.0.19.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.0.19.
      • [AER-6089] - (XDR) Race condition across multiple connections in libcurl may cause crash. Fixed in version 4.5.0.14.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart. Fixed in version 4.5.0.15.
      • [AER-6090] - (SECURITY) Batch sub-transactions' digests are not logged in the 'report-data-op' audit trail. Fixed in version 4.5.0.14.
      • [AER-6072] - (XDR) Crash using multi-handles in curl library when using change notification. Fixed in version 4.5.0.13.
      • [AER-6075] - (XDR) Dynamically setting xdr context configuration items when configuration file has no xdr context causes crash. Fixed in version 4.5.0.13.
      • [AER-6069] - (SECURITY) Minor memory leak during LDAP login process. Fixed in version 4.5.0.12.
      • [AER-6049] - (XDR) May unnecessarily assert when a fresh socket goes bad while shipping to http destinations. Fixed in version 4.4.0.15.
      • [AER-6031] - (KVS) For 'strong-consistency' namespaces, replications may unnecessarily assert when they are concurrent with non-durable deletes. Fixed in version 4.4.0.14.
      • [AER-6022] - (KVS) May unnecessarily assert when fast restarting after a shutdown that left a ref-counted record (for reduce, e.g. scan) that was deleted. Fixed in version 4.4.0.13.
      • [AER-6012] - (MIGRATION) For AP namespaces, there may be redundant migrations when quiescing multiple nodes at once and later shutting them down one by one. Fixed in version 4.4.0.11.
      • [AER-6016] - (XDR) May miss records when a destination cluster is down, especially if there is only one destination. Fixed in version 4.4.0.11.
      • [AER-6006] - (KVS) For 'strong-consistency' namespaces, re-replications may unnecessarily assert in very rare situations. Fixed in version 4.4.0.10.
      • [AER-6002] - (BALANCE) For 'strong-consistency' namespaces with 'replication-factor' 1, removing node(s) from roster may cause crash. Fixed in version 4.4.0.10.
      • [AER-5984] - (TLS) Small memory leak when logging a new TLS connection. Fixed in version 4.4.0.10.

    Bug Fixes

    • Enterprise & Community
      • [AER-5996] - (KVS) Regression - service context configuration item `auto-pin` values `cpu` and `numa` do not pin service threads to CPUs.
      • [AER-5997] - (MIGRATION) Rare race condition causes `migrate_signals_remaining` stat to underflow.
    • Enterprise Only

  • 4.4.0.8
    Release Date: December 17, 2018
    • The CentOS 7 RPM packages are built with OpenSSL 1.0.2, which is the current shipping package version. If you are running on an older version of CentOS 7 which uses OpenSSL 1.0.1, the installation will not succeed due to a dependency mismatch. Please resolve by either updating CentOS patches (security or whole release) to a point where OpenSSL 1.0.2 is used, or install OpenSSL 1.0.2 using "yum update openssl".
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • Enterprise & Community
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.0.24.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.0.24.
      • [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.0.24.
      • [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.0.23.
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure. Fixed in version 4.5.0.20.
      • [AER-6146] - (KVS) With 'debug-allocations' enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.0.19.
      • [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.0.17
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.0.16.
      • [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.0.15.
      • [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.0.15.
      • [AER-6086] - (CDT) Single result operations returning boolean are not translated correctly to integer. Fixed in version 4.5.0.14.
      • [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.0.14.
      • [AER-6077] - (BATCH) For 'storage-engine memory' namespaces, batch transactions unnecessarily return an error if record size exceeds 10MB. Fixed in version 4.5.0.13.
      • [AER-6068] - (LOGGING) Concurrent SIGHUPs to roll log files may race and double close a log sink file descriptor. Fixed in version 4.5.0.12.
      • [AER-6050] - (CDT) Extremely large unsorted lists or maps that require sorting within an operation may overflow the stack. Fixed in version 4.4.0.15.
      • [AER-6028] - (KVS) Proxied requests are failed by destination node before its first rebalance instead of returned to sender for retry. Fixed in version 4.4.0.14
      • [AER-6034] - (SCAN) Scans with a socket timeout of zero (meaning never time out) inadvertently time out. Fixed in version 4.4.0.14.
      • [AER-6029] - (FABRIC) Load balance counter for send threads does not decrement correctly in certain rare circumstances. Fixed in version 4.4.0.14.
      • [AER-6020] - (NETWORK) The heartbeat context configuration item 'mesh-seed-address-port' is limited to 64 characters when using DNS. Fixed in version 4.4.0.13.
      • [AER-6007] - (CDT) Map operations that add items and use both the DO_PARTIAL and NO_FAIL error policies may overwrite memory. Fixed in version 4.4.0.10.
      • [AER-5996] - (KVS) Regression - service context configuration item `auto-pin` values `cpu` and `numa` do not pin service threads to CPUs. Fixed in version 4.4.0.9.
      • [AER-5997] - (MIGRATION) Rare race condition causes `migrate_signals_remaining` stat to underflow. Fixed in version 4.4.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-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-6035] - (BALANCE) For AP namespaces with `prefer-uniform-balance` true, there may be redundant migrations after shutting down a quiesced node. Fixed in version 4.5.2.1.
      • [AER-6041] - (XDR) Honor compression threshold configuration for http destination. Fixed in version 4.5.2.1.
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.0.24.
      • [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.0.22.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item 'report-authentication' true. Fixed in version 4.5.0.21.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.5.0.19.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.0.19.
      • [AER-6089] - (XDR) Race condition across multiple connections in libcurl may cause crash. Fixed in version 4.5.0.14.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart. Fixed in version 4.5.0.15.
      • [AER-6090] - (SECURITY) Batch sub-transactions' digests are not logged in the 'report-data-op' audit trail. Fixed in version 4.5.0.14.
      • [AER-6072] - (XDR) Crash using multi-handles in curl library when using change notification. Fixed in version 4.5.0.13.
      • [AER-6075] - (XDR) Dynamically setting xdr context configuration items when configuration file has no xdr context causes crash. Fixed in version 4.5.0.13.
      • [AER-6069] - (SECURITY) Minor memory leak during LDAP login process. Fixed in version 4.5.0.12.
      • [AER-6049] - (XDR) May unnecessarily assert when a fresh socket goes bad while shipping to http destinations. Fixed in version 4.4.0.15.
      • [AER-6031] - (KVS) For 'strong-consistency' namespaces, replications may unnecessarily assert when they are concurrent with non-durable deletes. Fixed in version 4.4.0.14.
      • [AER-6022] - (KVS) May unnecessarily assert when fast restarting after a shutdown that left a ref-counted record (for reduce, e.g. scan) that was deleted. Fixed in version 4.4.0.13.
      • [AER-6012] - (MIGRATION) For AP namespaces, there may be redundant migrations when quiescing multiple nodes at once and later shutting them down one by one. Fixed in version 4.4.0.11.
      • [AER-6016] - (XDR) May miss records when a destination cluster is down, especially if there is only one destination. Fixed in version 4.4.0.11.
      • [AER-6006] - (KVS) For 'strong-consistency' namespaces, re-replications may unnecessarily assert in very rare situations. Fixed in version 4.4.0.10.
      • [AER-6002] - (BALANCE) For 'strong-consistency' namespaces with 'replication-factor' 1, removing node(s) from roster may cause crash. Fixed in version 4.4.0.10.
      • [AER-5984] - (TLS) Small memory leak when logging a new TLS connection. Fixed in version 4.4.0.10.
      • [AER-5995] - (BALANCE) For `strong-consistency` namespaces, if nodes are quiesced, `migrate-fill-delay` does not work properly. Fixed in version 4.4.0.9.

    Bug Fixes

    • Enterprise & Community
      • [AER-5985] - (STORAGE) Improper handling of dropped keys when replicating or migrating records.
    • Enterprise Only
      • [AER-5990] - (INFO) Service context configuration item `migrate-fill-delay` does not take time units when set dynamically.

  • 4.4.0.7
    Release Date: December 13, 2018
    • The CentOS 7 RPM packages are built with OpenSSL 1.0.2, which is the current shipping package version. If you are running on an older version of CentOS 7 which uses OpenSSL 1.0.1, the installation will not succeed due to a dependency mismatch. Please resolve by either updating CentOS patches (security or whole release) to a point where OpenSSL 1.0.2 is used, or install OpenSSL 1.0.2 using "yum update openssl".
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • Enterprise & Community
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.0.24.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.0.24.
      • [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.0.24.
      • [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.0.23.
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure. Fixed in version 4.5.0.20.
      • [AER-6146] - (KVS) With 'debug-allocations' enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.0.19.
      • [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.0.17
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.0.16.
      • [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.0.15.
      • [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.0.15.
      • [AER-6086] - (CDT) Single result operations returning boolean are not translated correctly to integer. Fixed in version 4.5.0.14.
      • [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.0.14.
      • [AER-6077] - (BATCH) For 'storage-engine memory' namespaces, batch transactions unnecessarily return an error if record size exceeds 10MB. Fixed in version 4.5.0.13.
      • [AER-6068] - (LOGGING) Concurrent SIGHUPs to roll log files may race and double close a log sink file descriptor. Fixed in version 4.5.0.12.
      • [AER-6050] - (CDT) Extremely large unsorted lists or maps that require sorting within an operation may overflow the stack. Fixed in version 4.4.0.15.
      • [AER-6028] - (KVS) Proxied requests are failed by destination node before its first rebalance instead of returned to sender for retry. Fixed in version 4.4.0.14
      • [AER-6034] - (SCAN) Scans with a socket timeout of zero (meaning never time out) inadvertently time out. Fixed in version 4.4.0.14.
      • [AER-6029] - (FABRIC) Load balance counter for send threads does not decrement correctly in certain rare circumstances. Fixed in version 4.4.0.14.
      • [AER-6020] - (NETWORK) The heartbeat context configuration item 'mesh-seed-address-port' is limited to 64 characters when using DNS. Fixed in version 4.4.0.13.
      • [AER-6007] - (CDT) Map operations that add items and use both the DO_PARTIAL and NO_FAIL error policies may overwrite memory. Fixed in version 4.4.0.10.
      • [AER-5996] - (KVS) Regression - service context configuration item `auto-pin` values `cpu` and `numa` do not pin service threads to CPUs. Fixed in version 4.4.0.9.
      • [AER-5997] - (MIGRATION) Rare race condition causes `migrate_signals_remaining` stat to underflow. Fixed in version 4.4.0.9.
      • [AER-5985] - (STORAGE) Improper handling of dropped keys when replicating or migrating records. Fixed in version 4.4.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-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-6035] - (BALANCE) For AP namespaces with `prefer-uniform-balance` true, there may be redundant migrations after shutting down a quiesced node. Fixed in version 4.5.2.1.
      • [AER-6041] - (XDR) Honor compression threshold configuration for http destination. Fixed in version 4.5.2.1.
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.0.24.
      • [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.0.22.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item 'report-authentication' true. Fixed in version 4.5.0.21.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.5.0.19.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.0.19.
      • [AER-6089] - (XDR) Race condition across multiple connections in libcurl may cause crash. Fixed in version 4.5.0.14.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart. Fixed in version 4.5.0.15.
      • [AER-6090] - (SECURITY) Batch sub-transactions' digests are not logged in the 'report-data-op' audit trail. Fixed in version 4.5.0.14.
      • [AER-6072] - (XDR) Crash using multi-handles in curl library when using change notification. Fixed in version 4.5.0.13.
      • [AER-6075] - (XDR) Dynamically setting xdr context configuration items when configuration file has no xdr context causes crash. Fixed in version 4.5.0.13.
      • [AER-6069] - (SECURITY) Minor memory leak during LDAP login process. Fixed in version 4.5.0.12.
      • [AER-6049] - (XDR) May unnecessarily assert when a fresh socket goes bad while shipping to http destinations. Fixed in version 4.4.0.15.
      • [AER-6031] - (KVS) For 'strong-consistency' namespaces, replications may unnecessarily assert when they are concurrent with non-durable deletes. Fixed in version 4.4.0.14.
      • [AER-6022] - (KVS) May unnecessarily assert when fast restarting after a shutdown that left a ref-counted record (for reduce, e.g. scan) that was deleted. Fixed in version 4.4.0.13.
      • [AER-6012] - (MIGRATION) For AP namespaces, there may be redundant migrations when quiescing multiple nodes at once and later shutting them down one by one. Fixed in version 4.4.0.11.
      • [AER-6016] - (XDR) May miss records when a destination cluster is down, especially if there is only one destination. Fixed in version 4.4.0.11.
      • [AER-6006] - (KVS) For 'strong-consistency' namespaces, re-replications may unnecessarily assert in very rare situations. Fixed in version 4.4.0.10.
      • [AER-6002] - (BALANCE) For 'strong-consistency' namespaces with 'replication-factor' 1, removing node(s) from roster may cause crash. Fixed in version 4.4.0.10.
      • [AER-5984] - (TLS) Small memory leak when logging a new TLS connection. Fixed in version 4.4.0.10.
      • [AER-5995] - (BALANCE) For `strong-consistency` namespaces, if nodes are quiesced, `migrate-fill-delay` does not work properly. Fixed in version 4.4.0.9.
      • [AER-5990] - (INFO) Service context configuration item `migrate-fill-delay` does not take time units when set dynamically. Fixed in version 4.4.0.8.

    Bug Fixes

    • Enterprise Only
      • [AER-5982] - (XDR) Some records may get stuck in flight to http server when the load stops.

  • 4.4.0.6
    Release Date: December 5, 2018
    • The CentOS 7 RPM packages are built with OpenSSL 1.0.2, which is the current shipping package version. If you are running on an older version of CentOS 7 which uses OpenSSL 1.0.1, the installation will not succeed due to a dependency mismatch. Please resolve by either updating CentOS patches (security or whole release) to a point where OpenSSL 1.0.2 is used, or install OpenSSL 1.0.2 using "yum update openssl".
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • Enterprise & Community
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.0.24.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.0.24.
      • [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.0.24.
      • [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.0.23.
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure. Fixed in version 4.5.0.20.
      • [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.0.17
      • [AER-6146] - (KVS) With 'debug-allocations' enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.0.19.
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.0.16.
      • [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.0.15.
      • [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.0.15.
      • [AER-6086] - (CDT) Single result operations returning boolean are not translated correctly to integer. Fixed in version 4.5.0.14.
      • [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.0.14.
      • [AER-6077] - (BATCH) For 'storage-engine memory' namespaces, batch transactions unnecessarily return an error if record size exceeds 10MB. Fixed in version 4.5.0.13.
      • [AER-6068] - (LOGGING) Concurrent SIGHUPs to roll log files may race and double close a log sink file descriptor. Fixed in version 4.5.0.12.
      • [AER-6050] - (CDT) Extremely large unsorted lists or maps that require sorting within an operation may overflow the stack. Fixed in version 4.4.0.15.
      • [AER-6028] - (KVS) Proxied requests are failed by destination node before its first rebalance instead of returned to sender for retry. Fixed in version 4.4.0.14
      • [AER-6034] - (SCAN) Scans with a socket timeout of zero (meaning never time out) inadvertently time out. Fixed in version 4.4.0.14.
      • [AER-6029] - (FABRIC) Load balance counter for send threads does not decrement correctly in certain rare circumstances. Fixed in version 4.4.0.14.
      • [AER-6020] - (NETWORK) The heartbeat context configuration item 'mesh-seed-address-port' is limited to 64 characters when using DNS. Fixed in version 4.4.0.13.
      • [AER-6007] - (CDT) Map operations that add items and use both the DO_PARTIAL and NO_FAIL error policies may overwrite memory. Fixed in version 4.4.0.10.
      • [AER-5996] - (KVS) Regression - service context configuration item `auto-pin` values `cpu` and `numa` do not pin service threads to CPUs. Fixed in version 4.4.0.9.
      • [AER-5997] - (MIGRATION) Rare race condition causes `migrate_signals_remaining` stat to underflow. Fixed in version 4.4.0.9.
      • [AER-5985] - (STORAGE) Improper handling of dropped keys when replicating or migrating records. Fixed in version 4.4.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-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-6035] - (BALANCE) For AP namespaces with `prefer-uniform-balance` true, there may be redundant migrations after shutting down a quiesced node. Fixed in version 4.5.2.1.
      • [AER-6041] - (XDR) Honor compression threshold configuration for http destination. Fixed in version 4.5.2.1.
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.0.24.
      • [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.0.22.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item 'report-authentication' true. Fixed in version 4.5.0.21.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.5.0.19.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.0.19.
      • [AER-6089] - (XDR) Race condition across multiple connections in libcurl may cause crash. Fixed in version 4.5.0.14.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart. Fixed in version 4.5.0.15.
      • [AER-6090] - (SECURITY) Batch sub-transactions' digests are not logged in the 'report-data-op' audit trail. Fixed in version 4.5.0.14.
      • [AER-6072] - (XDR) Crash using multi-handles in curl library when using change notification. Fixed in version 4.5.0.13.
      • [AER-6075] - (XDR) Dynamically setting xdr context configuration items when configuration file has no xdr context causes crash. Fixed in version 4.5.0.13.
      • [AER-6069] - (SECURITY) Minor memory leak during LDAP login process. Fixed in version 4.5.0.12.
      • [AER-6049] - (XDR) May unnecessarily assert when a fresh socket goes bad while shipping to http destinations. Fixed in version 4.4.0.15.
      • [AER-6031] - (KVS) For 'strong-consistency' namespaces, replications may unnecessarily assert when they are concurrent with non-durable deletes. Fixed in version 4.4.0.14.
      • [AER-6022] - (KVS) May unnecessarily assert when fast restarting after a shutdown that left a ref-counted record (for reduce, e.g. scan) that was deleted. Fixed in version 4.4.0.13.
      • [AER-6012] - (MIGRATION) For AP namespaces, there may be redundant migrations when quiescing multiple nodes at once and later shutting them down one by one. Fixed in version 4.4.0.11.
      • [AER-6016] - (XDR) May miss records when a destination cluster is down, especially if there is only one destination. Fixed in version 4.4.0.11.
      • [AER-6006] - (KVS) For 'strong-consistency' namespaces, re-replications may unnecessarily assert in very rare situations. Fixed in version 4.4.0.10.
      • [AER-6002] - (BALANCE) For 'strong-consistency' namespaces with 'replication-factor' 1, removing node(s) from roster may cause crash. Fixed in version 4.4.0.10.
      • [AER-5984] - (TLS) Small memory leak when logging a new TLS connection. Fixed in version 4.4.0.10.
      • [AER-5995] - (BALANCE) For `strong-consistency` namespaces, if nodes are quiesced, `migrate-fill-delay` does not work properly. Fixed in version 4.4.0.9.
      • [AER-5990] - (INFO) Service context configuration item `migrate-fill-delay` does not take time units when set dynamically. Fixed in version 4.4.0.8.
      • [AER-5982] - (XDR) Some records may get stuck in flight to http server when the load stops. Fixed in version 4.4.0.7.

    Bug Fixes

    • Enterprise Only
      • [AER-5981] - (SECURITY) Login command failure (e.g. incorrect password) may eventually result in assertion or double free.

  • 4.4.0.5
    Release Date: November 28, 2018
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • Enterprise & Community
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.0.24.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.0.24.
      • [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.0.24.
      • [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.0.23.
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure. Fixed in version 4.5.0.20.
      • [AER-6146] - (KVS) With 'debug-allocations' enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.0.19.
      • [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.0.17
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.0.16.
      • [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.0.15.
      • [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.0.15.
      • [AER-6086] - (CDT) Single result operations returning boolean are not translated correctly to integer. Fixed in version 4.5.0.14.
      • [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.0.14.
      • [AER-6077] - (BATCH) For 'storage-engine memory' namespaces, batch transactions unnecessarily return an error if record size exceeds 10MB. Fixed in version 4.5.0.13.
      • [AER-6068] - (LOGGING) Concurrent SIGHUPs to roll log files may race and double close a log sink file descriptor. Fixed in version 4.5.0.12.
      • [AER-6050] - (CDT) Extremely large unsorted lists or maps that require sorting within an operation may overflow the stack. Fixed in version 4.4.0.15.
      • [AER-6028] - (KVS) Proxied requests are failed by destination node before its first rebalance instead of returned to sender for retry. Fixed in version 4.4.0.14
      • [AER-6034] - (SCAN) Scans with a socket timeout of zero (meaning never time out) inadvertently time out. Fixed in version 4.4.0.14.
      • [AER-6029] - (FABRIC) Load balance counter for send threads does not decrement correctly in certain rare circumstances. Fixed in version 4.4.0.14.
      • [AER-6020] - (NETWORK) The heartbeat context configuration item 'mesh-seed-address-port' is limited to 64 characters when using DNS. Fixed in version 4.4.0.13.
      • [AER-6007] - (CDT) Map operations that add items and use both the DO_PARTIAL and NO_FAIL error policies may overwrite memory. Fixed in version 4.4.0.10.
      • [AER-5996] - (KVS) Regression - service context configuration item `auto-pin` values `cpu` and `numa` do not pin service threads to CPUs. Fixed in version 4.4.0.9.
      • [AER-5997] - (MIGRATION) Rare race condition causes `migrate_signals_remaining` stat to underflow. Fixed in version 4.4.0.9.
      • [AER-5985] - (STORAGE) Improper handling of dropped keys when replicating or migrating records. Fixed in version 4.4.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-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-6035] - (BALANCE) For AP namespaces with `prefer-uniform-balance` true, there may be redundant migrations after shutting down a quiesced node. Fixed in version 4.5.2.1.
      • [AER-6041] - (XDR) Honor compression threshold configuration for http destination. Fixed in version 4.5.2.1.
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.0.24.
      • [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.0.22.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item 'report-authentication' true. Fixed in version 4.5.0.21.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.5.0.19.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.0.19.
      • [AER-6089] - (XDR) Race condition across multiple connections in libcurl may cause crash. Fixed in version 4.5.0.14.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart. Fixed in version 4.5.0.15.
      • [AER-6090] - (SECURITY) Batch sub-transactions' digests are not logged in the 'report-data-op' audit trail. Fixed in version 4.5.0.14.
      • [AER-6072] - (XDR) Crash using multi-handles in curl library when using change notification. Fixed in version 4.5.0.13.
      • [AER-6075] - (XDR) Dynamically setting xdr context configuration items when configuration file has no xdr context causes crash. Fixed in version 4.5.0.13.
      • [AER-6069] - (SECURITY) Minor memory leak during LDAP login process. Fixed in version 4.5.0.12.
      • [AER-6049] - (XDR) May unnecessarily assert when a fresh socket goes bad while shipping to http destinations. Fixed in version 4.4.0.15.
      • [AER-6031] - (KVS) For 'strong-consistency' namespaces, replications may unnecessarily assert when they are concurrent with non-durable deletes. Fixed in version 4.4.0.14.
      • [AER-6022] - (KVS) May unnecessarily assert when fast restarting after a shutdown that left a ref-counted record (for reduce, e.g. scan) that was deleted. Fixed in version 4.4.0.13.
      • [AER-6012] - (MIGRATION) For AP namespaces, there may be redundant migrations when quiescing multiple nodes at once and later shutting them down one by one. Fixed in version 4.4.0.11.
      • [AER-6016] - (XDR) May miss records when a destination cluster is down, especially if there is only one destination. Fixed in version 4.4.0.11.
      • [AER-6006] - (KVS) For 'strong-consistency' namespaces, re-replications may unnecessarily assert in very rare situations. Fixed in version 4.4.0.10.
      • [AER-6002] - (BALANCE) For 'strong-consistency' namespaces with 'replication-factor' 1, removing node(s) from roster may cause crash. Fixed in version 4.4.0.10.
      • [AER-5984] - (TLS) Small memory leak when logging a new TLS connection. Fixed in version 4.4.0.10.
      • [AER-5995] - (BALANCE) For `strong-consistency` namespaces, if nodes are quiesced, `migrate-fill-delay` does not work properly. Fixed in version 4.4.0.9.
      • [AER-5990] - (INFO) Service context configuration item `migrate-fill-delay` does not take time units when set dynamically. Fixed in version 4.4.0.8.
      • [AER-5982] - (XDR) Some records may get stuck in flight to http server when the load stops. Fixed in version 4.4.0.7.
      • [AER-5981] - (SECURITY) Login command failure (e.g. incorrect password) may eventually result in assertion or double free. Fixed in version 4.4.0.6.

    Improvements

    • Enterprise & Community
      • [AER-5975] - (SMD) Ignore unknown JSON items within SMD items.

    Bug Fixes

    • Enterprise Only
      • [AER-5976] - (XDR) If using any HTTP version 2 option with 'change notification', bug in curl library can cause crash.
      • [AER-5974] - (BALANCE) For 'strong-consistency' namespaces, rare cluster split scenario after expanding roster can trigger assertion.

  • 4.4.0.4
    Release Date: November 19, 2018
    • Change Notification Framework is an Enterprise Edition only feature requiring an additional license. Existing Aerospike Enterprise customers should contact their account representative for a trial license.
    • Qualified `el6` package on Amazon Linux.
    • Qualified `el7` package on Amazon Linux 2.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • Enterprise & Community
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.0.24.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.0.24.
      • [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.0.24.
      • [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.0.23.
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure. Fixed in version 4.5.0.20.
      • [AER-6146] - (KVS) With 'debug-allocations' enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.0.19.
      • [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.0.17
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.0.16.
      • [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.0.15.
      • [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.0.15.
      • [AER-6086] - (CDT) Single result operations returning boolean are not translated correctly to integer. Fixed in version 4.5.0.14.
      • [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.0.14.
      • [AER-6077] - (BATCH) For 'storage-engine memory' namespaces, batch transactions unnecessarily return an error if record size exceeds 10MB. Fixed in version 4.5.0.13.
      • [AER-6068] - (LOGGING) Concurrent SIGHUPs to roll log files may race and double close a log sink file descriptor. Fixed in version 4.5.0.12.
      • [AER-6050] - (CDT) Extremely large unsorted lists or maps that require sorting within an operation may overflow the stack. Fixed in version 4.4.0.15.
      • [AER-6028] - (KVS) Proxied requests are failed by destination node before its first rebalance instead of returned to sender for retry. Fixed in version 4.4.0.14
      • [AER-6034] - (SCAN) Scans with a socket timeout of zero (meaning never time out) inadvertently time out. Fixed in version 4.4.0.14.
      • [AER-6029] - (FABRIC) Load balance counter for send threads does not decrement correctly in certain rare circumstances. Fixed in version 4.4.0.14.
      • [AER-6020] - (NETWORK) The heartbeat context configuration item 'mesh-seed-address-port' is limited to 64 characters when using DNS. Fixed in version 4.4.0.13.
      • [AER-6007] - (CDT) Map operations that add items and use both the DO_PARTIAL and NO_FAIL error policies may overwrite memory. Fixed in version 4.4.0.10.
      • [AER-5996] - (KVS) Regression - service context configuration item `auto-pin` values `cpu` and `numa` do not pin service threads to CPUs. Fixed in version 4.4.0.9.
      • [AER-5997] - (MIGRATION) Rare race condition causes `migrate_signals_remaining` stat to underflow. Fixed in version 4.4.0.9.
      • [AER-5985] - (STORAGE) Improper handling of dropped keys when replicating or migrating records. Fixed in version 4.4.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-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-6035] - (BALANCE) For AP namespaces with `prefer-uniform-balance` true, there may be redundant migrations after shutting down a quiesced node. Fixed in version 4.5.2.1.
      • [AER-6041] - (XDR) Honor compression threshold configuration for http destination. Fixed in version 4.5.2.1.
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.0.24.
      • [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.0.22.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item 'report-authentication' true. Fixed in version 4.5.0.21.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.5.0.19.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.0.19.
      • [AER-6089] - (XDR) Race condition across multiple connections in libcurl may cause crash. Fixed in version 4.5.0.14.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart. Fixed in version 4.5.0.15.
      • [AER-6090] - (SECURITY) Batch sub-transactions' digests are not logged in the 'report-data-op' audit trail. Fixed in version 4.5.0.14.
      • [AER-6072] - (XDR) Crash using multi-handles in curl library when using change notification. Fixed in version 4.5.0.13.
      • [AER-6075] - (XDR) Dynamically setting xdr context configuration items when configuration file has no xdr context causes crash. Fixed in version 4.5.0.13.
      • [AER-6069] - (SECURITY) Minor memory leak during LDAP login process. Fixed in version 4.5.0.12.
      • [AER-6049] - (XDR) May unnecessarily assert when a fresh socket goes bad while shipping to http destinations. Fixed in version 4.4.0.15.
      • [AER-6031] - (KVS) For 'strong-consistency' namespaces, replications may unnecessarily assert when they are concurrent with non-durable deletes. Fixed in version 4.4.0.14.
      • [AER-6022] - (KVS) May unnecessarily assert when fast restarting after a shutdown that left a ref-counted record (for reduce, e.g. scan) that was deleted. Fixed in version 4.4.0.13.
      • [AER-6012] - (MIGRATION) For AP namespaces, there may be redundant migrations when quiescing multiple nodes at once and later shutting them down one by one. Fixed in version 4.4.0.11.
      • [AER-6016] - (XDR) May miss records when a destination cluster is down, especially if there is only one destination. Fixed in version 4.4.0.11.
      • [AER-6006] - (KVS) For 'strong-consistency' namespaces, re-replications may unnecessarily assert in very rare situations. Fixed in version 4.4.0.10.
      • [AER-6002] - (BALANCE) For 'strong-consistency' namespaces with 'replication-factor' 1, removing node(s) from roster may cause crash. Fixed in version 4.4.0.10.
      • [AER-5984] - (TLS) Small memory leak when logging a new TLS connection. Fixed in version 4.4.0.10.
      • [AER-5995] - (BALANCE) For `strong-consistency` namespaces, if nodes are quiesced, `migrate-fill-delay` does not work properly. Fixed in version 4.4.0.9.
      • [AER-5990] - (INFO) Service context configuration item `migrate-fill-delay` does not take time units when set dynamically. Fixed in version 4.4.0.8.
      • [AER-5982] - (XDR) Some records may get stuck in flight to http server when the load stops. Fixed in version 4.4.0.7.
      • [AER-5981] - (SECURITY) Login command failure (e.g. incorrect password) may eventually result in assertion or double free. Fixed in version 4.4.0.6.
      • [AER-5976] - (XDR) If using any HTTP version 2 option with 'change notification', bug in curl library can cause crash. Fixed in version 4.4.0.5.

    New Features

    • Enterprise Only
      • [AER-5960] - (XDR) Added xdr context configuration item 'enable-change-notification' to export records to non-Aerospike destinations.

    Improvements

    • Enterprise & Community
      • [AER-5961] - (BATCH) Removed support for batch-direct mode.
      • [AER-5964] - (CLUSTERING) Resolve DNS asynchronously to avoid blocking heartbeat.
      • [AER-5955] - (INFO) Made 'truncate' command safer against accidents when issuing the command via asinfo tool.
      • [AER-5963] - (INFO) Removed deprecated (client-only) 'replicas-prole' command.
      • [AER-5946] - (GEO) Raised geo2dsphere-within context configuration item 'max-cells' limit to 256, and made 'min-level' and 'max-level' dynamic.
    • Enterprise Only
      • [AER-5957] - (INFO) Added (client-only) 'rebalance-generation' and 'rack-ids' commands.
      • [AER-5907] - (XDR) Added separate counter `xdr_ship_destination_permanent_error` for errors that are not relogged.

    Bug Fixes

    • Enterprise & Community
      • [AER-5867] - (GEO) Predicate expression list value iteration fails for geoJson variables.
      • [AER-5983] - (STATS) Transaction histograms for large requests (e.g., large writes and batches) may show inaccurate '...-start' time slice.
    • Enterprise Only
      • [AER-5965] - (CDT) For 'storage-engine device' namespaces with 'data-in-memory true', ordered map with 2+ elements causes crash on restart.
      • [AER-5916] - (XDR) Reported time lag is inaccurate in digestlog overflow situations.
      • [AER-5948] - (XDR) Log warnings use incorrect names for several TLS context configuration items.

    Updates

  • 4.3.1.14
    Release Date: April 26, 2019
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • Enterprise & Community
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.0.24.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.0.24.
      • [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.0.24.
      • [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.0.23.
      • [AER-6146] - (KVS) With 'debug-allocations' enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.0.19.
      • [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.0.17
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.0.16.
      • [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.0.15.
      • [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.0.15.
      • [AER-6086] - (CDT) Single result operations returning boolean are not translated correctly to integer. Fixed in version 4.5.0.14.
      • [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.0.14.
      • [AER-6077] - (BATCH) For 'storage-engine memory' namespaces, batch transactions unnecessarily return an error if record size exceeds 10MB. Fixed in version 4.5.0.13.
      • [AER-6068] - (LOGGING) Concurrent SIGHUPs to roll log files may race and double close a log sink file descriptor. Fixed in version 4.5.0.12.
    • Enterprise Only
      • [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-6035] - (BALANCE) For AP namespaces with `prefer-uniform-balance` true, there may be redundant migrations after shutting down a quiesced node. Fixed in version 4.5.2.1.
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.0.24.
      • [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.0.22.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item 'report-authentication' true. Fixed in version 4.5.0.21.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.5.0.19.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.0.19.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart. Fixed in version 4.5.0.15.
      • [AER-6090] - (SECURITY) Batch sub-transactions' digests are not logged in the 'report-data-op' audit trail. Fixed in version 4.5.0.14.
      • [AER-6075] - (XDR) Dynamically setting xdr context configuration items when configuration file has no xdr context causes crash. Fixed in version 4.5.0.13.
      • [AER-6069] - (SECURITY) Minor memory leak during LDAP login process. Fixed in version 4.5.0.12.
      • [AER-5965] - (CDT) For 'storage-engine device' namespaces with 'data-in-memory true', ordered map with 2+ elements causes crash on restart. Fixed in version 4.4.0.4.

    Bug Fixes

    • Enterprise & Community
      • [AER-6050] - (CDT) Extremely large unsorted lists or maps that require sorting within an operation may overflow the stack.

  • 4.3.1.13
    Release Date: March 25, 2019
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • Enterprise & Community
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.0.24.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.0.24.
      • [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.0.24.
      • [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.0.23.
      • [AER-6146] - (KVS) With 'debug-allocations' enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.0.19.
      • [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.0.17
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.0.16.
      • [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.0.15.
      • [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.0.15.
      • [AER-6086] - (CDT) Single result operations returning boolean are not translated correctly to integer. Fixed in version 4.5.0.14.
      • [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.0.14.
      • [AER-6077] - (BATCH) For 'storage-engine memory' namespaces, batch transactions unnecessarily return an error if record size exceeds 10MB. Fixed in version 4.5.0.13.
      • [AER-6068] - (LOGGING) Concurrent SIGHUPs to roll log files may race and double close a log sink file descriptor. Fixed in version 4.5.0.12.
      • [AER-6050] - (CDT) Extremely large unsorted lists or maps that require sorting within an operation may overflow the stack. Fixed in version 4.3.1.14.
    • Enterprise Only
      • [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-6035] - (BALANCE) For AP namespaces with `prefer-uniform-balance` true, there may be redundant migrations after shutting down a quiesced node. Fixed in version 4.5.2.1.
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.0.24.
      • [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.0.22.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item 'report-authentication' true. Fixed in version 4.5.0.21.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.5.0.19.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.0.19.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart. Fixed in version 4.5.0.15.
      • [AER-6090] - (SECURITY) Batch sub-transactions' digests are not logged in the 'report-data-op' audit trail. Fixed in version 4.5.0.14.
      • [AER-6075] - (XDR) Dynamically setting xdr context configuration items when configuration file has no xdr context causes crash. Fixed in version 4.5.0.13.
      • [AER-6069] - (SECURITY) Minor memory leak during LDAP login process. Fixed in version 4.5.0.12.
      • [AER-5965] - (CDT) For 'storage-engine device' namespaces with 'data-in-memory true', ordered map with 2+ elements causes crash on restart. Fixed in version 4.4.0.4.

    Improvements

    • Enterprise Only
      • [AER-6036] - (TLS) Do not block a TLS socket for a full second, for example when non-TLS connections are attempted.

    Bug Fixes

    • Enterprise & Community
      • [AER-6028] - (KVS) Proxied requests are failed by destination node before its first rebalance instead of returned to sender for retry.
      • [AER-6034] - (SCAN) Scans with a socket timeout of zero (meaning never time out) inadvertently time out.
      • [AER-6029] - (FABRIC) Load balance counter for send threads does not decrement correctly in certain rare circumstances.
    • Enterprise Only
      • [AER-6031] - (KVS) For 'strong-consistency' namespaces, replications may unnecessarily assert when they are concurrent with non-durable deletes.

  • 4.3.1.12
    Release Date: February 26, 2019
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • Enterprise & Community
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.0.24.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.0.24.
      • [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.0.24.
      • [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.0.23.
      • [AER-6146] - (KVS) With 'debug-allocations' enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.0.19.
      • [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.0.17
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.0.16.
      • [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.0.15.
      • [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.0.15.
      • [AER-6086] - (CDT) Single result operations returning boolean are not translated correctly to integer. Fixed in version 4.5.0.14.
      • [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.0.14.
      • [AER-6077] - (BATCH) For 'storage-engine memory' namespaces, batch transactions unnecessarily return an error if record size exceeds 10MB. Fixed in version 4.5.0.13.
      • [AER-6068] - (LOGGING) Concurrent SIGHUPs to roll log files may race and double close a log sink file descriptor. Fixed in version 4.5.0.12.
      • [AER-6050] - (CDT) Extremely large unsorted lists or maps that require sorting within an operation may overflow the stack. Fixed in version 4.3.1.14.
      • [AER-6028] - (KVS) Proxied requests are failed by destination node before its first rebalance instead of returned to sender for retry. Fixed in version 4.3.1.13.
      • [AER-6034] - (SCAN) Scans with a socket timeout of zero (meaning never time out) inadvertently time out. Fixed in version 4.3.1.13.
      • [AER-6029] - (FABRIC) Load balance counter for send threads does not decrement correctly in certain rare circumstances. Fixed in version 4.3.1.13.
    • Enterprise Only
      • [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-6035] - (BALANCE) For AP namespaces with `prefer-uniform-balance` true, there may be redundant migrations after shutting down a quiesced node. Fixed in version 4.5.2.1.
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.0.24.
      • [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.0.22.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item 'report-authentication' true. Fixed in version 4.5.0.21.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.5.0.19.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.0.19.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart. Fixed in version 4.5.0.15.
      • [AER-6090] - (SECURITY) Batch sub-transactions' digests are not logged in the 'report-data-op' audit trail. Fixed in version 4.5.0.14.
      • [AER-6075] - (XDR) Dynamically setting xdr context configuration items when configuration file has no xdr context causes crash. Fixed in version 4.5.0.13.
      • [AER-6069] - (SECURITY) Minor memory leak during LDAP login process. Fixed in version 4.5.0.12.
      • [AER-5965] - (CDT) For 'storage-engine device' namespaces with 'data-in-memory true', ordered map with 2+ elements causes crash on restart. Fixed in version 4.4.0.4.
      • [AER-6031] - (KVS) For 'strong-consistency' namespaces, replications may unnecessarily assert when they are concurrent with non-durable deletes. Fixed in version 4.3.1.13.

    Bug Fixes

    • Enterprise Only
      • [AER-6022] - (KVS) May unnecessarily assert when fast restarting after a shutdown that left a ref-counted record (for reduce, e.g. scan) that was deleted.
      • [AER-5746] - (XDR) Time lag value can be incorrect. Supplements fix done in 4.1.0.1.

  • 4.3.1.11
    Release Date: February 20, 2019
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • Enterprise & Community
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.0.24.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.0.24.
      • [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.0.24.
      • [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.0.23.
      • [AER-6146] - (KVS) With 'debug-allocations' enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.0.19.
      • [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.0.17
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.0.16.
      • [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.0.15.
      • [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.0.15.
      • [AER-6086] - (CDT) Single result operations returning boolean are not translated correctly to integer. Fixed in version 4.5.0.14.
      • [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.0.14.
      • [AER-6077] - (BATCH) For 'storage-engine memory' namespaces, batch transactions unnecessarily return an error if record size exceeds 10MB. Fixed in version 4.5.0.13.
      • [AER-6068] - (LOGGING) Concurrent SIGHUPs to roll log files may race and double close a log sink file descriptor. Fixed in version 4.5.0.12.
      • [AER-6050] - (CDT) Extremely large unsorted lists or maps that require sorting within an operation may overflow the stack. Fixed in version 4.3.1.14.
      • [AER-6028] - (KVS) Proxied requests are failed by destination node before its first rebalance instead of returned to sender for retry. Fixed in version 4.3.1.13.
      • [AER-6034] - (SCAN) Scans with a socket timeout of zero (meaning never time out) inadvertently time out. Fixed in version 4.3.1.13.
      • [AER-6029] - (FABRIC) Load balance counter for send threads does not decrement correctly in certain rare circumstances. Fixed in version 4.3.1.13.
    • Enterprise Only
      • [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-6035] - (BALANCE) For AP namespaces with `prefer-uniform-balance` true, there may be redundant migrations after shutting down a quiesced node. Fixed in version 4.5.2.1.
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.0.24.
      • [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.0.22.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item 'report-authentication' true. Fixed in version 4.5.0.21.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.5.0.19.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.0.19.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart. Fixed in version 4.5.0.15.
      • [AER-6090] - (SECURITY) Batch sub-transactions' digests are not logged in the 'report-data-op' audit trail. Fixed in version 4.5.0.14.
      • [AER-6075] - (XDR) Dynamically setting xdr context configuration items when configuration file has no xdr context causes crash. Fixed in version 4.5.0.13.
      • [AER-6069] - (SECURITY) Minor memory leak during LDAP login process. Fixed in version 4.5.0.12.
      • [AER-5965] - (CDT) For 'storage-engine device' namespaces with 'data-in-memory true', ordered map with 2+ elements causes crash on restart. Fixed in version 4.4.0.4.
      • [AER-6031] - (KVS) For 'strong-consistency' namespaces, replications may unnecessarily assert when they are concurrent with non-durable deletes. Fixed in version 4.3.1.13.
      • [AER-6022] - (KVS) May unnecessarily assert when fast restarting after a shutdown that left a ref-counted record (for reduce, e.g. scan) that was deleted. Fixed in version 4.3.1.12.

    Improvements

    Bug Fixes

    • Enterprise Only
      • [AER-6012] - (MIGRATION) For AP namespaces, there may be redundant migrations when quiescing multiple nodes at once and later shutting them down one by one.

  • 4.3.1.10
    Release Date: January 25, 2019
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • Enterprise & Community
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.0.24.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.0.24.
      • [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.0.24.
      • [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.0.23.
      • [AER-6146] - (KVS) With 'debug-allocations' enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.0.19.
      • [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.0.17
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.0.16.
      • [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.0.15.
      • [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.0.15.
      • [AER-6086] - (CDT) Single result operations returning boolean are not translated correctly to integer. Fixed in version 4.5.0.14.
      • [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.0.14.
      • [AER-6077] - (BATCH) For 'storage-engine memory' namespaces, batch transactions unnecessarily return an error if record size exceeds 10MB. Fixed in version 4.5.0.13.
      • [AER-6068] - (LOGGING) Concurrent SIGHUPs to roll log files may race and double close a log sink file descriptor. Fixed in version 4.5.0.12.
      • [AER-6050] - (CDT) Extremely large unsorted lists or maps that require sorting within an operation may overflow the stack. Fixed in version 4.3.1.14.
      • [AER-6028] - (KVS) Proxied requests are failed by destination node before its first rebalance instead of returned to sender for retry. Fixed in version 4.3.1.13.
      • [AER-6034] - (SCAN) Scans with a socket timeout of zero (meaning never time out) inadvertently time out. Fixed in version 4.3.1.13.
      • [AER-6029] - (FABRIC) Load balance counter for send threads does not decrement correctly in certain rare circumstances. Fixed in version 4.3.1.13.
    • Enterprise Only
      • [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-6035] - (BALANCE) For AP namespaces with `prefer-uniform-balance` true, there may be redundant migrations after shutting down a quiesced node. Fixed in version 4.5.2.1.
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.0.24.
      • [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.0.22.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item 'report-authentication' true. Fixed in version 4.5.0.21.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.5.0.19.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.0.19.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart. Fixed in version 4.5.0.15.
      • [AER-6090] - (SECURITY) Batch sub-transactions' digests are not logged in the 'report-data-op' audit trail. Fixed in version 4.5.0.14.
      • [AER-6075] - (XDR) Dynamically setting xdr context configuration items when configuration file has no xdr context causes crash. Fixed in version 4.5.0.13.
      • [AER-6069] - (SECURITY) Minor memory leak during LDAP login process. Fixed in version 4.5.0.12.
      • [AER-5965] - (CDT) For 'storage-engine device' namespaces with 'data-in-memory true', ordered map with 2+ elements causes crash on restart. Fixed in version 4.4.0.4.
      • [AER-6031] - (KVS) For 'strong-consistency' namespaces, replications may unnecessarily assert when they are concurrent with non-durable deletes. Fixed in version 4.3.1.13.
      • [AER-6022] - (KVS) May unnecessarily assert when fast restarting after a shutdown that left a ref-counted record (for reduce, e.g. scan) that was deleted. Fixed in version 4.3.1.12.
      • [AER-6012] - (MIGRATION) For AP namespaces, there may be redundant migrations when quiescing multiple nodes at once and later shutting them down one by one. Fixed in version 4.3.1.11.

    Bug Fixes

    • Enterprise & Community
      • [AER-6007] - (CDT) Map operations that add items and use both the DO_PARTIAL and NO_FAIL error policies may overwrite memory.
    • Enterprise Only
      • [AER-6006] - (KVS) For `strong-consistency` namespaces, re-replications may unnecessarily assert in very rare situations.
      • [AER-6002] - (BALANCE) For `strong-consistency` namespaces with `replication-factor` 1, removing node(s) from roster may cause crash.
      • [AER-5984] - (TLS) Small memory leak when logging a new TLS connection.

  • 4.3.1.9
    Release Date: January 10, 2019
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • Enterprise & Community
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.0.24.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.0.24.
      • [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.0.24.
      • [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.0.23.
      • [AER-6146] - (KVS) With 'debug-allocations' enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.0.19.
      • [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.0.17
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.0.16.
      • [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.0.15.
      • [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.0.15.
      • [AER-6086] - (CDT) Single result operations returning boolean are not translated correctly to integer. Fixed in version 4.5.0.14.
      • [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.0.14.
      • [AER-6077] - (BATCH) For 'storage-engine memory' namespaces, batch transactions unnecessarily return an error if record size exceeds 10MB. Fixed in version 4.5.0.13.
      • [AER-6068] - (LOGGING) Concurrent SIGHUPs to roll log files may race and double close a log sink file descriptor. Fixed in version 4.5.0.12.
      • [AER-6050] - (CDT) Extremely large unsorted lists or maps that require sorting within an operation may overflow the stack. Fixed in version 4.3.1.14.
      • [AER-6028] - (KVS) Proxied requests are failed by destination node before its first rebalance instead of returned to sender for retry. Fixed in version 4.3.1.13.
      • [AER-6034] - (SCAN) Scans with a socket timeout of zero (meaning never time out) inadvertently time out. Fixed in version 4.3.1.13.
      • [AER-6029] - (FABRIC) Load balance counter for send threads does not decrement correctly in certain rare circumstances. Fixed in version 4.3.1.13.
      • [AER-6007] - (CDT) Map operations that add items and use both the DO_PARTIAL and NO_FAIL error policies may overwrite memory. Fixed in version 4.3.1.10.
    • Enterprise Only
      • [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-6035] - (BALANCE) For AP namespaces with `prefer-uniform-balance` true, there may be redundant migrations after shutting down a quiesced node. Fixed in version 4.5.2.1.
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.0.24.
      • [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.0.22.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item 'report-authentication' true. Fixed in version 4.5.0.21.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.5.0.19.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.0.19.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart. Fixed in version 4.5.0.15.
      • [AER-6090] - (SECURITY) Batch sub-transactions' digests are not logged in the 'report-data-op' audit trail. Fixed in version 4.5.0.14.
      • [AER-6075] - (XDR) Dynamically setting xdr context configuration items when configuration file has no xdr context causes crash. Fixed in version 4.5.0.13.
      • [AER-6069] - (SECURITY) Minor memory leak during LDAP login process. Fixed in version 4.5.0.12.
      • [AER-5965] - (CDT) For 'storage-engine device' namespaces with 'data-in-memory true', ordered map with 2+ elements causes crash on restart. Fixed in version 4.4.0.4.
      • [AER-6031] - (KVS) For 'strong-consistency' namespaces, replications may unnecessarily assert when they are concurrent with non-durable deletes. Fixed in version 4.3.1.13.
      • [AER-6022] - (KVS) May unnecessarily assert when fast restarting after a shutdown that left a ref-counted record (for reduce, e.g. scan) that was deleted. Fixed in version 4.3.1.12.
      • [AER-6012] - (MIGRATION) For AP namespaces, there may be redundant migrations when quiescing multiple nodes at once and later shutting them down one by one. Fixed in version 4.3.1.11.
      • [AER-6006] - (KVS) For 'strong-consistency' namespaces, re-replications may unnecessarily assert in very rare situations. Fixed in version 4.3.1.10.
      • [AER-6002] - (BALANCE) For 'strong-consistency' namespaces with 'replication-factor' 1, removing node(s) from roster may cause crash. Fixed in version 4.3.1.10.
      • [AER-5984] - (TLS) Small memory leak when logging a new TLS connection. Fixed in version 4.3.1.10.

    Bug Fixes

  • 4.3.1.8
    Release Date: December 17, 2018
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • Enterprise & Community
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.0.24.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.0.24.
      • [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.0.24.
      • [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.0.23.
      • [AER-6146] - (KVS) With 'debug-allocations' enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.0.19.
      • [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.0.17
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.0.16.
      • [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.0.15.
      • [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.0.15.
      • [AER-6086] - (CDT) Single result operations returning boolean are not translated correctly to integer. Fixed in version 4.5.0.14.
      • [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.0.14.
      • [AER-6077] - (BATCH) For 'storage-engine memory' namespaces, batch transactions unnecessarily return an error if record size exceeds 10MB. Fixed in version 4.5.0.13.
      • [AER-6068] - (LOGGING) Concurrent SIGHUPs to roll log files may race and double close a log sink file descriptor. Fixed in version 4.5.0.12.
      • [AER-6050] - (CDT) Extremely large unsorted lists or maps that require sorting within an operation may overflow the stack. Fixed in version 4.3.1.14.
      • [AER-6028] - (KVS) Proxied requests are failed by destination node before its first rebalance instead of returned to sender for retry. Fixed in version 4.3.1.13.
      • [AER-6034] - (SCAN) Scans with a socket timeout of zero (meaning never time out) inadvertently time out. Fixed in version 4.3.1.13.
      • [AER-6029] - (FABRIC) Load balance counter for send threads does not decrement correctly in certain rare circumstances. Fixed in version 4.3.1.13.
      • [AER-6007] - (CDT) Map operations that add items and use both the DO_PARTIAL and NO_FAIL error policies may overwrite memory. Fixed in version 4.3.1.10.
      • [AER-5997] - (MIGRATION) Rare race condition causes `migrate_signals_remaining` stat to underflow. Fixed in version 4.3.1.9.
    • Enterprise Only
      • [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-6035] - (BALANCE) For AP namespaces with `prefer-uniform-balance` true, there may be redundant migrations after shutting down a quiesced node. Fixed in version 4.5.2.1.
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.0.24.
      • [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.0.22.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item 'report-authentication' true. Fixed in version 4.5.0.21.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.5.0.19.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.0.19.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart. Fixed in version 4.5.0.15.
      • [AER-6090] - (SECURITY) Batch sub-transactions' digests are not logged in the 'report-data-op' audit trail. Fixed in version 4.5.0.14.
      • [AER-6075] - (XDR) Dynamically setting xdr context configuration items when configuration file has no xdr context causes crash. Fixed in version 4.5.0.13.
      • [AER-6069] - (SECURITY) Minor memory leak during LDAP login process. Fixed in version 4.5.0.12.
      • [AER-5965] - (CDT) For 'storage-engine device' namespaces with 'data-in-memory true', ordered map with 2+ elements causes crash on restart. Fixed in version 4.4.0.4.
      • [AER-6031] - (KVS) For 'strong-consistency' namespaces, replications may unnecessarily assert when they are concurrent with non-durable deletes. Fixed in version 4.3.1.13.
      • [AER-6022] - (KVS) May unnecessarily assert when fast restarting after a shutdown that left a ref-counted record (for reduce, e.g. scan) that was deleted. Fixed in version 4.3.1.12.
      • [AER-6012] - (MIGRATION) For AP namespaces, there may be redundant migrations when quiescing multiple nodes at once and later shutting them down one by one. Fixed in version 4.3.1.11.
      • [AER-6006] - (KVS) For 'strong-consistency' namespaces, re-replications may unnecessarily assert in very rare situations. Fixed in version 4.3.1.10.
      • [AER-6002] - (BALANCE) For 'strong-consistency' namespaces with 'replication-factor' 1, removing node(s) from roster may cause crash. Fixed in version 4.3.1.10.
      • [AER-5984] - (TLS) Small memory leak when logging a new TLS connection. Fixed in version 4.3.1.10.
      • [AER-5995] - (BALANCE) For `strong-consistency` namespaces, if nodes are quiesced, `migrate-fill-delay` does not work properly. Fixed in version 4.3.1.9.

    Bug Fixes

    • Enterprise & Community
      • [AER-5985] - (STORAGE) Improper handling of dropped keys when replicating or migrating records.
    • Enterprise Only
      • [AER-5990] - (INFO) Service context configuration item `migrate-fill-delay` does not take time units when set dynamically.

  • 4.3.1.7
    Release Date: December 5, 2018
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • Enterprise & Community
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.0.24.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.0.24.
      • [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.0.24.
      • [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.0.23.
      • [AER-6146] - (KVS) With 'debug-allocations' enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.0.19.
      • [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.0.17
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.0.16.
      • [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.0.15.
      • [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.0.15.
      • [AER-6086] - (CDT) Single result operations returning boolean are not translated correctly to integer. Fixed in version 4.5.0.14.
      • [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.0.14.
      • [AER-6077] - (BATCH) For 'storage-engine memory' namespaces, batch transactions unnecessarily return an error if record size exceeds 10MB. Fixed in version 4.5.0.13.
      • [AER-6068] - (LOGGING) Concurrent SIGHUPs to roll log files may race and double close a log sink file descriptor. Fixed in version 4.5.0.12.
      • [AER-6050] - (CDT) Extremely large unsorted lists or maps that require sorting within an operation may overflow the stack. Fixed in version 4.3.1.14.
      • [AER-6028] - (KVS) Proxied requests are failed by destination node before its first rebalance instead of returned to sender for retry. Fixed in version 4.3.1.13.
      • [AER-6034] - (SCAN) Scans with a socket timeout of zero (meaning never time out) inadvertently time out. Fixed in version 4.3.1.13.
      • [AER-6029] - (FABRIC) Load balance counter for send threads does not decrement correctly in certain rare circumstances. Fixed in version 4.3.1.13.
      • [AER-6007] - (CDT) Map operations that add items and use both the DO_PARTIAL and NO_FAIL error policies may overwrite memory. Fixed in version 4.3.1.10.
      • [AER-5997] - (MIGRATION) Rare race condition causes `migrate_signals_remaining` stat to underflow. Fixed in version 4.3.1.9.
      • [AER-5985] - (STORAGE) Improper handling of dropped keys when replicating or migrating records. Fixed in version 4.3.1.8.
    • Enterprise Only
      • [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-6035] - (BALANCE) For AP namespaces with `prefer-uniform-balance` true, there may be redundant migrations after shutting down a quiesced node. Fixed in version 4.5.2.1.
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.0.24.
      • [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.0.22.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item 'report-authentication' true. Fixed in version 4.5.0.21.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.5.0.19.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.0.19.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart. Fixed in version 4.5.0.15.
      • [AER-6090] - (SECURITY) Batch sub-transactions' digests are not logged in the 'report-data-op' audit trail. Fixed in version 4.5.0.14.
      • [AER-6075] - (XDR) Dynamically setting xdr context configuration items when configuration file has no xdr context causes crash. Fixed in version 4.5.0.13.
      • [AER-6069] - (SECURITY) Minor memory leak during LDAP login process. Fixed in version 4.5.0.12.
      • [AER-5965] - (CDT) For 'storage-engine device' namespaces with 'data-in-memory true', ordered map with 2+ elements causes crash on restart. Fixed in version 4.4.0.4.
      • [AER-6031] - (KVS) For 'strong-consistency' namespaces, replications may unnecessarily assert when they are concurrent with non-durable deletes. Fixed in version 4.3.1.13.
      • [AER-6022] - (KVS) May unnecessarily assert when fast restarting after a shutdown that left a ref-counted record (for reduce, e.g. scan) that was deleted. Fixed in version 4.3.1.12.
      • [AER-6012] - (MIGRATION) For AP namespaces, there may be redundant migrations when quiescing multiple nodes at once and later shutting them down one by one. Fixed in version 4.3.1.11.
      • [AER-6006] - (KVS) For 'strong-consistency' namespaces, re-replications may unnecessarily assert in very rare situations. Fixed in version 4.3.1.10.
      • [AER-6002] - (BALANCE) For 'strong-consistency' namespaces with 'replication-factor' 1, removing node(s) from roster may cause crash. Fixed in version 4.3.1.10.
      • [AER-5984] - (TLS) Small memory leak when logging a new TLS connection. Fixed in version 4.3.1.10.
      • [AER-5995] - (BALANCE) For `strong-consistency` namespaces, if nodes are quiesced, `migrate-fill-delay` does not work properly. Fixed in version 4.3.1.9.
      • [AER-5990] - (INFO) Service context configuration item `migrate-fill-delay` does not take time units when set dynamically. Fixed in version 4.3.1.8.

    Bug Fixes

    • Enterprise Only
      • [AER-5981] - (SECURITY) Login command failure (e.g. incorrect password) may eventually result in assertion or double free.

  • 4.3.1.6
    Release Date: November 27, 2018
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • Enterprise & Community
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.0.24.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.0.24.
      • [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.0.24.
      • [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.0.23.
      • [AER-6146] - (KVS) With 'debug-allocations' enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.0.19.
      • [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.0.17
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.0.16.
      • [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.0.15.
      • [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.0.15.
      • [AER-6086] - (CDT) Single result operations returning boolean are not translated correctly to integer. Fixed in version 4.5.0.14.
      • [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.0.14.
      • [AER-6077] - (BATCH) For 'storage-engine memory' namespaces, batch transactions unnecessarily return an error if record size exceeds 10MB. Fixed in version 4.5.0.13.
      • [AER-6068] - (LOGGING) Concurrent SIGHUPs to roll log files may race and double close a log sink file descriptor. Fixed in version 4.5.0.12.
      • [AER-6050] - (CDT) Extremely large unsorted lists or maps that require sorting within an operation may overflow the stack. Fixed in version 4.3.1.14.
      • [AER-6028] - (KVS) Proxied requests are failed by destination node before its first rebalance instead of returned to sender for retry. Fixed in version 4.3.1.13.
      • [AER-6034] - (SCAN) Scans with a socket timeout of zero (meaning never time out) inadvertently time out. Fixed in version 4.3.1.13.
      • [AER-6029] - (FABRIC) Load balance counter for send threads does not decrement correctly in certain rare circumstances. Fixed in version 4.3.1.13.
      • [AER-6007] - (CDT) Map operations that add items and use both the DO_PARTIAL and NO_FAIL error policies may overwrite memory. Fixed in version 4.3.1.10.
      • [AER-5997] - (MIGRATION) Rare race condition causes `migrate_signals_remaining` stat to underflow. Fixed in version 4.3.1.9.
      • [AER-5985] - (STORAGE) Improper handling of dropped keys when replicating or migrating records. Fixed in version 4.3.1.8.
    • Enterprise Only
      • [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-6035] - (BALANCE) For AP namespaces with `prefer-uniform-balance` true, there may be redundant migrations after shutting down a quiesced node. Fixed in version 4.5.2.1.
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.0.24.
      • [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.0.22.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item 'report-authentication' true. Fixed in version 4.5.0.21.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.5.0.19.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.0.19.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart. Fixed in version 4.5.0.15.
      • [AER-6090] - (SECURITY) Batch sub-transactions' digests are not logged in the 'report-data-op' audit trail. Fixed in version 4.5.0.14.
      • [AER-6075] - (XDR) Dynamically setting xdr context configuration items when configuration file has no xdr context causes crash. Fixed in version 4.5.0.13.
      • [AER-6069] - (SECURITY) Minor memory leak during LDAP login process. Fixed in version 4.5.0.12.
      • [AER-5965] - (CDT) For 'storage-engine device' namespaces with 'data-in-memory true', ordered map with 2+ elements causes crash on restart. Fixed in version 4.4.0.4.
      • [AER-6031] - (KVS) For 'strong-consistency' namespaces, replications may unnecessarily assert when they are concurrent with non-durable deletes. Fixed in version 4.3.1.13.
      • [AER-6022] - (KVS) May unnecessarily assert when fast restarting after a shutdown that left a ref-counted record (for reduce, e.g. scan) that was deleted. Fixed in version 4.3.1.12.
      • [AER-6012] - (MIGRATION) For AP namespaces, there may be redundant migrations when quiescing multiple nodes at once and later shutting them down one by one. Fixed in version 4.3.1.11.
      • [AER-6006] - (KVS) For 'strong-consistency' namespaces, re-replications may unnecessarily assert in very rare situations. Fixed in version 4.3.1.10.
      • [AER-6002] - (BALANCE) For 'strong-consistency' namespaces with 'replication-factor' 1, removing node(s) from roster may cause crash. Fixed in version 4.3.1.10.
      • [AER-5984] - (TLS) Small memory leak when logging a new TLS connection. Fixed in version 4.3.1.10.
      • [AER-5995] - (BALANCE) For `strong-consistency` namespaces, if nodes are quiesced, `migrate-fill-delay` does not work properly. Fixed in version 4.3.1.9.
      • [AER-5990] - (INFO) Service context configuration item `migrate-fill-delay` does not take time units when set dynamically. Fixed in version 4.3.1.8.
      • [AER-5981] - (SECURITY) Login command failure (e.g. incorrect password) may eventually result in assertion or double free. Fixed in version 4.3.1.7.

    Improvements

    • Enterprise & Community
      • [AER-5975] - (SMD) Ignore unknown JSON items within SMD items.

    Bug Fixes

    • Enterprise Only
      • [AER-5974] - (BALANCE) For 'strong-consistency' namespaces, rare cluster split scenario after expanding roster can trigger assertion.

  • 4.3.1.5
    Release Date: November 6, 2018
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • Enterprise & Community
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.0.24.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.0.24.
      • [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.0.24.
      • [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.0.23.
      • [AER-6146] - (KVS) With 'debug-allocations' enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.0.19.
      • [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.0.17
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.0.16.
      • [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.0.15.
      • [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.0.15.
      • [AER-6086] - (CDT) Single result operations returning boolean are not translated correctly to integer. Fixed in version 4.5.0.14.
      • [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.0.14.
      • [AER-6077] - (BATCH) For 'storage-engine memory' namespaces, batch transactions unnecessarily return an error if record size exceeds 10MB. Fixed in version 4.5.0.13.
      • [AER-6068] - (LOGGING) Concurrent SIGHUPs to roll log files may race and double close a log sink file descriptor. Fixed in version 4.5.0.12.
      • [AER-6050] - (CDT) Extremely large unsorted lists or maps that require sorting within an operation may overflow the stack. Fixed in version 4.3.1.14.
      • [AER-6028] - (KVS) Proxied requests are failed by destination node before its first rebalance instead of returned to sender for retry. Fixed in version 4.3.1.13.
      • [AER-6034] - (SCAN) Scans with a socket timeout of zero (meaning never time out) inadvertently time out. Fixed in version 4.3.1.13.
      • [AER-6029] - (FABRIC) Load balance counter for send threads does not decrement correctly in certain rare circumstances. Fixed in version 4.3.1.13.
      • [AER-6007] - (CDT) Map operations that add items and use both the DO_PARTIAL and NO_FAIL error policies may overwrite memory. Fixed in version 4.3.1.10.
      • [AER-5997] - (MIGRATION) Rare race condition causes `migrate_signals_remaining` stat to underflow. Fixed in version 4.3.1.9.
      • [AER-5985] - (STORAGE) Improper handling of dropped keys when replicating or migrating records. Fixed in version 4.3.1.8.
    • Enterprise Only
      • [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-6035] - (BALANCE) For AP namespaces with `prefer-uniform-balance` true, there may be redundant migrations after shutting down a quiesced node. Fixed in version 4.5.2.1.
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.0.24.
      • [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.0.22.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item 'report-authentication' true. Fixed in version 4.5.0.21.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.5.0.19.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.0.19.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart. Fixed in version 4.5.0.15.
      • [AER-6090] - (SECURITY) Batch sub-transactions' digests are not logged in the 'report-data-op' audit trail. Fixed in version 4.5.0.14.
      • [AER-6075] - (XDR) Dynamically setting xdr context configuration items when configuration file has no xdr context causes crash. Fixed in version 4.5.0.13.
      • [AER-6069] - (SECURITY) Minor memory leak during LDAP login process. Fixed in version 4.5.0.12.
      • [AER-5965] - (CDT) For 'storage-engine device' namespaces with 'data-in-memory true', ordered map with 2+ elements causes crash on restart. Fixed in version 4.4.0.4.
      • [AER-6031] - (KVS) For 'strong-consistency' namespaces, replications may unnecessarily assert when they are concurrent with non-durable deletes. Fixed in version 4.3.1.13.
      • [AER-6022] - (KVS) May unnecessarily assert when fast restarting after a shutdown that left a ref-counted record (for reduce, e.g. scan) that was deleted. Fixed in version 4.3.1.12.
      • [AER-6012] - (MIGRATION) For AP namespaces, there may be redundant migrations when quiescing multiple nodes at once and later shutting them down one by one. Fixed in version 4.3.1.11.
      • [AER-6006] - (KVS) For 'strong-consistency' namespaces, re-replications may unnecessarily assert in very rare situations. Fixed in version 4.3.1.10.
      • [AER-6002] - (BALANCE) For 'strong-consistency' namespaces with 'replication-factor' 1, removing node(s) from roster may cause crash. Fixed in version 4.3.1.10.
      • [AER-5984] - (TLS) Small memory leak when logging a new TLS connection. Fixed in version 4.3.1.10.
      • [AER-5995] - (BALANCE) For `strong-consistency` namespaces, if nodes are quiesced, `migrate-fill-delay` does not work properly. Fixed in version 4.3.1.9.
      • [AER-5990] - (INFO) Service context configuration item `migrate-fill-delay` does not take time units when set dynamically. Fixed in version 4.3.1.8.
      • [AER-5981] - (SECURITY) Login command failure (e.g. incorrect password) may eventually result in assertion or double free. Fixed in version 4.3.1.7.

    Improvements

    • Enterprise & Community
      • [AER-5950] - (STORAGE) When defrag load is extremely low, periodically flush defrag buffer in order to free source write blocks.

    Bug Fixes

    • Enterprise & Community
      • [AER-5956] - (INFO) 'cluster-stable' command fails for 100 or more nodes, or with parameter 'ignore-migrations=false'.
    • Enterprise Only
      • [AER-5958] - (INFO) For 'strong-consistency' namespaces, 'racks' command will return incorrect values if all roster nodes are not present.

  • 4.3.1.4
    Release Date: October 22, 2018
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • Enterprise & Community
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.0.24.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.0.24.
      • [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.0.24.
      • [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.0.23.
      • [AER-6146] - (KVS) With 'debug-allocations' enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.0.19.
      • [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.0.17
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.0.16.
      • [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.0.15.
      • [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.0.15.
      • [AER-6086] - (CDT) Single result operations returning boolean are not translated correctly to integer. Fixed in version 4.5.0.14.
      • [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.0.14.
      • [AER-6077] - (BATCH) For 'storage-engine memory' namespaces, batch transactions unnecessarily return an error if record size exceeds 10MB. Fixed in version 4.5.0.13.
      • [AER-6068] - (LOGGING) Concurrent SIGHUPs to roll log files may race and double close a log sink file descriptor. Fixed in version 4.5.0.12.
      • [AER-6050] - (CDT) Extremely large unsorted lists or maps that require sorting within an operation may overflow the stack. Fixed in version 4.3.1.14.
      • [AER-6028] - (KVS) Proxied requests are failed by destination node before its first rebalance instead of returned to sender for retry. Fixed in version 4.3.1.13.
      • [AER-6034] - (SCAN) Scans with a socket timeout of zero (meaning never time out) inadvertently time out. Fixed in version 4.3.1.13.
      • [AER-6029] - (FABRIC) Load balance counter for send threads does not decrement correctly in certain rare circumstances. Fixed in version 4.3.1.13.
      • [AER-6007] - (CDT) Map operations that add items and use both the DO_PARTIAL and NO_FAIL error policies may overwrite memory. Fixed in version 4.3.1.10.
      • [AER-5997] - (MIGRATION) Rare race condition causes `migrate_signals_remaining` stat to underflow. Fixed in version 4.3.1.9.
      • [AER-5985] - (STORAGE) Improper handling of dropped keys when replicating or migrating records. Fixed in version 4.3.1.8.
    • Enterprise Only
      • [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-6035] - (BALANCE) For AP namespaces with `prefer-uniform-balance` true, there may be redundant migrations after shutting down a quiesced node. Fixed in version 4.5.2.1.
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.0.24.
      • [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.0.22.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item 'report-authentication' true. Fixed in version 4.5.0.21.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.5.0.19.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.0.19.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart. Fixed in version 4.5.0.15.
      • [AER-6090] - (SECURITY) Batch sub-transactions' digests are not logged in the 'report-data-op' audit trail. Fixed in version 4.5.0.14.
      • [AER-6075] - (XDR) Dynamically setting xdr context configuration items when configuration file has no xdr context causes crash. Fixed in version 4.5.0.13.
      • [AER-6069] - (SECURITY) Minor memory leak during LDAP login process. Fixed in version 4.5.0.12.
      • [AER-5965] - (CDT) For 'storage-engine device' namespaces with 'data-in-memory true', ordered map with 2+ elements causes crash on restart. Fixed in version 4.4.0.4.
      • [AER-6031] - (KVS) For 'strong-consistency' namespaces, replications may unnecessarily assert when they are concurrent with non-durable deletes. Fixed in version 4.3.1.13.
      • [AER-6022] - (KVS) May unnecessarily assert when fast restarting after a shutdown that left a ref-counted record (for reduce, e.g. scan) that was deleted. Fixed in version 4.3.1.12.
      • [AER-6012] - (MIGRATION) For AP namespaces, there may be redundant migrations when quiescing multiple nodes at once and later shutting them down one by one. Fixed in version 4.3.1.11.
      • [AER-6006] - (KVS) For 'strong-consistency' namespaces, re-replications may unnecessarily assert in very rare situations. Fixed in version 4.3.1.10.
      • [AER-6002] - (BALANCE) For 'strong-consistency' namespaces with 'replication-factor' 1, removing node(s) from roster may cause crash. Fixed in version 4.3.1.10.
      • [AER-5984] - (TLS) Small memory leak when logging a new TLS connection. Fixed in version 4.3.1.10.
      • [AER-5995] - (BALANCE) For `strong-consistency` namespaces, if nodes are quiesced, `migrate-fill-delay` does not work properly. Fixed in version 4.3.1.9.
      • [AER-5990] - (INFO) Service context configuration item `migrate-fill-delay` does not take time units when set dynamically. Fixed in version 4.3.1.8.
      • [AER-5981] - (SECURITY) Login command failure (e.g. incorrect password) may eventually result in assertion or double free. Fixed in version 4.3.1.7.

    Improvements

    • Enterprise Only
      • [AER-5951] - (BALANCE) Added info command 'protect-roster-set' to make roster changes that remove nodes safer in various scenarios.
      • [AER-5952] - (BALANCE) For 'strong-consistency' namespaces, improved availability in extremely rare cluster split scenario.

    Bug Fixes

    • Enterprise & Community
      • [AER-5953] - (GEO) Possible memory overwrite in extremely rare cases.

  • 4.3.1.3
    Release Date: October 18, 2018

    Known Issues

    • Enterprise & Community
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.0.24.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.0.24.
      • [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.0.24.
      • [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.0.23.
      • [AER-6146] - (KVS) With 'debug-allocations' enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.0.19.
      • [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.0.17
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.0.16.
      • [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.0.15.
      • [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.0.15.
      • [AER-6086] - (CDT) Single result operations returning boolean are not translated correctly to integer. Fixed in version 4.5.0.14.
      • [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.0.14.
      • [AER-6077] - (BATCH) For 'storage-engine memory' namespaces, batch transactions unnecessarily return an error if record size exceeds 10MB. Fixed in version 4.5.0.13.
      • [AER-6068] - (LOGGING) Concurrent SIGHUPs to roll log files may race and double close a log sink file descriptor. Fixed in version 4.5.0.12.
      • [AER-6050] - (CDT) Extremely large unsorted lists or maps that require sorting within an operation may overflow the stack. Fixed in version 4.3.1.14.
      • [AER-6028] - (KVS) Proxied requests are failed by destination node before its first rebalance instead of returned to sender for retry. Fixed in version 4.3.1.13.
      • [AER-6034] - (SCAN) Scans with a socket timeout of zero (meaning never time out) inadvertently time out. Fixed in version 4.3.1.13.
      • [AER-6029] - (FABRIC) Load balance counter for send threads does not decrement correctly in certain rare circumstances. Fixed in version 4.3.1.13.
      • [AER-6007] - (CDT) Map operations that add items and use both the DO_PARTIAL and NO_FAIL error policies may overwrite memory. Fixed in version 4.3.1.10.
      • [AER-5997] - (MIGRATION) Rare race condition causes `migrate_signals_remaining` stat to underflow. Fixed in version 4.3.1.9.
      • [AER-5985] - (STORAGE) Improper handling of dropped keys when replicating or migrating records. Fixed in version 4.3.1.8.
    • Enterprise Only
      • [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-6035] - (BALANCE) For AP namespaces with `prefer-uniform-balance` true, there may be redundant migrations after shutting down a quiesced node. Fixed in version 4.5.2.1.
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.0.24.
      • [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.0.22.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item 'report-authentication' true. Fixed in version 4.5.0.21.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys. Fixed in version 4.5.0.19.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.0.19.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart. Fixed in version 4.5.0.15.
      • [AER-6090] - (SECURITY) Batch sub-transactions' digests are not logged in the 'report-data-op' audit trail. Fixed in version 4.5.0.14.
      • [AER-6075] - (XDR) Dynamically setting xdr context configuration items when configuration file has no xdr context causes crash. Fixed in version 4.5.0.13.
      • [AER-6069] - (SECURITY) Minor memory leak during LDAP login process. Fixed in version 4.5.0.12.
      • [AER-5965] - (CDT) For 'storage-engine device' namespaces with 'data-in-memory true', ordered map with 2+ elements causes crash on restart. Fixed in version 4.4.0.4.
      • [AER-6031] - (KVS) For 'strong-consistency' namespaces, replications may unnecessarily assert when they are concurrent with non-durable deletes. Fixed in version 4.3.1.13.
      • [AER-6022] - (KVS) May unnecessarily assert when fast restarting after a shutdown that left a ref-counted record (for reduce, e.g. scan) that was deleted. Fixed in version 4.3.1.12.
      • [AER-6012] - (MIGRATION) For AP namespaces, there may be redundant migrations when quiescing multiple nodes at once and later shutting them down one by one. Fixed in version 4.3.1.11.
      • [AER-6006] - (KVS) For 'strong-consistency' namespaces, re-replications may unnecessarily assert in very rare situations. Fixed in version 4.3.1.10.
      • [AER-6002] - (BALANCE) For 'strong-consistency' namespaces with 'replication-factor' 1, removing node(s) from roster may cause crash. Fixed in version 4.3.1.10.
      • [AER-5984] - (TLS) Small memory leak when logging a new TLS connection. Fixed in version 4.3.1.10.
      • [AER-5995] - (BALANCE) For `strong-consistency` namespaces, if nodes are quiesced, `migrate-fill-delay` does not work properly. Fixed in version 4.3.1.9.
      • [AER-5990] - (INFO) Service context configuration item `migrate-fill-delay` does not take time units when set dynamically. Fixed in version 4.3.1.8.
      • [AER-5981] - (SECURITY) Login command failure (e.g. incorrect password) may eventually result in assertion or double free. Fixed in version 4.3.1.7.

    New Features

    • Enterprise & Community
      • [AER-5944] - (STORAGE) Added storage context configuration item 'read-page-cache' to disable O_DIRECT and O_DSYNC on selected read operations.
      • [AER-5945] - (CDT) Added INF and WILDCARD types for use in map and list comparators.
    • Enterprise Only
      • [AER-5292] - (BALANCE) Added info command 'quiesce' to inform a node to prepare to be removed from the cluster.
      • [AER-5875] - (TLS) Added support for password-protected TLS keys.
      • [AER-5931] - (MIGRATION) Added service context configuration item 'migrate-fill-delay' to optionally delay "fill" migrations to temporary replicas.

    Improvements

    • Enterprise & Community
      • [AER-5915] - (KVS) Moved configuration item 'transaction-pending-limit' from service context to namespace context.
      • [AER-5938] - (SINDEX) Secondary indexes now use SMD union merge instead of majority merge.
      • [AER-5935] - (INFO) Added service context configuration item 'enable-health-check' and info commands 'health-outliers' and 'health-stats'.
      • [AER-5921] - (NETWORK) Cap the listen() backlog at 512 instead of 128 connections.
      • [AER-5947] - (STORAGE) Replace storage context configuration item 'fsync-max-sec' with 'direct-files'.
      • [AER-5920] - (UDF) System Lua code is now loaded directly from C strings.
      • [AER-5939] - (LOGGING) Use ticker warnings and detail messages to reduce log noise when failing to allocate index arena stages.

    Bug Fixes

    • Enterprise & Community
      • [AER-5933] - (CDT) Map/List get-by-value, get-by-value-list comparison may be incorrect for maps/lists of different lengths.
      • [AER-5930] - (CLUSTERING) Crash in service-list exchange when out of file descriptors.
      • [AER-5943] - (GENERIC) JEMalloc may leak memory when threads exit their run functions.
    • Enterprise Only
      • [AER-5932] - (INFO) Some TLS configuration items returned by 'get-config' contain underscores instead of hyphens.
      • [AER-5925] - (TLS) The TLS context configuration item 'protocols' is parsed incorrectly when multiple values are specified.

    Updates

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

    Known Issues

    • Enterprise & Community
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.0.24.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.0.24.
      • [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.0.24.
      • [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.0.23.
      • [AER-6146] - (KVS) With 'debug-allocations' enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.0.19.
      • [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.0.17
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.0.16.
      • [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.0.15.
      • [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.0.15.
      • [AER-6086] - (CDT) Single result operations returning boolean are not translated correctly to integer. Fixed in version 4.5.0.14.
      • [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.0.14.
      • [AER-6077] - (BATCH) For 'storage-engine memory' namespaces, batch transactions unnecessarily return an error if record size exceeds 10MB. Fixed in version 4.5.0.13.
      • [AER-6068] - (LOGGING) Concurrent SIGHUPs to roll log files may race and double close a log sink file descriptor. Fixed in version 4.5.0.12.
      • [AER-6050] - (CDT) Extremely large unsorted lists or maps that require sorting within an operation may overflow the stack. Fixed in version 4.3.1.14.
      • [AER-6028] - (KVS) Proxied requests are failed by destination node before its first rebalance instead of returned to sender for retry. Fixed in version 4.3.1.13.
      • [AER-6034] - (SCAN) Scans with a socket timeout of zero (meaning never time out) inadvertently time out. Fixed in version 4.3.1.13.
      • [AER-6029] - (FABRIC) Load balance counter for send threads does not decrement correctly in certain rare circumstances. Fixed in version 4.3.1.13.
      • [AER-6007] - (CDT) Map operations that add items and use both the DO_PARTIAL and NO_FAIL error policies may overwrite memory. Fixed in version 4.3.1.10.
      • [AER-5997] - (MIGRATION) Rare race condition causes `migrate_signals_remaining` stat to underflow. Fixed in version 4.3.1.9.
      • [AER-5985] - (STORAGE) Improper handling of dropped keys when replicating or migrating records. Fixed in version 4.3.1.8.
    • Enterprise Only
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.0.24.
      • [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.0.22.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item 'report-authentication' true. Fixed in version 4.5.0.21.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.0.19.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart. Fixed in version 4.5.0.15.
      • [AER-6090] - (SECURITY) Batch sub-transactions' digests are not logged in the 'report-data-op' audit trail. Fixed in version 4.5.0.14.
      • [AER-6075] - (XDR) Dynamically setting xdr context configuration items when configuration file has no xdr context causes crash. Fixed in version 4.5.0.13.
      • [AER-6069] - (SECURITY) Minor memory leak during LDAP login process. Fixed in version 4.5.0.12.
      • [AER-5965] - (CDT) For 'storage-engine device' namespaces with 'data-in-memory true', ordered map with 2+ elements causes crash on restart. Fixed in version 4.4.0.4.
      • [AER-6031] - (KVS) For 'strong-consistency' namespaces, replications may unnecessarily assert when they are concurrent with non-durable deletes. Fixed in version 4.3.1.13.
      • [AER-6022] - (KVS) May unnecessarily assert when fast restarting after a shutdown that left a ref-counted record (for reduce, e.g. scan) that was deleted. Fixed in version 4.3.1.12.
      • [AER-6006] - (KVS) For 'strong-consistency' namespaces, re-replications may unnecessarily assert in very rare situations. Fixed in version 4.3.1.10.
      • [AER-6002] - (BALANCE) For 'strong-consistency' namespaces with 'replication-factor' 1, removing node(s) from roster may cause crash. Fixed in version 4.3.1.10.
      • [AER-5984] - (TLS) Small memory leak when logging a new TLS connection. Fixed in version 4.3.1.10.
      • [AER-5981] - (SECURITY) Login command failure (e.g. incorrect password) may eventually result in assertion or double free. Fixed in version 4.3.1.7.

    Bug Fixes

    • Enterprise Only
      • [AER-5941] - (BALANCE) AP cluster with namespace not on all nodes with 'prefer-uniform-balance' true may access invalid memory.
      • [AER-5942] - (BALANCE) Using 'prefer-uniform-balance' true in a cluster whose node count is a power of two will access uninitialized memory.

  • 4.3.0.9
    Release Date: October 1, 2018
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • Enterprise & Community
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.0.24.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.0.24.
      • [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.0.24.
      • [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.0.23.
      • [AER-6146] - (KVS) With 'debug-allocations' enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.0.19.
      • [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.0.17
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.0.16.
      • [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.0.15.
      • [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.0.15.
      • [AER-6086] - (CDT) Single result operations returning boolean are not translated correctly to integer. Fixed in version 4.5.0.14.
      • [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.0.14.
      • [AER-6077] - (BATCH) For 'storage-engine memory' namespaces, batch transactions unnecessarily return an error if record size exceeds 10MB. Fixed in version 4.5.0.13.
      • [AER-6068] - (LOGGING) Concurrent SIGHUPs to roll log files may race and double close a log sink file descriptor. Fixed in version 4.5.0.12.
      • [AER-6050] - (CDT) Extremely large unsorted lists or maps that require sorting within an operation may overflow the stack. Fixed in version 4.3.1.14.
      • [AER-6028] - (KVS) Proxied requests are failed by destination node before its first rebalance instead of returned to sender for retry. Fixed in version 4.3.1.13.
      • [AER-6034] - (SCAN) Scans with a socket timeout of zero (meaning never time out) inadvertently time out. Fixed in version 4.3.1.13.
      • [AER-6029] - (FABRIC) Load balance counter for send threads does not decrement correctly in certain rare circumstances. Fixed in version 4.3.1.13.
      • [AER-6007] - (CDT) Map operations that add items and use both the DO_PARTIAL and NO_FAIL error policies may overwrite memory. Fixed in version 4.3.1.10.
      • [AER-5997] - (MIGRATION) Rare race condition causes `migrate_signals_remaining` stat to underflow. Fixed in version 4.3.1.9.
      • [AER-5985] - (STORAGE) Improper handling of dropped keys when replicating or migrating records. Fixed in version 4.3.1.8.
    • Enterprise Only
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.0.24.
      • [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.0.22.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item 'report-authentication' true. Fixed in version 4.5.0.21.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.0.19.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart. Fixed in version 4.5.0.15.
      • [AER-6090] - (SECURITY) Batch sub-transactions' digests are not logged in the 'report-data-op' audit trail. Fixed in version 4.5.0.14.
      • [AER-6075] - (XDR) Dynamically setting xdr context configuration items when configuration file has no xdr context causes crash. Fixed in version 4.5.0.13.
      • [AER-6069] - (SECURITY) Minor memory leak during LDAP login process. Fixed in version 4.5.0.12.
      • [AER-5965] - (CDT) For 'storage-engine device' namespaces with 'data-in-memory true', ordered map with 2+ elements causes crash on restart. Fixed in version 4.4.0.4.
      • [AER-6031] - (KVS) For 'strong-consistency' namespaces, replications may unnecessarily assert when they are concurrent with non-durable deletes. Fixed in version 4.3.1.13.
      • [AER-6022] - (KVS) May unnecessarily assert when fast restarting after a shutdown that left a ref-counted record (for reduce, e.g. scan) that was deleted. Fixed in version 4.3.1.12.
      • [AER-6006] - (KVS) For 'strong-consistency' namespaces, re-replications may unnecessarily assert in very rare situations. Fixed in version 4.3.1.10.
      • [AER-6002] - (BALANCE) For 'strong-consistency' namespaces with 'replication-factor' 1, removing node(s) from roster may cause crash. Fixed in version 4.3.1.10.
      • [AER-5984] - (TLS) Small memory leak when logging a new TLS connection. Fixed in version 4.3.1.10.
      • [AER-5981] - (SECURITY) Login command failure (e.g. incorrect password) may eventually result in assertion or double free. Fixed in version 4.3.1.7.
      • [AER-5941] - (BALANCE) AP cluster with namespace not on all nodes with 'prefer-uniform-balance' true may access invalid memory. Fixed in version 4.3.0.10.
      • [AER-5942] - (BALANCE) Using 'prefer-uniform-balance' true in a cluster whose node count is a power of two will access uninitialized memory. Fixed in version 4.3.0.10.

    Bug Fixes

    • Enterprise & Community
      • [AER-5940] - (INFO) Crash when meminfo file reports zero physical memory.

  • 4.3.0.8
    Release Date: September 20, 2018
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • Enterprise & Community
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.0.24.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.0.24.
      • [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.0.24.
      • [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.0.23.
      • [AER-6146] - (KVS) With 'debug-allocations' enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.0.19.
      • [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.0.17
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.0.16.
      • [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.0.15.
      • [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.0.15.
      • [AER-6086] - (CDT) Single result operations returning boolean are not translated correctly to integer. Fixed in version 4.5.0.14.
      • [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.0.14.
      • [AER-6077] - (BATCH) For 'storage-engine memory' namespaces, batch transactions unnecessarily return an error if record size exceeds 10MB. Fixed in version 4.5.0.13.
      • [AER-6068] - (LOGGING) Concurrent SIGHUPs to roll log files may race and double close a log sink file descriptor. Fixed in version 4.5.0.12.
      • [AER-6050] - (CDT) Extremely large unsorted lists or maps that require sorting within an operation may overflow the stack. Fixed in version 4.3.1.14.
      • [AER-6028] - (KVS) Proxied requests are failed by destination node before its first rebalance instead of returned to sender for retry. Fixed in version 4.3.1.13.
      • [AER-6034] - (SCAN) Scans with a socket timeout of zero (meaning never time out) inadvertently time out. Fixed in version 4.3.1.13.
      • [AER-6029] - (FABRIC) Load balance counter for send threads does not decrement correctly in certain rare circumstances. Fixed in version 4.3.1.13.
      • [AER-6007] - (CDT) Map operations that add items and use both the DO_PARTIAL and NO_FAIL error policies may overwrite memory. Fixed in version 4.3.1.10.
      • [AER-5997] - (MIGRATION) Rare race condition causes `migrate_signals_remaining` stat to underflow. Fixed in version 4.3.1.9.
      • [AER-5985] - (STORAGE) Improper handling of dropped keys when replicating or migrating records. Fixed in version 4.3.1.8.
    • Enterprise Only
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.0.24.
      • [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.0.22.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item 'report-authentication' true. Fixed in version 4.5.0.21.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.0.19.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart. Fixed in version 4.5.0.15.
      • [AER-6090] - (SECURITY) Batch sub-transactions' digests are not logged in the 'report-data-op' audit trail. Fixed in version 4.5.0.14.
      • [AER-6075] - (XDR) Dynamically setting xdr context configuration items when configuration file has no xdr context causes crash. Fixed in version 4.5.0.13.
      • [AER-6069] - (SECURITY) Minor memory leak during LDAP login process. Fixed in version 4.5.0.12.
      • [AER-5965] - (CDT) For 'storage-engine device' namespaces with 'data-in-memory true', ordered map with 2+ elements causes crash on restart. Fixed in version 4.4.0.4.
      • [AER-6031] - (KVS) For 'strong-consistency' namespaces, replications may unnecessarily assert when they are concurrent with non-durable deletes. Fixed in version 4.3.1.13.
      • [AER-6022] - (KVS) May unnecessarily assert when fast restarting after a shutdown that left a ref-counted record (for reduce, e.g. scan) that was deleted. Fixed in version 4.3.1.12.
      • [AER-6006] - (KVS) For 'strong-consistency' namespaces, re-replications may unnecessarily assert in very rare situations. Fixed in version 4.3.1.10.
      • [AER-6002] - (BALANCE) For 'strong-consistency' namespaces with 'replication-factor' 1, removing node(s) from roster may cause crash. Fixed in version 4.3.1.10.
      • [AER-5984] - (TLS) Small memory leak when logging a new TLS connection. Fixed in version 4.3.1.10.
      • [AER-5981] - (SECURITY) Login command failure (e.g. incorrect password) may eventually result in assertion or double free. Fixed in version 4.3.1.7.
      • [AER-5941] - (BALANCE) AP cluster with namespace not on all nodes with 'prefer-uniform-balance' true may access invalid memory. Fixed in version 4.3.0.10.
      • [AER-5942] - (BALANCE) Using 'prefer-uniform-balance' true in a cluster whose node count is a power of two will access uninitialized memory. Fixed in version 4.3.0.10.

    Bug Fixes

    • Enterprise & Community
      • [AER-5936] - (STORAGE) Cold start with 'commit-to-device' true may assert on encountering rare mixture of old records.

  • 4.3.0.7
    Release Date: August 30, 2018
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • Enterprise & Community
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.0.24.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.0.24.
      • [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.0.24.
      • [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.0.23.
      • [AER-6146] - (KVS) With 'debug-allocations' enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.0.19.
      • [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.0.17
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.0.16.
      • [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.0.15.
      • [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.0.15.
      • [AER-6086] - (CDT) Single result operations returning boolean are not translated correctly to integer. Fixed in version 4.5.0.14.
      • [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.0.14.
      • [AER-6077] - (BATCH) For 'storage-engine memory' namespaces, batch transactions unnecessarily return an error if record size exceeds 10MB. Fixed in version 4.5.0.13.
      • [AER-6068] - (LOGGING) Concurrent SIGHUPs to roll log files may race and double close a log sink file descriptor. Fixed in version 4.5.0.12.
      • [AER-6050] - (CDT) Extremely large unsorted lists or maps that require sorting within an operation may overflow the stack. Fixed in version 4.3.1.14.
      • [AER-6028] - (KVS) Proxied requests are failed by destination node before its first rebalance instead of returned to sender for retry. Fixed in version 4.3.1.13.
      • [AER-6034] - (SCAN) Scans with a socket timeout of zero (meaning never time out) inadvertently time out. Fixed in version 4.3.1.13.
      • [AER-6029] - (FABRIC) Load balance counter for send threads does not decrement correctly in certain rare circumstances. Fixed in version 4.3.1.13.
      • [AER-6007] - (CDT) Map operations that add items and use both the DO_PARTIAL and NO_FAIL error policies may overwrite memory. Fixed in version 4.3.1.10.
      • [AER-5997] - (MIGRATION) Rare race condition causes `migrate_signals_remaining` stat to underflow. Fixed in version 4.3.1.9.
      • [AER-5985] - (STORAGE) Improper handling of dropped keys when replicating or migrating records. Fixed in version 4.3.1.8.
    • Enterprise Only
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.0.24.
      • [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.0.22.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item 'report-authentication' true. Fixed in version 4.5.0.21.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.0.19.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart. Fixed in version 4.5.0.15.
      • [AER-6090] - (SECURITY) Batch sub-transactions' digests are not logged in the 'report-data-op' audit trail. Fixed in version 4.5.0.14.
      • [AER-6075] - (XDR) Dynamically setting xdr context configuration items when configuration file has no xdr context causes crash. Fixed in version 4.5.0.13.
      • [AER-6069] - (SECURITY) Minor memory leak during LDAP login process. Fixed in version 4.5.0.12.
      • [AER-5965] - (CDT) For 'storage-engine device' namespaces with 'data-in-memory true', ordered map with 2+ elements causes crash on restart. Fixed in version 4.4.0.4.
      • [AER-6031] - (KVS) For 'strong-consistency' namespaces, replications may unnecessarily assert when they are concurrent with non-durable deletes. Fixed in version 4.3.1.13.
      • [AER-6022] - (KVS) May unnecessarily assert when fast restarting after a shutdown that left a ref-counted record (for reduce, e.g. scan) that was deleted. Fixed in version 4.3.1.12.
      • [AER-6006] - (KVS) For 'strong-consistency' namespaces, re-replications may unnecessarily assert in very rare situations. Fixed in version 4.3.1.10.
      • [AER-6002] - (BALANCE) For 'strong-consistency' namespaces with 'replication-factor' 1, removing node(s) from roster may cause crash. Fixed in version 4.3.1.10.
      • [AER-5984] - (TLS) Small memory leak when logging a new TLS connection. Fixed in version 4.3.1.10.
      • [AER-5981] - (SECURITY) Login command failure (e.g. incorrect password) may eventually result in assertion or double free. Fixed in version 4.3.1.7.
      • [AER-5941] - (BALANCE) AP cluster with namespace not on all nodes with 'prefer-uniform-balance' true may access invalid memory. Fixed in version 4.3.0.10.
      • [AER-5942] - (BALANCE) Using 'prefer-uniform-balance' true in a cluster whose node count is a power of two will access uninitialized memory. Fixed in version 4.3.0.10.

    Bug Fixes

    • Enterprise & Community
      • [AER-5928] - (KVS) In non 'data-in-memory' namespaces, read operation mixed with 'replace' write causes write to update instead.
    • Enterprise Only
      • [AER-5929] - (XDR) XDR (sometimes silently) drops bins with name length of 15 characters.

  • 4.3.0.6
    Release Date: August 24, 2018
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • Enterprise & Community
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.0.24.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.0.24.
      • [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.0.24.
      • [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.0.23.
      • [AER-6146] - (KVS) With 'debug-allocations' enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.0.19.
      • [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.0.17
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.0.16.
      • [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.0.15.
      • [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.0.15.
      • [AER-6086] - (CDT) Single result operations returning boolean are not translated correctly to integer. Fixed in version 4.5.0.14.
      • [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.0.14.
      • [AER-6077] - (BATCH) For 'storage-engine memory' namespaces, batch transactions unnecessarily return an error if record size exceeds 10MB. Fixed in version 4.5.0.13.
      • [AER-6068] - (LOGGING) Concurrent SIGHUPs to roll log files may race and double close a log sink file descriptor. Fixed in version 4.5.0.12.
      • [AER-6050] - (CDT) Extremely large unsorted lists or maps that require sorting within an operation may overflow the stack. Fixed in version 4.3.1.14.
      • [AER-6028] - (KVS) Proxied requests are failed by destination node before its first rebalance instead of returned to sender for retry. Fixed in version 4.3.1.13.
      • [AER-6034] - (SCAN) Scans with a socket timeout of zero (meaning never time out) inadvertently time out. Fixed in version 4.3.1.13.
      • [AER-6029] - (FABRIC) Load balance counter for send threads does not decrement correctly in certain rare circumstances. Fixed in version 4.3.1.13.
      • [AER-6007] - (CDT) Map operations that add items and use both the DO_PARTIAL and NO_FAIL error policies may overwrite memory. Fixed in version 4.3.1.10.
      • [AER-5997] - (MIGRATION) Rare race condition causes `migrate_signals_remaining` stat to underflow. Fixed in version 4.3.1.9.
      • [AER-5985] - (STORAGE) Improper handling of dropped keys when replicating or migrating records. Fixed in version 4.3.1.8.
    • Enterprise Only
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.0.24.
      • [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.0.22.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item 'report-authentication' true. Fixed in version 4.5.0.21.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.0.19.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart. Fixed in version 4.5.0.15.
      • [AER-6090] - (SECURITY) Batch sub-transactions' digests are not logged in the 'report-data-op' audit trail. Fixed in version 4.5.0.14.
      • [AER-6075] - (XDR) Dynamically setting xdr context configuration items when configuration file has no xdr context causes crash. Fixed in version 4.5.0.13.
      • [AER-6069] - (SECURITY) Minor memory leak during LDAP login process. Fixed in version 4.5.0.12.
      • [AER-5965] - (CDT) For 'storage-engine device' namespaces with 'data-in-memory true', ordered map with 2+ elements causes crash on restart. Fixed in version 4.4.0.4.
      • [AER-6031] - (KVS) For 'strong-consistency' namespaces, replications may unnecessarily assert when they are concurrent with non-durable deletes. Fixed in version 4.3.1.13.
      • [AER-6022] - (KVS) May unnecessarily assert when fast restarting after a shutdown that left a ref-counted record (for reduce, e.g. scan) that was deleted. Fixed in version 4.3.1.12.
      • [AER-6006] - (KVS) For 'strong-consistency' namespaces, re-replications may unnecessarily assert in very rare situations. Fixed in version 4.3.1.10.
      • [AER-6002] - (BALANCE) For 'strong-consistency' namespaces with 'replication-factor' 1, removing node(s) from roster may cause crash. Fixed in version 4.3.1.10.
      • [AER-5984] - (TLS) Small memory leak when logging a new TLS connection. Fixed in version 4.3.1.10.
      • [AER-5981] - (SECURITY) Login command failure (e.g. incorrect password) may eventually result in assertion or double free. Fixed in version 4.3.1.7.
      • [AER-5941] - (BALANCE) AP cluster with namespace not on all nodes with 'prefer-uniform-balance' true may access invalid memory. Fixed in version 4.3.0.10.
      • [AER-5942] - (BALANCE) Using 'prefer-uniform-balance' true in a cluster whose node count is a power of two will access uninitialized memory. Fixed in version 4.3.0.10.
      • [AER-5929] - (XDR) XDR (sometimes silently) drops bins with name length of 15 characters. Fixed in version 4.3.0.7.

    Bug Fixes

    • Enterprise Only
      • [AER-5924] - (BALANCE) May assert rebalancing to cluster containing non-roster node with unique rack-id.

  • 4.3.0.4
    Release Date: August 17, 2018
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • Enterprise & Community
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.0.24.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.0.24.
      • [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.0.24.
      • [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.0.23.
      • [AER-6146] - (KVS) With 'debug-allocations' enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.0.19.
      • [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.0.17
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.0.16.
      • [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.0.15.
      • [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.0.15.
      • [AER-6086] - (CDT) Single result operations returning boolean are not translated correctly to integer. Fixed in version 4.5.0.14.
      • [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.0.14.
      • [AER-6077] - (BATCH) For 'storage-engine memory' namespaces, batch transactions unnecessarily return an error if record size exceeds 10MB. Fixed in version 4.5.0.13.
      • [AER-6068] - (LOGGING) Concurrent SIGHUPs to roll log files may race and double close a log sink file descriptor. Fixed in version 4.5.0.12.
      • [AER-6050] - (CDT) Extremely large unsorted lists or maps that require sorting within an operation may overflow the stack. Fixed in version 4.3.1.14.
      • [AER-6028] - (KVS) Proxied requests are failed by destination node before its first rebalance instead of returned to sender for retry. Fixed in version 4.3.1.13.
      • [AER-6034] - (SCAN) Scans with a socket timeout of zero (meaning never time out) inadvertently time out. Fixed in version 4.3.1.13.
      • [AER-6029] - (FABRIC) Load balance counter for send threads does not decrement correctly in certain rare circumstances. Fixed in version 4.3.1.13.
      • [AER-6007] - (CDT) Map operations that add items and use both the DO_PARTIAL and NO_FAIL error policies may overwrite memory. Fixed in version 4.3.1.10.
      • [AER-5997] - (MIGRATION) Rare race condition causes `migrate_signals_remaining` stat to underflow. Fixed in version 4.3.1.9.
      • [AER-5985] - (STORAGE) Improper handling of dropped keys when replicating or migrating records. Fixed in version 4.3.1.8.
    • Enterprise Only
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.0.24.
      • [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.0.22.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item 'report-authentication' true. Fixed in version 4.5.0.21.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.0.19.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart. Fixed in version 4.5.0.15.
      • [AER-6090] - (SECURITY) Batch sub-transactions' digests are not logged in the 'report-data-op' audit trail. Fixed in version 4.5.0.14.
      • [AER-6075] - (XDR) Dynamically setting xdr context configuration items when configuration file has no xdr context causes crash. Fixed in version 4.5.0.13.
      • [AER-6069] - (SECURITY) Minor memory leak during LDAP login process. Fixed in version 4.5.0.12.
      • [AER-5965] - (CDT) For 'storage-engine device' namespaces with 'data-in-memory true', ordered map with 2+ elements causes crash on restart. Fixed in version 4.4.0.4.
      • [AER-6031] - (KVS) For 'strong-consistency' namespaces, replications may unnecessarily assert when they are concurrent with non-durable deletes. Fixed in version 4.3.1.13.
      • [AER-6022] - (KVS) May unnecessarily assert when fast restarting after a shutdown that left a ref-counted record (for reduce, e.g. scan) that was deleted. Fixed in version 4.3.1.12.
      • [AER-6006] - (KVS) For 'strong-consistency' namespaces, re-replications may unnecessarily assert in very rare situations. Fixed in version 4.3.1.10.
      • [AER-6002] - (BALANCE) For 'strong-consistency' namespaces with 'replication-factor' 1, removing node(s) from roster may cause crash. Fixed in version 4.3.1.10.
      • [AER-5984] - (TLS) Small memory leak when logging a new TLS connection. Fixed in version 4.3.1.10.
      • [AER-5981] - (SECURITY) Login command failure (e.g. incorrect password) may eventually result in assertion or double free. Fixed in version 4.3.1.7.
      • [AER-5941] - (BALANCE) AP cluster with namespace not on all nodes with 'prefer-uniform-balance' true may access invalid memory. Fixed in version 4.3.0.10.
      • [AER-5942] - (BALANCE) Using 'prefer-uniform-balance' true in a cluster whose node count is a power of two will access uninitialized memory. Fixed in version 4.3.0.10.
      • [AER-5929] - (XDR) XDR (sometimes silently) drops bins with name length of 15 characters. Fixed in version 4.3.0.7.
      • [AER-5924] - (BALANCE) May assert rebalancing to cluster containing non-roster node with unique rack-id. Fixed in version 4.3.0.6.

    Bug Fixes

    • Enterprise & Community
      • [AER-5917] - (KVS) In non 'data-in-memory' namespaces, cannot add a stored key to an existing record.
    • Enterprise Only
      • [AER-5919] - (KVS) Fast restart may assert if previous shutdown occurred during a rebalance.

  • 4.3.0.3
    Release Date: August 13, 2018
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • Enterprise & Community
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.0.24.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.0.24.
      • [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.0.24.
      • [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.0.23.
      • [AER-6146] - (KVS) With 'debug-allocations' enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.0.19.
      • [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.0.17
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.0.16.
      • [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.0.15.
      • [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.0.15.
      • [AER-6086] - (CDT) Single result operations returning boolean are not translated correctly to integer. Fixed in version 4.5.0.14.
      • [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.0.14.
      • [AER-6077] - (BATCH) For 'storage-engine memory' namespaces, batch transactions unnecessarily return an error if record size exceeds 10MB. Fixed in version 4.5.0.13.
      • [AER-6068] - (LOGGING) Concurrent SIGHUPs to roll log files may race and double close a log sink file descriptor. Fixed in version 4.5.0.12.
      • [AER-6050] - (CDT) Extremely large unsorted lists or maps that require sorting within an operation may overflow the stack. Fixed in version 4.3.1.14.
      • [AER-6028] - (KVS) Proxied requests are failed by destination node before its first rebalance instead of returned to sender for retry. Fixed in version 4.3.1.13.
      • [AER-6034] - (SCAN) Scans with a socket timeout of zero (meaning never time out) inadvertently time out. Fixed in version 4.3.1.13.
      • [AER-6029] - (FABRIC) Load balance counter for send threads does not decrement correctly in certain rare circumstances. Fixed in version 4.3.1.13.
      • [AER-6007] - (CDT) Map operations that add items and use both the DO_PARTIAL and NO_FAIL error policies may overwrite memory. Fixed in version 4.3.1.10.
      • [AER-5997] - (MIGRATION) Rare race condition causes `migrate_signals_remaining` stat to underflow. Fixed in version 4.3.1.9.
      • [AER-5985] - (STORAGE) Improper handling of dropped keys when replicating or migrating records. Fixed in version 4.3.1.8.
      • [AER-5917] - (KVS) In non 'data-in-memory' namespaces, cannot add a stored key to an existing record. Fixed in version 4.3.0.4.
    • Enterprise Only
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.0.24.
      • [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.0.22.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item 'report-authentication' true. Fixed in version 4.5.0.21.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.0.19.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart. Fixed in version 4.5.0.15.
      • [AER-6090] - (SECURITY) Batch sub-transactions' digests are not logged in the 'report-data-op' audit trail. Fixed in version 4.5.0.14.
      • [AER-6075] - (XDR) Dynamically setting xdr context configuration items when configuration file has no xdr context causes crash. Fixed in version 4.5.0.13.
      • [AER-6069] - (SECURITY) Minor memory leak during LDAP login process. Fixed in version 4.5.0.12.
      • [AER-5965] - (CDT) For 'storage-engine device' namespaces with 'data-in-memory true', ordered map with 2+ elements causes crash on restart. Fixed in version 4.4.0.4.
      • [AER-6031] - (KVS) For 'strong-consistency' namespaces, replications may unnecessarily assert when they are concurrent with non-durable deletes. Fixed in version 4.3.1.13.
      • [AER-6022] - (KVS) May unnecessarily assert when fast restarting after a shutdown that left a ref-counted record (for reduce, e.g. scan) that was deleted. Fixed in version 4.3.1.12.
      • [AER-6006] - (KVS) For 'strong-consistency' namespaces, re-replications may unnecessarily assert in very rare situations. Fixed in version 4.3.1.10.
      • [AER-6002] - (BALANCE) For 'strong-consistency' namespaces with 'replication-factor' 1, removing node(s) from roster may cause crash. Fixed in version 4.3.1.10.
      • [AER-5984] - (TLS) Small memory leak when logging a new TLS connection. Fixed in version 4.3.1.10.
      • [AER-5981] - (SECURITY) Login command failure (e.g. incorrect password) may eventually result in assertion or double free. Fixed in version 4.3.1.7.
      • [AER-5941] - (BALANCE) AP cluster with namespace not on all nodes with 'prefer-uniform-balance' true may access invalid memory. Fixed in version 4.3.0.10.
      • [AER-5942] - (BALANCE) Using 'prefer-uniform-balance' true in a cluster whose node count is a power of two will access uninitialized memory. Fixed in version 4.3.0.10.
      • [AER-5929] - (XDR) XDR (sometimes silently) drops bins with name length of 15 characters. Fixed in version 4.3.0.7.
      • [AER-5924] - (BALANCE) May assert rebalancing to cluster containing non-roster node with unique rack-id. Fixed in version 4.3.0.6.
      • [AER-5919] - (KVS) Fast restart may assert if previous shutdown occurred during a rebalance. Fixed in version 4.3.0.4.

    Bug Fixes

    • Enterprise Only
      • [AER-5913] - (KVS) Re-replication during clock-skew stop-writes leaves record stuck in 're-replicating' state, blocking migrations.

  • 4.3.0.2
    Release Date: August 1, 2018
    • All Flash (Enterprise only, requires new feature key).
    • Ability to choose uniform partition balance over minimal migrations during cluster changes (Enterprise only).
    • Relative range operations for CDTs, and NO_FAIL and DO_PARTIAL CDT error policies.
    • When upgrading the Aerospike Server, from a version prior to 4.3 with replication-factor of 2 or greater along with the use of the rack-aware feature in AP namespaces, refer to the special considerations knowledge base article for details. (Enterprise Only)
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • Enterprise & Community
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.0.24.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.0.24.
      • [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.0.24.
      • [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.0.23.
      • [AER-6146] - (KVS) With 'debug-allocations' enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.0.19.
      • [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.0.17
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.0.16.
      • [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.0.15.
      • [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.0.15.
      • [AER-6086] - (CDT) Single result operations returning boolean are not translated correctly to integer. Fixed in version 4.5.0.14.
      • [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.0.14.
      • [AER-6077] - (BATCH) For 'storage-engine memory' namespaces, batch transactions unnecessarily return an error if record size exceeds 10MB. Fixed in version 4.5.0.13.
      • [AER-6068] - (LOGGING) Concurrent SIGHUPs to roll log files may race and double close a log sink file descriptor. Fixed in version 4.5.0.12.
      • [AER-6050] - (CDT) Extremely large unsorted lists or maps that require sorting within an operation may overflow the stack. Fixed in version 4.3.1.14.
      • [AER-6028] - (KVS) Proxied requests are failed by destination node before its first rebalance instead of returned to sender for retry. Fixed in version 4.3.1.13.
      • [AER-6034] - (SCAN) Scans with a socket timeout of zero (meaning never time out) inadvertently time out. Fixed in version 4.3.1.13.
      • [AER-6029] - (FABRIC) Load balance counter for send threads does not decrement correctly in certain rare circumstances. Fixed in version 4.3.1.13.
      • [AER-6007] - (CDT) Map operations that add items and use both the DO_PARTIAL and NO_FAIL error policies may overwrite memory. Fixed in version 4.3.1.10.
      • [AER-5997] - (MIGRATION) Rare race condition causes `migrate_signals_remaining` stat to underflow. Fixed in version 4.3.1.9.
      • [AER-5985] - (STORAGE) Improper handling of dropped keys when replicating or migrating records. Fixed in version 4.3.1.8.
      • [AER-5917] - (KVS) In non 'data-in-memory' namespaces, cannot add a stored key to an existing record. Fixed in version 4.3.0.4.
    • Enterprise Only
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.0.24.
      • [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.0.22.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item 'report-authentication' true. Fixed in version 4.5.0.21.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.0.19.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart. Fixed in version 4.5.0.15.
      • [AER-6090] - (SECURITY) Batch sub-transactions' digests are not logged in the 'report-data-op' audit trail. Fixed in version 4.5.0.14.
      • [AER-6075] - (XDR) Dynamically setting xdr context configuration items when configuration file has no xdr context causes crash. Fixed in version 4.5.0.13.
      • [AER-6069] - (SECURITY) Minor memory leak during LDAP login process. Fixed in version 4.5.0.12.
      • [AER-5965] - (CDT) For 'storage-engine device' namespaces with 'data-in-memory true', ordered map with 2+ elements causes crash on restart. Fixed in version 4.4.0.4.
      • [AER-6031] - (KVS) For 'strong-consistency' namespaces, replications may unnecessarily assert when they are concurrent with non-durable deletes. Fixed in version 4.3.1.13.
      • [AER-6022] - (KVS) May unnecessarily assert when fast restarting after a shutdown that left a ref-counted record (for reduce, e.g. scan) that was deleted. Fixed in version 4.3.1.12.
      • [AER-6006] - (KVS) For 'strong-consistency' namespaces, re-replications may unnecessarily assert in very rare situations. Fixed in version 4.3.1.10.
      • [AER-6002] - (BALANCE) For 'strong-consistency' namespaces with 'replication-factor' 1, removing node(s) from roster may cause crash. Fixed in version 4.3.1.10.
      • [AER-5984] - (TLS) Small memory leak when logging a new TLS connection. Fixed in version 4.3.1.10.
      • [AER-5981] - (SECURITY) Login command failure (e.g. incorrect password) may eventually result in assertion or double free. Fixed in version 4.3.1.7.
      • [AER-5941] - (BALANCE) AP cluster with namespace not on all nodes with 'prefer-uniform-balance' true may access invalid memory. Fixed in version 4.3.0.10.
      • [AER-5942] - (BALANCE) Using 'prefer-uniform-balance' true in a cluster whose node count is a power of two will access uninitialized memory. Fixed in version 4.3.0.10.
      • [AER-5929] - (XDR) XDR (sometimes silently) drops bins with name length of 15 characters. Fixed in version 4.3.0.7.
      • [AER-5924] - (BALANCE) May assert rebalancing to cluster containing non-roster node with unique rack-id. Fixed in version 4.3.0.6.
      • [AER-5919] - (KVS) Fast restart may assert if previous shutdown occurred during a rebalance. Fixed in version 4.3.0.4.
      • [AER-5913] - (KVS) Re-replication during clock-skew stop-writes leaves record stuck in 're-replicating' state, blocking migrations. Fixed in version 4.3.0.3.

    New Features

    • Enterprise & Community
      • [AER-5891] - (CDT) Added CDT relative range operations.
      • [AER-5892] - (CDT) Added NO_FAIL and DO_PARTIAL CDT error policies.
    • Enterprise Only
      • [AER-5901] - (KVS) Added namespace context configuration item 'index-type' with value 'flash' to use block storage devices for primary index.
      • [AER-5900],[AER-4714] - (BALANCE) Added namespace context configuration item 'prefer-uniform-balance' to choose uniform partition balance over minimal migrations.

    Improvements

    • Enterprise & Community
      • [AER-5881] - (KVS) Setting service context configuration item 'nsup-period' to zero deactivates runtime expiration/eviction.
      • [AER-5882] - (KVS) Setting service context configuration item 'object-size-hist-period' to zero deactivates object size histogram population.
      • [AER-5885] - (KVS) Replaced service context configuration item 'nsup-startup-evict' with namespace context item 'disable-cold-start-eviction'.
      • [AER-5886] - (KVS) Added namespace context configuration item 'disable-nsup' to disable runtime expiration/eviction for the namespace.
      • [AER-5906] - (KVS) Removed default value of namespace context configuration item 'memory-size'.
      • [AER-5909] - (KVS) Improved efficiency of pushing to head of queue.
      • [AER-5883] - (SINDEX) Setting service context configuration item 'sindex-gc-period' to zero deactivates secondary index garbage collection.
      • [AER-5897] - (INFO) Added 'size' parameter and 'ignore-migrations' option to 'cluster-stable' info command, and made 'namespace' parameter optional.
      • [AER-4969] - (INFO) Expose various device-specific metrics through the info protocol.
      • [AER-5893] - (NETWORK) Increased the character limit on heartbeat context configuration item 'mesh-seed-address-port' from 64 to 255.
      • [AER-5902] - (STORAGE) Allow storage files to have shadow files.
      • [AER-5905] - (STORAGE) Removed default value of storage context configuration item 'filesize'.
    • Enterprise Only
      • [AER-5541] - (KVS) Added storage context configuration item 'serialize-tomb-raider' to allow serialization of different namespaces' tomb raids.
      • [AER-5884] - (KVS) Setting namespace context configuration item 'tomb-raider-period' to zero deactivates tomb raider.

    Bug Fixes

    • Enterprise & Community
      • [AER-5904] - (CLUSTERING) Clock skew may be falsely reported briefly when a node joins a cluster where the logical clock is ahead of the physical clock.
      • [AER-5911] - (FABRIC) Race condition caused by recycling duplicate resolution fabric message for replica write/ping.
      • [AER-5894] - (STORAGE) IO on shadow device fails if its minimum IO size exceeds that of its primary device.
    • Enterprise Only
      • [AER-5912] - (CLUSTERING) Slow drives may prevent initial cluster formation under strong consistency when roster is missing.
      • [AER-5888] - (BALANCE) Changing rack IDs with replication factor 3 or more may result in suboptimal master selection.
      • [AER-5880] - (XDR) Dynamic changes to datacenter context configuration items 'dc-connections' and 'dc-connections-idle-ms' are applied to all DCs.

    Updates

  • 4.2.0.10
    Release Date: August 10, 2018
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • Enterprise & Community
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.0.24.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.0.24.
      • [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.0.24.
      • [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.0.23.
      • [AER-6146] - (KVS) With 'debug-allocations' enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.0.19.
      • [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.0.17
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.0.16.
      • [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.0.15.
      • [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.0.15.
      • [AER-6086] - (CDT) Single result operations returning boolean are not translated correctly to integer. Fixed in version 4.5.0.14.
      • [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.0.14.
      • [AER-6077] - (BATCH) For 'storage-engine memory' namespaces, batch transactions unnecessarily return an error if record size exceeds 10MB. Fixed in version 4.5.0.13.
      • [AER-6068] - (LOGGING) Concurrent SIGHUPs to roll log files may race and double close a log sink file descriptor. Fixed in version 4.5.0.12.
      • [AER-6050] - (CDT) Extremely large unsorted lists or maps that require sorting within an operation may overflow the stack. Fixed in version 4.3.1.14.
      • [AER-6034] - (SCAN) Scans with a socket timeout of zero (meaning never time out) inadvertently time out. Fixed in version 4.3.1.13.
      • [AER-6029] - (FABRIC) Load balance counter for send threads does not decrement correctly in certain rare circumstances. Fixed in version 4.3.1.13.
      • [AER-5997] - (MIGRATION) Rare race condition causes `migrate_signals_remaining` stat to underflow. Fixed in version 4.3.1.9.
      • [AER-5985] - (STORAGE) Improper handling of dropped keys when replicating or migrating records. Fixed in version 4.3.1.8.
      • [AER-5917] - (KVS) In non 'data-in-memory' namespaces, cannot add a stored key to an existing record. Fixed in version 4.3.0.4.
    • Enterprise Only
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.0.24.
      • [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.0.22.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item 'report-authentication' true. Fixed in version 4.5.0.21.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.0.19.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart. Fixed in version 4.5.0.15.
      • [AER-6090] - (SECURITY) Batch sub-transactions' digests are not logged in the 'report-data-op' audit trail. Fixed in version 4.5.0.14.
      • [AER-6075] - (XDR) Dynamically setting xdr context configuration items when configuration file has no xdr context causes crash. Fixed in version 4.5.0.13.
      • [AER-6069] - (SECURITY) Minor memory leak during LDAP login process. Fixed in version 4.5.0.12.
      • [AER-5965] - (CDT) For 'storage-engine device' namespaces with 'data-in-memory true', ordered map with 2+ elements causes crash on restart. Fixed in version 4.4.0.4.
      • [AER-6031] - (KVS) For 'strong-consistency' namespaces, replications may unnecessarily assert when they are concurrent with non-durable deletes. Fixed in version 4.3.1.13.
      • [AER-6022] - (KVS) May unnecessarily assert when fast restarting after a shutdown that left a ref-counted record (for reduce, e.g. scan) that was deleted. Fixed in version 4.3.1.12.
      • [AER-6006] - (KVS) For 'strong-consistency' namespaces, re-replications may unnecessarily assert in very rare situations. Fixed in version 4.3.1.10.
      • [AER-6002] - (BALANCE) For 'strong-consistency' namespaces with 'replication-factor' 1, removing node(s) from roster may cause crash. Fixed in version 4.3.1.10.
      • [AER-5984] - (TLS) Small memory leak when logging a new TLS connection. Fixed in version 4.3.1.10.
      • [AER-5981] - (SECURITY) Login command failure (e.g. incorrect password) may eventually result in assertion or double free. Fixed in version 4.3.1.7.
      • [AER-5929] - (XDR) XDR (sometimes silently) drops bins with name length of 15 characters. Fixed in version 4.3.0.7.
      • [AER-5919] - (KVS) Fast restart may assert if previous shutdown occurred during a rebalance. Fixed in version 4.3.0.4.

    Improvements

    • Enterprise & Community
      • [AER-5909] - (KVS) Improved efficiency of pushing to head of queue.

    Bug Fixes

    • Enterprise & Community
      • [AER-5911] - (FABRIC) Race condition caused by recycling duplicate resolution fabric message for replica write/ping.
    • Enterprise Only
      • [AER-5913] - (KVS) Re-replication during clock-skew stop-writes leaves record stuck in 're-replicating' state, blocking migrations.
      • [AER-5912] - (CLUSTERING) Slow drives may prevent initial cluster formation under strong consistency when roster is missing.

  • 4.2.0.7
    Release Date: July 27, 2018
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • Enterprise & Community
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.0.24.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.0.24.
      • [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.0.24.
      • [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.0.23.
      • [AER-6146] - (KVS) With 'debug-allocations' enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.0.19.
      • [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.0.17
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.0.16.
      • [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.0.15.
      • [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.0.15.
      • [AER-6086] - (CDT) Single result operations returning boolean are not translated correctly to integer. Fixed in version 4.5.0.14.
      • [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.0.14.
      • [AER-6077] - (BATCH) For 'storage-engine memory' namespaces, batch transactions unnecessarily return an error if record size exceeds 10MB. Fixed in version 4.5.0.13.
      • [AER-6068] - (LOGGING) Concurrent SIGHUPs to roll log files may race and double close a log sink file descriptor. Fixed in version 4.5.0.12.
      • [AER-6050] - (CDT) Extremely large unsorted lists or maps that require sorting within an operation may overflow the stack. Fixed in version 4.3.1.14.
      • [AER-6034] - (SCAN) Scans with a socket timeout of zero (meaning never time out) inadvertently time out. Fixed in version 4.3.1.13.
      • [AER-6029] - (FABRIC) Load balance counter for send threads does not decrement correctly in certain rare circumstances. Fixed in version 4.3.1.13.
      • [AER-5997] - (MIGRATION) Rare race condition causes `migrate_signals_remaining` stat to underflow. Fixed in version 4.3.1.9.
      • [AER-5985] - (STORAGE) Improper handling of dropped keys when replicating or migrating records. Fixed in version 4.3.1.8.
      • [AER-5917] - (KVS) In non 'data-in-memory' namespaces, cannot add a stored key to an existing record. Fixed in version 4.3.0.4.
    • Enterprise Only
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.0.24.
      • [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.0.22.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item 'report-authentication' true. Fixed in version 4.5.0.21.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.0.19.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart. Fixed in version 4.5.0.15.
      • [AER-6090] - (SECURITY) Batch sub-transactions' digests are not logged in the 'report-data-op' audit trail. Fixed in version 4.5.0.14.
      • [AER-6075] - (XDR) Dynamically setting xdr context configuration items when configuration file has no xdr context causes crash. Fixed in version 4.5.0.13.
      • [AER-6069] - (SECURITY) Minor memory leak during LDAP login process. Fixed in version 4.5.0.12.
      • [AER-5965] - (CDT) For 'storage-engine device' namespaces with 'data-in-memory true', ordered map with 2+ elements causes crash on restart. Fixed in version 4.4.0.4.
      • [AER-6031] - (KVS) For 'strong-consistency' namespaces, replications may unnecessarily assert when they are concurrent with non-durable deletes. Fixed in version 4.3.1.13.
      • [AER-6022] - (KVS) May unnecessarily assert when fast restarting after a shutdown that left a ref-counted record (for reduce, e.g. scan) that was deleted. Fixed in version 4.3.1.12.
      • [AER-6006] - (KVS) For 'strong-consistency' namespaces, re-replications may unnecessarily assert in very rare situations. Fixed in version 4.3.1.10.
      • [AER-6002] - (BALANCE) For 'strong-consistency' namespaces with 'replication-factor' 1, removing node(s) from roster may cause crash. Fixed in version 4.3.1.10.
      • [AER-5984] - (TLS) Small memory leak when logging a new TLS connection. Fixed in version 4.3.1.10.
      • [AER-5981] - (SECURITY) Login command failure (e.g. incorrect password) may eventually result in assertion or double free. Fixed in version 4.3.1.7.
      • [AER-5929] - (XDR) XDR (sometimes silently) drops bins with name length of 15 characters. Fixed in version 4.3.0.7.
      • [AER-5919] - (KVS) Fast restart may assert if previous shutdown occurred during a rebalance. Fixed in version 4.3.0.4.
      • [AER-5912] - (CLUSTERING) Slow drives may prevent initial cluster formation under strong consistency when roster is missing. Fixed in version 4.2.0.10.
      • [AER-5913] - (KVS) Re-replication during clock-skew stop-writes leaves record stuck in 're-replicating' state, blocking migrations. Fixed in version 4.2.0.10.

    Bug Fixes

    • Enterprise & Community
      • [AER-5908] - (UDF) Memory leak running UDFs in single-bin namespaces. Introduced in 3.15.0.1.
    • Enterprise Only
      • [AER-5903] - (STORAGE) Zero padding at end of write blocks may decrypt to accidentally yield good record magic.

  • 4.2.0.5
    Release Date: July 18, 2018
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Known Issues

    • Enterprise & Community
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
      • [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-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.0.24.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.0.24.
      • [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.0.24.
      • [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.0.23.
      • [AER-6146] - (KVS) With 'debug-allocations' enabled, a memory accounting array will eventually overflow and cause a crash. Fixed in version 4.5.0.19.
      • [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.0.17
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate. Fixed in version 4.5.0.16.
      • [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.0.15.
      • [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.0.15.
      • [AER-6086] - (CDT) Single result operations returning boolean are not translated correctly to integer. Fixed in version 4.5.0.14.
      • [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.0.14.
      • [AER-6077] - (BATCH) For 'storage-engine memory' namespaces, batch transactions unnecessarily return an error if record size exceeds 10MB. Fixed in version 4.5.0.13.
      • [AER-6068] - (LOGGING) Concurrent SIGHUPs to roll log files may race and double close a log sink file descriptor. Fixed in version 4.5.0.12.
      • [AER-6050] - (CDT) Extremely large unsorted lists or maps that require sorting within an operation may overflow the stack. Fixed in version 4.3.1.14.
      • [AER-6034] - (SCAN) Scans with a socket timeout of zero (meaning never time out) inadvertently time out. Fixed in version 4.3.1.13.
      • [AER-6029] - (FABRIC) Load balance counter for send threads does not decrement correctly in certain rare circumstances. Fixed in version 4.3.1.13.
      • [AER-5997] - (MIGRATION) Rare race condition causes `migrate_signals_remaining` stat to underflow. Fixed in version 4.3.1.9.
      • [AER-5985] - (STORAGE) Improper handling of dropped keys when replicating or migrating records. Fixed in version 4.3.1.8.
      • [AER-5917] - (KVS) In non 'data-in-memory' namespaces, cannot add a stored key to an existing record. Fixed in version 4.3.0.4.
    • Enterprise Only
      • [AER-6195] - (MIGRATION) Rare race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.0.24.
      • [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.0.22.
      • [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item 'report-authentication' true. Fixed in version 4.5.0.21.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections. Fixed in version 4.5.0.19.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart. Fixed in version 4.5.0.15.
      • [AER-6090] - (SECURITY) Batch sub-transactions' digests are not logged in the 'report-data-op' audit trail. Fixed in version 4.5.0.14.
      • [AER-6075] - (XDR) Dynamically setting xdr context configuration items when configuration file has no xdr context causes crash. Fixed in version 4.5.0.13.
      • [AER-6069] - (SECURITY) Minor memory leak during LDAP login process. Fixed in version 4.5.0.12.
      • [AER-5965] - (CDT) For 'storage-engine device' namesp