Aerospike Server Community Edition 6.0.0.18

Description

• This General Availability release 6.0.0.18 contains all hotfixes deployed during the release candidate cycle.
• When upgrading to server version 6.0, you must either trim or wipe (zeroize) the Aerospike header on the devices. A modified record storage format was introduced by AER-6513, which adds protection against partially written records during an unclean shutdown.
• For upgrading, or the unlikely event of downgrading, please refer to Special Upgrades.
• BREAKING CHANGE: The truncate privilege is now a separate privilege and is no longer under write.
• The batch operations capability has been made comprehensive. We now fully support batch reads, writes, deletes, and UDF commands.
• The previously deprecated Predicate Expression API has been removed. Use Aerospike Filter Expressions (added in version 5.2).
• Service context configuration paxos-single-replica-limit has been removed.
• Configurations, Metrics, and Server Logs related to Scans are now referred to as Primary Index Queries (pi queries). For example, scan_basic_complete is now referred to as pi_query_long_basic_complete.
• 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:
  • query-show replaces query-list and the deprecated scan-show command.
  • query-abort replaces query-kill and the deprecated scan-abort command.
• The batch-without-digests configuration parameter has been removed.
• A number of Best Practices will be checked at startup. The Best Practices can be enforced by enabling the new enforce-best-practices configuration item.
• Several configuration parameters have been renamed or removed. Please refer to Config, Metrics, and Info Changes in Aerospike Database 6.0.
• Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.

Bug Fixes

• Enterprise, Federal & Community
  • [AER-6646] - (CDT) For data-in-memory namespaces, failing any but the first modify operation on a given bin within a transaction may leak memory.

Known Issues

• If you use ‘equality’ secondary index queries that return a small number of records, you may see a latency increase in server releases 6.0-6.2. A partial fix is included in server 6.3, and a complete fix for server 7.0.
• If your secondary index query only returns 0 records or 1 record, meaning that it is acting as a unique index, you should consider converting such a query to a get/exists operation by creating a self-managed reverse index (lookup table).
• Spark Connector version 3.5 starts using batch writes when possible, a feature which was introduced in Aerospike server version 6.0. Consult the Spark Connector rate limiting documentation before you upgrade the server. Pay attention to throttling write throughput, and use Spark Connector 3.5.5 or later, which fixes throttling behavior to conform to the aerospike.transaction.rate.
• Known Issues: Server

Updates

• aerospike-tools 8.0.4