Aerospike Server 4.8.0.1 (December 12, 2019)

Aerospike Server version 4.8.0.1 was released on December 12, 2019.

This major release contains New Features, Improvements and a Bug Fix.

  • 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
    • Records containing certain Complex Data Type (CDT) issues, for example improperly sorted ordered lists, created with Aerospike Server versions prior to 4.6 could be incompatible with server versions 4.6 or later due to stricter CDT validation. This could also block XDR shipping. A tool to identify and/or fix such records will be made available.

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.
© 2015 Copyright Aerospike, Inc. | All rights reserved. Creators of the Aerospike Database.