Aerospike Server Community Edition 5.7.0.17
Description
- For upgrading, or the unlikely event of downgrading, please refer to Special Upgrades.
- The Predicate Expression API is obsolete. The Aerospike Server and Client have scheduled removal with our next major Aerospike Server release. Use Aerospike Filter Expressions (added in version 5.2).
- The
jobs
info command is now officially deprecated and will continue to be supported through a deprecation period, after which it will be removed.jobs
are now redundant with the new secondary index building methods and the following new info commands:scan-show
replacesscan-list
.query-show
replacesquery-list
.query-abort
replacesquery-kill
.
- The configuration parameter
batch-without-digests
, now defaults to true, is deprecated and will be removed in six months. Customers using clients older than a year (around the time of Server 4.9 which introducedbatch-without-digests
) will now have to explicitly set thebatch-without-digests
configuration item to false. - A number of
Best Practices
will be checked at startup. The Best Practices can be enforced by enabling the newenforce-best-practices
configuration item. - The security context configuration items
enable-security
andenable-ldap
have been removed. The Server will not start if eitherenable-security
orenable-ldap
is present in the configuration file. - Security will now be enabled simply by the presence of the security { } section in the configuration file. Similarly, LDAP will now be enabled simply by the presence of the ldap { } section within the security { } section of the configuration file.
- To use XDR with ACL
auth-mode
must be explicitly configured.- For more information please refer to: Securing with access control using PKI (versions 5.7+).
- We build on Red Hat Enterprise Linux (RHEL) 8 instead of CentOS 8 when creating rpm packages.
- For more information please refer to: CentOS Linux EOL.
- Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.
New Features
Improvements
Bug Fixes
- Enterprise & Community
- [AER-6526] - (SINDEX) Truncating a namespace or set with a secondary index, and more than 2 billion records per node, may overflow a garbage collection queue and crash.
- Enterprise Only
- [AER-6527] - (XDR) Dynamically removing seed nodes while trying to connect may cause connections to be skipped or cause a crash.