# Aerospike Database 6.2.0 Release Notes

November 17, 2022  |  **[Download](https://aerospike.com/download/)**

## New in this version

### Features

Starting with Database 6.2.0, Aerospike Database supports 64-bit ARM processors compatible with the ARMv8.2-A instruction set (Neoverse N1 microarchitecture), such as AWS Graviton2 processors. This augments support for 64-bit Intel/AMD processors compatible with x86-64-v2 microarchitectures.

### Breaking changes

-   Removed support for Debian 9
-   Database 6.2.0 for ARM64 does not support LuaJit.
    -   FFI module is not present in Database 6.2.0.
    -   Aerospike Database 6.2.0 supports the standard Lua 5.1.0 interpreter.

::: caution
A new package naming convention will affect download automation for new versions of the [server](https://aerospike.com/docs/database/install/upgrade/standard#download-the-server-package), [tools](https://aerospike.com/docs/database/tools/install), [Prometheus Exporter](https://aerospike.com/docs/database/observe/monitor/install/linux), [C client](https://aerospike.com/docs/develop/client/c/install). Refer to the [Frequently Asked Questions](https://aerospike.com/docs/database/reference/faq) for details.
:::

## Prerequisites and notes

-   For upgrade instructions, refer to [Upgrade or Repair Server](https://aerospike.com/docs/database/install/upgrade)
-   For special upgrade instructions, refer to [Special Upgrades](https://aerospike.com/docs/database/advanced/special-upgrades)

## Product lifecycle updates

Long-term Support (LTS) releases are maintained and supported for 2.5 years (30 months). Interim releases are maintained and supported for 15 months. See [Platform support](https://aerospike.com/docs/database/reference/platform-support) for details.

## 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`.
-   See [Known issues for 6.2.0.0](https://aerospike.com/docs/database/reference/issues?search=6.2.0.0)