---
title: "Aerospike Database 6.1.0.12 Release Notes"
description: "Release notes for Aerospike Database 6.1.0.12, detailing bug fixes and known issues."
---

# Aerospike Database 6.1.0.12 Release Notes

> For the complete documentation index see: [llms.txt](https://aerospike.com/docs/llms.txt)
> 
> All documentation pages available in markdown.

March 16, 2023  |  **[Download](https://aerospike.com/download/)**

::: note
Community, Enterprise, & Federal Edition: This version and subsequent Database 6.1.0.x Debian package files (_.deb) and Red Hat Package Manager files (_.rpm) are now GPG Signed.
:::

## 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`](https://aerospike.com/docs/database/reference/config#namespace__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.
        

## 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.0-6.2.0. The [`inline-short-queries`](https://aerospike.com/docs/database/reference/config#namespace__inline-short-queries) configuration option provides a partial fix in Database 6.3.0, and a more advanced fix is scheduled for Database 6.4.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 Database 6.0.0. Consult the Spark Connector [rate limiting documentation](https://aerospike.com/docs/connectors/spark/rate-limiting#set-rate-quotas-in-the-spark-application) 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.12](https://aerospike.com/docs/database/reference/issues?search=6.1.0.12)
    

## Updates

[Aerospike Tools 8.0.4](https://aerospike.com/docs/database/tools/release-notes/#tools-804)