Aerospike Database 6.1.0.13 Release Notes

For the complete documentation index see: llms.txt

All documentation pages available in markdown.

April 06, 2023 | Download

Bug Fixes

Enterprise, Federal & Community
- AER-6621 - (LOGGING) CDT operations resulting in “normal” errors ELEMENT_NOT_FOUND & ELEMENT_EXISTS are logged as warnings instead of detail.
- AER-6623 - (QUERY) For AP namespaces, queries may miss records during certain migration scenarios.
Enterprise & Federal Only
- AER-6620 - (KVS) For index-type flash namespaces, configuring index-stage-size 4G or larger may cause assertions or other bad symptoms on warm restart.
- AER-6622 - (SINDEX) When cool restarting data-in-memory namespaces, a secondary-indexed record which expires after startup but before being loaded into memory will assert.

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.13