Skip to main content
We are excited to be a part of AWS re:Invent 2024. Visit us at booth #1844 in Las Vegas.More info
Loading

Aerospike Database Release Notes 6.1.0.11

March 08, 2023

Aerospike Database software version 6.1.0.11 is now available.

This release is a hotfix for Aerospike Database 6.1.

note

Federal Edition Only: This version and subsequent Database 6.1.0.x Debian package software files (.deb) and Red Hat Package Manager files (.rpm) are now GPG Signed.

Bug Fixes​

  • Enterprise, Federal & Community

    • [AER-6612] - (CDT) Writing an ordered map with a map index bigger than the content may corrupt the map.

    • [AER-6614] - (CDT) With result type EXISTS, a GET_ALL_BY_KEY_LIST operation on an ordered map always returns false.

    • [AER-6610] - (DEPLOYMENT) The Aerospike server may fail to start in some containers when the available CPUs are a proper subset of the actual CPUs.

    • [AER-6613] - (KVS) For single-bin, data-in-memory namespaces, writes using the delete-record operation may free the bin data twice and cause a crash.

    • [AER-6611] - (SINDEX) Dropping a secondary index on which there are active queries may cause an assertion or other bad symptoms.

Known Issues​

  • If you use equality secondary index queries that return a small number of records, you may see a latency increase in Database 6..0-6.2. The inline-short-queries configuration option provides a partial fix in Database 6.3, and a more advanced fix is scheduled for Database 6.4.

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

  • There is a possibility of partial de-duplicate (repeated records) in secondary index query (SI query) responses for SI queries that use list or map type secondary indexes. Any record that satisfies such a query at least once will be included, but it is possible and normal to see a record more than once.

  • Known issues for 6.1.0.11

Updates​

Aerospike Tools 8.0.4

Last updated on