Aerospike Database 6.1.0.12 Release Notes

For the complete documentation index see: llms.txt

All documentation pages available in markdown.

March 16, 2023 | Download

Bug Fixes

Enterprise, Federal & Community
- AER-6617 - (DEPLOYMENT) The Aerospike server may fail to start in containers with cgroup v1 when the available CPUs are a proper subset of the actual CPUs.
- AER-6618 - (EXPRESSIONS) Deleting a bin using a write operation expression will cause a crash.
- AER-6615 - (SMD) A module that is continually retransmitting may block another module’s ‘set’ operations.
Enterprise & Federal Only
- AER-6619 - (BALANCE) For strong-consistency namespaces, a stale appeal acknowledgement may cause a crash.
- AER-6616 - (XDR) Removing connector seed nodes while a DC is disconnected may cause an assertion on reconnection.

If you use equality secondary index queries that return a small number of records, you may see a latency increase in Database 6.0.0 and later. The inline-short-queries configuration option provides a partial fix in Database 6.3.0.

Note
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 Database 6.0.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.
When using range queries on List or Map secondary indexes, records can be returned multiple times if the collection contains multiple values that fall within the range. Every matching record is included at least once, so your application must handle deduplication of the results.
Known issues for 6.1.0.12