Aerospike Server Community Edition 5.0.0.30
Description
- Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
- In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if
forwardhas not been explicitly enabled. - Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
- In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if
- Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 can only connect to XDR destination clusters running versions 4.1 or newer.
- All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0.
- Aerospike Server version 5.0 will not form a cluster with version 4.8 nodes or earlier.
- When upgrading the Aerospike Server refer to the Special Upgrades documentation.
- The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
- ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
- For expirations,
nsup-periodmust be configured (new default is 0). - For evictions, the relevant
high-water-disk-pct/high-water-memory-pct/mounts-high-water-pctmust be configured (new defaults are 0). - For details refer to the
Namespace Retention Configurationdocumentation.
- For expirations,
- CentOS Linux 8 End of Life is scheduled for December 2021.
- For more information please refer to: FAQ - CentOS Project shifts focus to CentOS Stream
New Features
Improvements
Bug Fixes
- Enterprise & Community
- [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical.
- [AER-6402] - (SINDEX) When iterating through secondary indexes to adjust for changing list bin values, inactive indexes are incorrectly skipped, which may cause a crash.