# Aerospike Database 6.1.0.18 Release Notes

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

## Improvements

-   Enterprise & Federal Only
    
    -   AER-6656 - (TLS) Improved the handling of numerous new TLS connections when nodes join large clusters.

## Bug Fixes

-   Enterprise & Federal Only
    
    -   AER-6651 - (SINDEX) [`sindex-type pmem`](https://aerospike.com/docs/database/reference/config#namespace__sindex-type) context configuration items [`mounts-size-limit`](https://aerospike.com/docs/database/reference/config#namespace__mounts-size-limit) and [`mounts-high-water-pct`](https://aerospike.com/docs/database/reference/config#namespace__mounts-high-water-pct) should be dynamic.

## 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.18](https://aerospike.com/docs/database/reference/issues?search=6.1.0.18)
    

## Updates

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