Aerospike Server FE Release Notes

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/7.1.0.4-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 11.0.2

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/7.1.0.3-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 11.0.2

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/7.1.0.2-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 11.0.1

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/7.1.0.1-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 11.0.1

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/7.1-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 11.0.0

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/7.0.0.13-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 10.2.1

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/7.0.0.12-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 10.2.1

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/7.0.0.11-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 10.2.1

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/7.0.0.10-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 10.2.1

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/7.0.0.9-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 10.2.1

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/7.0.0.8-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 10.2.1

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/7.0.0.7-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 10.2.1

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/7.0.0.6-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 10.2.1

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/7.0.0.5-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 10.2.1

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/7.0.0.4-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 10.2.1

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/7.0.0.3-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 10.0.1

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/7.0.0.2-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 10.0.1

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/7.0-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 10.0.0

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.4.0.21-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 10.0.0

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.4.0.20-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 10.0.0

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.4.0.19-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 10.0.0

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.4.0.18-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 10.0.0

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.4.0.16-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 10.0.0

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.4.0.15-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 10.0.0

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.4.0.14-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 10.0.0

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.4.0.13-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 10.0.0

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.4.0.12-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 10.0.0

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.4.0.11-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 10.0.0

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.4.0.10-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 10.0.0

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.4.0.9-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 10.0.0

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.4.0.7-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 10.0.0

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.4.0.6-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 9.2.1

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.4.0.4-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 9.1.0

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.4.0.3-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 9.1.0

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.4.0.2-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 9.1.0

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.4.0.1-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 9.0.0

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.4-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 9.0.0

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.3.0.26-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.5.1

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.3.0.25-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.5.1

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.3.0.24-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.5.1

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.3.0.23-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.5.1

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.3.0.22-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.5.1

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.3.0.21-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.5.1

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.3.0.20-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.5.1

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.3.0.19-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.5.1

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.3.0.18-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.5.1

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.3.0.17-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.5.1

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.3.0.16-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.5.1

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.3.0.15-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.5.1

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.3.0.13-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.5.1

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.3.0.12-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.5.1

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.3.0.10-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.5.1

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.3.0.9-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.5.1

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.3.0.8-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.5.1

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.3.0.7-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.5.1

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.3.0.6-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.5.1

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.3.0.5-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.4.0

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.3.0.4-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.3.0

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.3.0.3-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.3.0

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.3.0.2-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.3.0

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.3.0.1-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.2.0

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.3-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.2.0

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.2.0.28-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.1.0

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.2.0.27-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.1.0

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.2.0.26-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.1.0

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.2.0.25-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.1.0

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.2.0.24-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.1.0

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.2.0.23-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.1.0

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.2.0.22-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.1.0

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.2.0.20-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.1.0

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.2.0.19-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.1.0

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.2.0.17-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.1.0

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.2.0.16-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.1.0

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.2.0.15-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.1.0

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.2.0.14-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.1.0

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.2.0.13-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.1.0

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.2.0.12-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.1.0

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.2.0.11-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.1.0

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.2.0.10-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.1.0

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.2.0.9-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.1.0

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.2.0.8-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.1.0

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.2.0.7-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.1.0

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.2.0.6-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.1.0

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.2.0.3-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.1.0

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.2.0.2-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.0.4

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.2.0.1-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.0.3

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.2-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.0.2

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.1.0.38-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.0.4

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.1.0.37-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.0.4

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.1.0.36-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.0.4

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.1.0.35-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.0.4

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.1.0.34-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.0.4

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.1.0.33-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.0.4

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.1.0.32-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.0.4

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.1.0.31-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.0.4

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.1.0.30-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.0.4

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.1.0.29-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.0.4

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.1.0.28-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.0.4

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.1.0.27-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.0.4

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.1.0.25-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.0.4

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.1.0.24-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.0.4

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.1.0.22-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.0.4

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.1.0.21-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.0.4

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.1.0.20-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.0.4

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.1.0.19-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.0.4

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.1.0.18-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.0.4

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.1.0.17-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.0.4

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.1.0.16-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.0.4

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.1.0.15-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.0.4

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.1.0.14-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.0.4

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.1.0.13-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.0.4

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.1.0.12-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.0.4

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.1.0.11-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.0.4

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.1.0.8-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.0.4

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.1.0.7-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.0.4

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.1.0.6-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.0.3

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.1.0.5-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 8.0.3

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.1.0.4-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 7.3.1

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.1.0.3-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 7.3.1

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.1.0.2-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 7.2.1

• Release Notes are now available here: https://docs.aerospike.com/reference/release_notes/server/6.1.0.1-server-release-notes

Known Issues

• Known Issues: Server

Updates

• aerospike-tools 7.2.0

• This General Availability release 6.0.0.22 contains all hotfixes deployed during the release candidate cycle.
• When upgrading to server version 6.0, you must either trim or wipe (zeroize) the Aerospike header on the devices. A modified record storage format was introduced by AER-6513, which adds protection against partially written records during an unclean shutdown.
• For upgrading, or the unlikely event of downgrading, please refer to Special Upgrades.
• BREAKING CHANGE: The truncate privilege is now a separate privilege and is no longer under write.
• The batch operations capability has been made comprehensive. We now fully support batch reads, writes, deletes, and UDF commands.
• The previously deprecated Predicate Expression API has been removed. Use Aerospike Filter Expressions (added in version 5.2).
• Service context configuration paxos-single-replica-limit has been removed.
• Configurations, Metrics, and Server Logs related to Scans are now referred to as Primary Index Queries (pi queries). For example, scan_basic_complete is now referred to as pi_query_long_basic_complete.
• The jobs info command is now officially deprecated and will continue to be supported through a deprecation period, after which it will be removed. jobs are now redundant with the new secondary index building methods and the following new info commands:
  • query-show replaces query-list and the deprecated scan-show command.
  • query-abort replaces query-kill and the deprecated scan-abort command.
• The batch-without-digests configuration parameter has been removed.
• A number of Best Practices will be checked at startup. The Best Practices can be enforced by enabling the new enforce-best-practices configuration item.
• Several configuration parameters have been renamed or removed. Please refer to Config, Metrics, and Info Changes in Aerospike Database 6.0.
• Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.

Bug Fixes

• Enterprise & Federal Only
  • [AER-6665] - (XDR) Batched durable deletes will cause a crash if DC namespace context configuration item ship-bin-luts is set.

Known Issues

• If you use equality secondary index queries that return a small number of records, you may see a latency increase in server releases 6.0-6.2. The inline-short-queries configuration option provides a partial fix in server 6.3, and a more advanced fix is scheduled for server 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 server version 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.
• Known Issues: Server

Updates

• aerospike-tools 8.0.4

• This General Availability release 6.0.0.21 contains all hotfixes deployed during the release candidate cycle.
• When upgrading to server version 6.0, you must either trim or wipe (zeroize) the Aerospike header on the devices. A modified record storage format was introduced by AER-6513, which adds protection against partially written records during an unclean shutdown.
• For upgrading, or the unlikely event of downgrading, please refer to Special Upgrades.
• BREAKING CHANGE: The truncate privilege is now a separate privilege and is no longer under write.
• The batch operations capability has been made comprehensive. We now fully support batch reads, writes, deletes, and UDF commands.
• The previously deprecated Predicate Expression API has been removed. Use Aerospike Filter Expressions (added in version 5.2).
• Service context configuration paxos-single-replica-limit has been removed.
• Configurations, Metrics, and Server Logs related to Scans are now referred to as Primary Index Queries (pi queries). For example, scan_basic_complete is now referred to as pi_query_long_basic_complete.
• The jobs info command is now officially deprecated and will continue to be supported through a deprecation period, after which it will be removed. jobs are now redundant with the new secondary index building methods and the following new info commands:
  • query-show replaces query-list and the deprecated scan-show command.
  • query-abort replaces query-kill and the deprecated scan-abort command.
• The batch-without-digests configuration parameter has been removed.
• A number of Best Practices will be checked at startup. The Best Practices can be enforced by enabling the new enforce-best-practices configuration item.
• Several configuration parameters have been renamed or removed. Please refer to Config, Metrics, and Info Changes in Aerospike Database 6.0.
• Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.

Bug Fixes

• Enterprise, Federal & Community
  • [AER-6662]- (SMD) Internally retried SMD events are not thread safe at shutdown or with certain info commands.

Known Issues

• If you use equality secondary index queries that return a small number of records, you may see a latency increase in server releases 6.0-6.2. The inline-short-queries configuration option provides a partial fix in server 6.3, and a more advanced fix is scheduled for server 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 server version 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.
• Known Issues: Server

Updates

• aerospike-tools 8.0.4

• This General Availability release 6.0.0.20 contains all hotfixes deployed during the release candidate cycle.
• When upgrading to server version 6.0, you must either trim or wipe (zeroize) the Aerospike header on the devices. A modified record storage format was introduced by AER-6513, which adds protection against partially written records during an unclean shutdown.
• For upgrading, or the unlikely event of downgrading, please refer to Special Upgrades.
• BREAKING CHANGE: The truncate privilege is now a separate privilege and is no longer under write.
• The batch operations capability has been made comprehensive. We now fully support batch reads, writes, deletes, and UDF commands.
• The previously deprecated Predicate Expression API has been removed. Use Aerospike Filter Expressions (added in version 5.2).
• Service context configuration paxos-single-replica-limit has been removed.
• Configurations, Metrics, and Server Logs related to Scans are now referred to as Primary Index Queries (pi queries). For example, scan_basic_complete is now referred to as pi_query_long_basic_complete.
• The jobs info command is now officially deprecated and will continue to be supported through a deprecation period, after which it will be removed. jobs are now redundant with the new secondary index building methods and the following new info commands:
  • query-show replaces query-list and the deprecated scan-show command.
  • query-abort replaces query-kill and the deprecated scan-abort command.
• The batch-without-digests configuration parameter has been removed.
• A number of Best Practices will be checked at startup. The Best Practices can be enforced by enabling the new enforce-best-practices configuration item.
• Several configuration parameters have been renamed or removed. Please refer to Config, Metrics, and Info Changes in Aerospike Database 6.0.
• Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.

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 context configuration items mounts-size-limit and 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 server releases 6.0-6.2. The inline-short-queries configuration option provides a partial fix in server 6.3, and a more advanced fix is scheduled for server 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 server version 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.
• Known Issues: Server

Updates

• aerospike-tools 8.0.4

• This General Availability release 6.0.0.19 contains all hotfixes deployed during the release candidate cycle.
• When upgrading to server version 6.0, you must either trim or wipe (zeroize) the Aerospike header on the devices. A modified record storage format was introduced by AER-6513, which adds protection against partially written records during an unclean shutdown.
• For upgrading, or the unlikely event of downgrading, please refer to Special Upgrades.
• BREAKING CHANGE: The truncate privilege is now a separate privilege and is no longer under write.
• The batch operations capability has been made comprehensive. We now fully support batch reads, writes, deletes, and UDF commands.
• The previously deprecated Predicate Expression API has been removed. Use Aerospike Filter Expressions (added in version 5.2).
• Service context configuration paxos-single-replica-limit has been removed.
• Configurations, Metrics, and Server Logs related to Scans are now referred to as Primary Index Queries (pi queries). For example, scan_basic_complete is now referred to as pi_query_long_basic_complete.
• The jobs info command is now officially deprecated and will continue to be supported through a deprecation period, after which it will be removed. jobs are now redundant with the new secondary index building methods and the following new info commands:
  • query-show replaces query-list and the deprecated scan-show command.
  • query-abort replaces query-kill and the deprecated scan-abort command.
• The batch-without-digests configuration parameter has been removed.
• A number of Best Practices will be checked at startup. The Best Practices can be enforced by enabling the new enforce-best-practices configuration item.
• Several configuration parameters have been renamed or removed. Please refer to Config, Metrics, and Info Changes in Aerospike Database 6.0.
• Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.

Improvements

• Enterprise & Federal Only
  • [AER-6645] - (XDR) Time out and reset connections based on request latency instead of inactivity.

Known Issues

• If you use equality secondary index queries that return a small number of records, you may see a latency increase in server releases 6.0-6.2. The inline-short-queries configuration option provides a partial fix in server 6.3, and a more advanced fix is scheduled for server 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 server version 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.
• Known Issues: Server

Updates

• aerospike-tools 8.0.4

• This General Availability release 6.0.0.18 contains all hotfixes deployed during the release candidate cycle.
• When upgrading to server version 6.0, you must either trim or wipe (zeroize) the Aerospike header on the devices. A modified record storage format was introduced by AER-6513, which adds protection against partially written records during an unclean shutdown.
• For upgrading, or the unlikely event of downgrading, please refer to Special Upgrades.
• BREAKING CHANGE: The truncate privilege is now a separate privilege and is no longer under write.
• The batch operations capability has been made comprehensive. We now fully support batch reads, writes, deletes, and UDF commands.
• The previously deprecated Predicate Expression API has been removed. Use Aerospike Filter Expressions (added in version 5.2).
• Service context configuration paxos-single-replica-limit has been removed.
• Configurations, Metrics, and Server Logs related to Scans are now referred to as Primary Index Queries (pi queries). For example, scan_basic_complete is now referred to as pi_query_long_basic_complete.
• The jobs info command is now officially deprecated and will continue to be supported through a deprecation period, after which it will be removed. jobs are now redundant with the new secondary index building methods and the following new info commands:
  • query-show replaces query-list and the deprecated scan-show command.
  • query-abort replaces query-kill and the deprecated scan-abort command.
• The batch-without-digests configuration parameter has been removed.
• A number of Best Practices will be checked at startup. The Best Practices can be enforced by enabling the new enforce-best-practices configuration item.
• Several configuration parameters have been renamed or removed. Please refer to Config, Metrics, and Info Changes in Aerospike Database 6.0.
• Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.

Bug Fixes

• Enterprise, Federal & Community
  • [AER-6646] - (CDT) For data-in-memory namespaces, failing any but the first modify operation on a given bin within a transaction may leak memory.

Known Issues

• If you use equality secondary index queries that return a small number of records, you may see a latency increase in server releases 6.0-6.2. The inline-short-queries configuration option provides a partial fix in server 6.3, and a more advanced fix is scheduled for server 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 server version 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.
• Known Issues: Server

Updates

• aerospike-tools 8.0.4

• This General Availability release 6.0.0.17 contains all hotfixes deployed during the release candidate cycle.
• When upgrading to server version 6.0, you must either trim or wipe (zeroize) the Aerospike header on the devices. A modified record storage format was introduced by AER-6513, which adds protection against partially written records during an unclean shutdown.
• For upgrading, or the unlikely event of downgrading, please refer to Special Upgrades.
• BREAKING CHANGE: The truncate privilege is now a separate privilege and is no longer under write.
• The batch operations capability has been made comprehensive. We now fully support batch reads, writes, deletes, and UDF commands.
• The previously deprecated Predicate Expression API has been removed. Use Aerospike Filter Expressions (added in version 5.2).
• Service context configuration paxos-single-replica-limit has been removed.
• Configurations, Metrics, and Server Logs related to Scans are now referred to as Primary Index Queries (pi queries). For example, scan_basic_complete is now referred to as pi_query_long_basic_complete.
• The jobs info command is now officially deprecated and will continue to be supported through a deprecation period, after which it will be removed. jobs are now redundant with the new secondary index building methods and the following new info commands:
  • query-show replaces query-list and the deprecated scan-show command.
  • query-abort replaces query-kill and the deprecated scan-abort command.
• The batch-without-digests configuration parameter has been removed.
• A number of Best Practices will be checked at startup. The Best Practices can be enforced by enabling the new enforce-best-practices configuration item.
• Several configuration parameters have been renamed or removed. Please refer to Config, Metrics, and Info Changes in Aerospike Database 6.0.
• Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.

Bug Fixes

• Enterprise, Federal & Community
  • [AER-6639] - (KVS) The system_free_mem... statistics incorrectly exclude available, lazily freed pages.
• Enterprise & Federal Only
  • [AER-6641] - (STORAGE) For strong-consistency namespaces, removing a device fails to flag the node as untrusted when it restarts.
  • [AER-6638] - (XDR) Removing connector seed nodes while connecting to a DC may cause an assertion.

Known Issues

• If you use equality secondary index queries that return a small number of records, you may see a latency increase in server releases 6.0-6.2. The inline-short-queries configuration option provides a partial fix in server 6.3, and a more advanced fix is scheduled for server 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 server version 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.
• Known Issues: Server

Updates

• aerospike-tools 8.0.4

• This General Availability release 6.0.0.16 contains all hotfixes deployed during the release candidate cycle.
• When upgrading to server version 6.0, you must either trim or wipe (zeroize) the Aerospike header on the devices. A modified record storage format was introduced by AER-6513, which adds protection against partially written records during an unclean shutdown.
• For upgrading, or the unlikely event of downgrading, please refer to Special Upgrades.
• BREAKING CHANGE: The truncate privilege is now a separate privilege and is no longer under write.
• The batch operations capability has been made comprehensive. We now fully support batch reads, writes, deletes, and UDF commands.
• The previously deprecated Predicate Expression API has been removed. Use Aerospike Filter Expressions (added in version 5.2).
• Service context configuration paxos-single-replica-limit has been removed.
• Configurations, Metrics, and Server Logs related to Scans are now referred to as Primary Index Queries (pi queries). For example, scan_basic_complete is now referred to as pi_query_long_basic_complete.
• The jobs info command is now officially deprecated and will continue to be supported through a deprecation period, after which it will be removed. jobs are now redundant with the new secondary index building methods and the following new info commands:
  • query-show replaces query-list and the deprecated scan-show command.
  • query-abort replaces query-kill and the deprecated scan-abort command.
• The batch-without-digests configuration parameter has been removed.
• A number of Best Practices will be checked at startup. The Best Practices can be enforced by enabling the new enforce-best-practices configuration item.
• Several configuration parameters have been renamed or removed. Please refer to Config, Metrics, and Info Changes in Aerospike Database 6.0.
• Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.

Bug Fixes

• Enterprise, Federal & Community
  • [AER-6627] - (AGGREGATION) A range query on a list or map secondary index can overflow a record's ref-count and assert.
• Enterprise & Federal Only
  • [AER-6628] - (KVS) For index-type flash namespaces, configuring index-stage-size 4G or larger will cause warm restart to be abnormally slow.

Known Issues

• If you use equality secondary index queries that return a small number of records, you may see a latency increase in server releases 6.0-6.2. The inline-short-queries configuration option provides a partial fix in server 6.3, and a more advanced fix is scheduled for server 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 server version 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.
• Known Issues: Server

Updates

• aerospike-tools 8.0.4

• This General Availability release 6.0.0.15 contains all hotfixes deployed during the release candidate cycle.
• When upgrading to server version 6.0, you must either trim or wipe (zeroize) the Aerospike header on the devices. A modified record storage format was introduced by AER-6513, which adds protection against partially written records during an unclean shutdown.
• For upgrading, or the unlikely event of downgrading, please refer to Special Upgrades.
• BREAKING CHANGE: The truncate privilege is now a separate privilege and is no longer under write.
• The batch operations capability has been made comprehensive. We now fully support batch reads, writes, deletes, and UDF commands.
• The previously deprecated Predicate Expression API has been removed. Use Aerospike Filter Expressions (added in version 5.2).
• Service context configuration paxos-single-replica-limit has been removed.
• Configurations, Metrics, and Server Logs related to Scans are now referred to as Primary Index Queries (pi queries). For example, scan_basic_complete is now referred to as pi_query_long_basic_complete.
• The jobs info command is now officially deprecated and will continue to be supported through a deprecation period, after which it will be removed. jobs are now redundant with the new secondary index building methods and the following new info commands:
  • query-show replaces query-list and the deprecated scan-show command.
  • query-abort replaces query-kill and the deprecated scan-abort command.
• The batch-without-digests configuration parameter has been removed.
• A number of Best Practices will be checked at startup. The Best Practices can be enforced by enabling the new enforce-best-practices configuration item.
• Several configuration parameters have been renamed or removed. Please refer to Config, Metrics, and Info Changes in Aerospike Database 6.0.
• Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.

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.

Known Issues

• If you use equality secondary index queries that return a small number of records, you may see a latency increase in server releases 6.0-6.2. The inline-short-queries configuration option provides a partial fix in server 6.3, and a more advanced fix is scheduled for server 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 server version 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.
• Known Issues: Server

Updates

• aerospike-tools 8.0.4

• This General Availability release 6.0.0.14 contains all hotfixes deployed during the release candidate cycle.
• When upgrading to server version 6.0, you must either trim or wipe (zeroize) the Aerospike header on the devices. A modified record storage format was introduced by AER-6513, which adds protection against partially written records during an unclean shutdown.
• For upgrading, or the unlikely event of downgrading, please refer to Special Upgrades.
• BREAKING CHANGE: The truncate privilege is now a separate privilege and is no longer under write.
• The batch operations capability has been made comprehensive. We now fully support batch reads, writes, deletes, and UDF commands.
• The previously deprecated Predicate Expression API has been removed. Use Aerospike Filter Expressions (added in version 5.2).
• Service context configuration paxos-single-replica-limit has been removed.
• Configurations, Metrics, and Server Logs related to Scans are now referred to as Primary Index Queries (pi queries). For example, scan_basic_complete is now referred to as pi_query_long_basic_complete.
• The jobs info command is now officially deprecated and will continue to be supported through a deprecation period, after which it will be removed. jobs are now redundant with the new secondary index building methods and the following new info commands:
  • query-show replaces query-list and the deprecated scan-show command.
  • query-abort replaces query-kill and the deprecated scan-abort command.
• The batch-without-digests configuration parameter has been removed.
• A number of Best Practices will be checked at startup. The Best Practices can be enforced by enabling the new enforce-best-practices configuration item.
• Several configuration parameters have been renamed or removed. Please refer to Config, Metrics, and Info Changes in Aerospike Database 6.0.
• Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.
• Community, Enterprise, & Federal Editions: This version and subsequent server 6.0.0.x Debian package software 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 via 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 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 server releases 6.0-6.2. The inline-short-queries configuration option provides a partial fix in server 6.3, and a more advanced fix is scheduled for server 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 server version 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.
• Known Issues: Server

Updates

• aerospike-tools 8.0.4

• This General Availability release 6.0.0.13 contains all hotfixes deployed during the release candidate cycle.
• When upgrading to server version 6.0, you must either trim or wipe (zeroize) the Aerospike header on the devices. A modified record storage format was introduced by AER-6513, which adds protection against partially written records during an unclean shutdown.
• For upgrading, or the unlikely event of downgrading, please refer to Special Upgrades.
• BREAKING CHANGE: The truncate privilege is now a separate privilege and is no longer under write.
• The batch operations capability has been made comprehensive. We now fully support batch reads, writes, deletes, and UDF commands.
• The previously deprecated Predicate Expression API has been removed. Use Aerospike Filter Expressions (added in version 5.2).
• Service context configuration paxos-single-replica-limit has been removed.
• Configurations, Metrics, and Server Logs related to Scans are now referred to as Primary Index Queries (pi queries). For example, scan_basic_complete is now referred to as pi_query_long_basic_complete.
• The jobs info command is now officially deprecated and will continue to be supported through a deprecation period, after which it will be removed. jobs are now redundant with the new secondary index building methods and the following new info commands:
  • query-show replaces query-list and the deprecated scan-show command.
  • query-abort replaces query-kill and the deprecated scan-abort command.
• The batch-without-digests configuration parameter has been removed.
• A number of Best Practices will be checked at startup. The Best Practices can be enforced by enabling the new enforce-best-practices configuration item.
• Several configuration parameters have been renamed or removed. Please refer to Config, Metrics, and Info Changes in Aerospike Database 6.0.
• Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.
• Federal Edition Only: This version and subsequent server 6.0.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-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.

Known Issues

• If you use equality secondary index queries that return a small number of records, you may see a latency increase in server releases 6.0-6.2. The inline-short-queries configuration option provides a partial fix in server 6.3, and a more advanced fix is scheduled for server 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 server version 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.
• Known Issues: Server

Updates

• aerospike-tools 8.0.4

• This General Availability release 6.0.0.11 contains all hotfixes deployed during the release candidate cycle.
• When upgrading to server version 6.0, you must either trim or wipe (zeroize) the Aerospike header on the devices. A modified record storage format was introduced by AER-6513, which adds protection against partially written records during an unclean shutdown.
• For upgrading, or the unlikely event of downgrading, please refer to Special Upgrades.
• BREAKING CHANGE: The truncate privilege is now a separate privilege and is no longer under write.
• The batch operations capability has been made comprehensive. We now fully support batch reads, writes, deletes, and UDF commands.
• The previously deprecated Predicate Expression API has been removed. Use Aerospike Filter Expressions (added in version 5.2).
• Service context configuration paxos-single-replica-limit has been removed.
• Configurations, Metrics, and Server Logs related to Scans are now referred to as Primary Index Queries (pi queries). For example, scan_basic_complete is now referred to as pi_query_long_basic_complete.
• The jobs info command is now officially deprecated and will continue to be supported through a deprecation period, after which it will be removed. jobs are now redundant with the new secondary index building methods and the following new info commands:
  • query-show replaces query-list and the deprecated scan-show command.
  • query-abort replaces query-kill and the deprecated scan-abort command.
• The batch-without-digests configuration parameter has been removed.
• A number of Best Practices will be checked at startup. The Best Practices can be enforced by enabling the new enforce-best-practices configuration item.
• Several configuration parameters have been renamed or removed. Please refer to Config, Metrics, and Info Changes in Aerospike Database 6.0.
• Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.

Bug Fixes

• Enterprise, Federal & Community
  • [AER-6601] - (CLUSTERING) When a node fails to cluster due to a cluster size limit, it leaks memory.
  • [AER-6597] - (QUERY) A secondary index query may return incorrect results if the bin type changes from CDT to non-CDT during the query.

Known Issues

• If you use equality secondary index queries that return a small number of records, you may see a latency increase in server releases 6.0-6.2. The inline-short-queries configuration option provides a partial fix in server 6.3, and a more advanced fix is scheduled for server 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 server version 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.
• Known Issues: Server

Updates

• aerospike-tools 8.0.4

• This General Availability release 6.0.0.10 contains all hotfixes deployed during the release candidate cycle.
• When upgrading to server version 6.0, you must either trim or wipe (zeroize) the Aerospike header on the devices. A modified record storage format was introduced by AER-6513, which adds protection against partially written records during an unclean shutdown.
• For upgrading, or the unlikely event of downgrading, please refer to Special Upgrades.
• BREAKING CHANGE: The truncate privilege is now a separate privilege and is no longer under write.
• The batch operations capability has been made comprehensive. We now fully support batch reads, writes, deletes, and UDF commands.
• The previously deprecated Predicate Expression API has been removed. Use Aerospike Filter Expressions (added in version 5.2).
• Service context configuration paxos-single-replica-limit has been removed.
• Configurations, Metrics, and Server Logs related to Scans are now referred to as Primary Index Queries (pi queries). For example, scan_basic_complete is now referred to as pi_query_long_basic_complete.
• The jobs info command is now officially deprecated and will continue to be supported through a deprecation period, after which it will be removed. jobs are now redundant with the new secondary index building methods and the following new info commands:
  • query-show replaces query-list and the deprecated scan-show command.
  • query-abort replaces query-kill and the deprecated scan-abort command.
• The batch-without-digests configuration parameter has been removed.
• A number of Best Practices will be checked at startup. The Best Practices can be enforced by enabling the new enforce-best-practices configuration item.
• Several configuration parameters have been renamed or removed. Please refer to Config, Metrics, and Info Changes in Aerospike Database 6.0.
• Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.

Improvements

• Enterprise, Federal & Community
  • [TOOLS-2286] - (ASADM) Bundle asadm with Python 3.10.

Known Issues

• If you use equality secondary index queries that return a small number of records, you may see a latency increase in server releases 6.0-6.2. The inline-short-queries configuration option provides a partial fix in server 6.3, and a more advanced fix is scheduled for server 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 server version 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.
• Known Issues: Server

Updates

• aerospike-tools 8.0.4

• This General Availability release 6.0.0.9 contains all hotfixes deployed during the release candidate cycle.
• When upgrading to server version 6.0, you must either trim or wipe (zeroize) the Aerospike header on the devices. A modified record storage format was introduced by AER-6513, which adds protection against partially written records during an unclean shutdown.
• For upgrading, or the unlikely event of downgrading, please refer to Special Upgrades.
• BREAKING CHANGE: The truncate privilege is now a separate privilege and is no longer under write.
• The batch operations capability has been made comprehensive. We now fully support batch reads, writes, deletes, and UDF commands.
• The previously deprecated Predicate Expression API has been removed. Use Aerospike Filter Expressions (added in version 5.2).
• Service context configuration paxos-single-replica-limit has been removed.
• Configurations, Metrics, and Server Logs related to Scans are now referred to as Primary Index Queries (pi queries). For example, scan_basic_complete is now referred to as pi_query_long_basic_complete.
• The jobs info command is now officially deprecated and will continue to be supported through a deprecation period, after which it will be removed. jobs are now redundant with the new secondary index building methods and the following new info commands:
  • query-show replaces query-list and the deprecated scan-show command.
  • query-abort replaces query-kill and the deprecated scan-abort command.
• The batch-without-digests configuration parameter has been removed.
• A number of Best Practices will be checked at startup. The Best Practices can be enforced by enabling the new enforce-best-practices configuration item.
• Several configuration parameters have been renamed or removed. Please refer to Config, Metrics, and Info Changes in Aerospike Database 6.0.
• Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.

Improvements

• Enterprise, Federal & Community
  • [AER-6581] - (LOGGING) Changed logging level for 'starting/finished aggregation query job...' messages from info to debug.

Bug Fixes

• Enterprise, Federal & Community
  • [AER-6580] - (SINDEX) Deleting an indexed list or map containing multiple elements with the same value may leave inaccessible keys in the secondary index.
• Enterprise & Federal Only
  • [AER-6582] - (XDR) Setting DC context configuration item tls-name after adding seed nodes which require it may cause a crash.

Known Issues

• If you use equality secondary index queries that return a small number of records, you may see a latency increase in server releases 6.0-6.2. The inline-short-queries configuration option provides a partial fix in server 6.3, and a more advanced fix is scheduled for server 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 server version 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.
• Known Issues: Server

Updates

• aerospike-tools 8.0.3

• This General Availability release 6.0.0.8 contains all hotfixes deployed during the release candidate cycle.
• When upgrading to server version 6.0, you must either trim or wipe (zeroize) the Aerospike header on the devices. A modified record storage format was introduced by AER-6513, which adds protection against partially written records during an unclean shutdown.
• For upgrading, or the unlikely event of downgrading, please refer to Special Upgrades.
• BREAKING CHANGE: The truncate privilege is now a separate privilege and is no longer under write.
• The batch operations capability has been made comprehensive. We now fully support batch reads, writes, deletes, and UDF commands.
• The previously deprecated Predicate Expression API has been removed. Use Aerospike Filter Expressions (added in version 5.2).
• Service context configuration paxos-single-replica-limit has been removed.
• Configurations, Metrics, and Server Logs related to Scans are now referred to as Primary Index Queries (pi queries). For example, scan_basic_complete is now referred to as pi_query_long_basic_complete.
• The jobs info command is now officially deprecated and will continue to be supported through a deprecation period, after which it will be removed. jobs are now redundant with the new secondary index building methods and the following new info commands:
  • query-show replaces query-list and the deprecated scan-show command.
  • query-abort replaces query-kill and the deprecated scan-abort command.
• The batch-without-digests configuration parameter has been removed.
• A number of Best Practices will be checked at startup. The Best Practices can be enforced by enabling the new enforce-best-practices configuration item.
• Several configuration parameters have been renamed or removed. Please refer to Config, Metrics, and Info Changes in Aerospike Database 6.0.
• Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.

Bug Fixes

• Enterprise, Federal & Community
  • [AER-6576] - (SINDEX) Race between garbage collection and update of a secondary index entry may result in the erroneous removal of the entry.
• Enterprise & Federal Only
  • [AER-6572] - (XDR) Not setting DC context configuration item auth-user when auth-mode requires it will cause a crash.

Known Issues

• If you use equality secondary index queries that return a small number of records, you may see a latency increase in server releases 6.0-6.2. The inline-short-queries configuration option provides a partial fix in server 6.3, and a more advanced fix is scheduled for server 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 server version 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.
• Known Issues: Server

Updates

• aerospike-tools 7.3.1

• This General Availability release 6.0.0.7 contains all hotfixes deployed during the release candidate cycle.
• When upgrading to server version 6.0, you must either trim or wipe (zeroize) the Aerospike header on the devices. A modified record storage format was introduced by AER-6513, which adds protection against partially written records during an unclean shutdown.
• For upgrading, or the unlikely event of downgrading, please refer to Special Upgrades.
• BREAKING CHANGE: The truncate privilege is now a separate privilege and is no longer under write.
• The batch operations capability has been made comprehensive. We now fully support batch reads, writes, deletes, and UDF commands.
• The previously deprecated Predicate Expression API has been removed. Use Aerospike Filter Expressions (added in version 5.2).
• Service context configuration paxos-single-replica-limit has been removed.
• Configurations, Metrics, and Server Logs related to Scans are now referred to as Primary Index Queries (pi queries). For example, scan_basic_complete is now referred to as pi_query_long_basic_complete.
• The jobs info command is now officially deprecated and will continue to be supported through a deprecation period, after which it will be removed. jobs are now redundant with the new secondary index building methods and the following new info commands:
  • query-show replaces query-list and the deprecated scan-show command.
  • query-abort replaces query-kill and the deprecated scan-abort command.
• The batch-without-digests configuration parameter has been removed.
• A number of Best Practices will be checked at startup. The Best Practices can be enforced by enabling the new enforce-best-practices configuration item.
• Several configuration parameters have been renamed or removed. Please refer to Config, Metrics, and Info Changes in Aerospike Database 6.0.
• Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.

Improvements

• Enterprise & Federal Only
  • [AER-6570] - (DEPLOYMENT) With index-type flash namespaces, allow the server to start as a non-root user if the flash-index-friendly '/proc/sys' values have been set.

Bug Fixes

• Enterprise & Federal Only
  • [AER-6569] - (INFO) A cluster-stable command without a 'namespace' parameter will not check for unavailable and dead partitions.
  • [AER-6571] - (UDF) The record.numbins() and record.bin_names() functions erroneously include bin tombstones.

Known Issues

• If you use equality secondary index queries that return a small number of records, you may see a latency increase in server releases 6.0-6.2. The inline-short-queries configuration option provides a partial fix in server 6.3, and a more advanced fix is scheduled for server 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 server version 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.
• Known Issues: Server

Updates

• aerospike-tools 7.3.1

• This General Availability release 6.0.0.6 contains all hotfixes deployed during the release candidate cycle.
• When upgrading to server version 6.0, you must either trim or wipe (zeroize) the Aerospike header on the devices. A modified record storage format was introduced by AER-6513, which adds protection against partially written records during an unclean shutdown.
• For upgrading, or the unlikely event of downgrading, please refer to Special Upgrades.
• BREAKING CHANGE: The truncate privilege is now a separate privilege and is no longer under write.
• The batch operations capability has been made comprehensive. We now fully support batch reads, writes, deletes, and UDF commands.
• The previously deprecated Predicate Expression API has been removed. Use Aerospike Filter Expressions (added in version 5.2).
• Service context configuration paxos-single-replica-limit has been removed.
• Configurations, Metrics, and Server Logs related to Scans are now referred to as Primary Index Queries (pi queries). For example, scan_basic_complete is now referred to as pi_query_long_basic_complete.
• The jobs info command is now officially deprecated and will continue to be supported through a deprecation period, after which it will be removed. jobs are now redundant with the new secondary index building methods and the following new info commands:
  • query-show replaces query-list and the deprecated scan-show command.
  • query-abort replaces query-kill and the deprecated scan-abort command.
• The batch-without-digests configuration parameter has been removed.
• A number of Best Practices will be checked at startup. The Best Practices can be enforced by enabling the new enforce-best-practices configuration item.
• Several configuration parameters have been renamed or removed. Please refer to Config, Metrics, and Info Changes in Aerospike Database 6.0.
• Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.

Bug Fixes

• Enterprise, Federal & Community
  • [AER-6568] - (QUERY) For single-bin namespaces, primary index queries erroneously fail without starting.

Known Issues

• If you use equality secondary index queries that return a small number of records, you may see a latency increase in server releases 6.0-6.2. The inline-short-queries configuration option provides a partial fix in server 6.3, and a more advanced fix is scheduled for server 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 server version 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.
• Known Issues: Server

Updates

• aerospike-tools 7.2.1

• This General Availability release 6.0.0.5 contains all hotfixes deployed during the release candidate cycle.
• When upgrading to server version 6.0, you must either trim or wipe (zeroize) the Aerospike header on the devices. A modified record storage format was introduced by AER-6513, which adds protection against partially written records during an unclean shutdown.
• For upgrading, or the unlikely event of downgrading, please refer to Special Upgrades.
• BREAKING CHANGE: The truncate privilege is now a separate privilege and is no longer under write.
• The batch operations capability has been made comprehensive. We now fully support batch reads, writes, deletes, and UDF commands.
• The previously deprecated Predicate Expression API has been removed. Use Aerospike Filter Expressions (added in version 5.2).
• Service context configuration paxos-single-replica-limit has been removed.
• Configurations, Metrics, and Server Logs related to Scans are now referred to as Primary Index Queries (pi queries). For example, scan_basic_complete is now referred to as pi_query_long_basic_complete.
• The jobs info command is now officially deprecated and will continue to be supported through a deprecation period, after which it will be removed. jobs are now redundant with the new secondary index building methods and the following new info commands:
  • query-show replaces query-list and the deprecated scan-show command.
  • query-abort replaces query-kill and the deprecated scan-abort command.
• The batch-without-digests configuration parameter has been removed.
• A number of Best Practices will be checked at startup. The Best Practices can be enforced by enabling the new enforce-best-practices configuration item.
• Several configuration parameters have been renamed or removed. Please refer to Config, Metrics, and Info Changes in Aerospike Database 6.0.
• Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.

Bug Fixes

• Enterprise, Federal & Community
  • [AER-6566] - (SINDEX) When cold starting storage-backed data-in-memory namespaces, finding a later but expired version of a secondary-indexed record will assert.
• Enterprise & Federal Only
  • [AER-6567] - (SINDEX) For index-type flash, a client non-durably deleting a secondary-indexed record may cause an assertion.

Known Issues

• If you use equality secondary index queries that return a small number of records, you may see a latency increase in server releases 6.0-6.2. The inline-short-queries configuration option provides a partial fix in server 6.3, and a more advanced fix is scheduled for server 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 server version 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.
• Known Issues: Server

Updates

• aerospike-tools 7.1.1

• This release is superseded by 6.0.0.5.
• This General Availability release 6.0.0.4 contains all hotfixes deployed during the release candidate cycle.
• When upgrading to server version 6.0, you must either trim or wipe (zeroize) the Aerospike header on the devices. A modified record storage format was introduced by AER-6513, which adds protection against partially written records during an unclean shutdown.
• For upgrading, or the unlikely event of downgrading, please refer to Special Upgrades.
• BREAKING CHANGE: The truncate privilege is now a separate privilege and is no longer under write.
• The batch operations capability has been made comprehensive. We now fully support batch reads, writes, deletes, and UDF commands.
• The previously deprecated Predicate Expression API has been removed. Use Aerospike Filter Expressions (added in version 5.2).
• Service context configuration paxos-single-replica-limit has been removed.
• Configurations, Metrics, and Server Logs related to Scans are now referred to as Primary Index Queries (pi queries). For example, scan_basic_complete is now referred to as pi_query_long_basic_complete.
• The jobs info command is now officially deprecated and will continue to be supported through a deprecation period, after which it will be removed. jobs are now redundant with the new secondary index building methods and the following new info commands:
  • query-show replaces query-list and the deprecated scan-show command.
  • query-abort replaces query-kill and the deprecated scan-abort command.
• The batch-without-digests configuration parameter has been removed.
• A number of Best Practices will be checked at startup. The Best Practices can be enforced by enabling the new enforce-best-practices configuration item.
• Several configuration parameters have been renamed or removed. Please refer to Config, Metrics, and Info Changes in Aerospike Database 6.0.
• Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.

Improvements

• Enterprise & Federal Only
  • [AER-6562] - (SINDEX) For index-type flash, adjust secondary index(es) directly on non-durable deletes, instead of relying on garbage collection. [Note: this introduced an issue fixed in AER-6567.]

Bug Fixes

• Enterprise, Federal & Community
  • [AER-6564] - (CDT) A context operation on a CDT with top-level list which changes the CDT size such that it crosses a 256, 64K, or 1M byte boundary may cause a crash.
  • [AER-6563] - (EXPRESSIONS) For namespaces with data not in memory, a client-provided object used as a bin in a call may cause a crash.

Known Issues

• If you use equality secondary index queries that return a small number of records, you may see a latency increase in server releases 6.0-6.2. The inline-short-queries configuration option provides a partial fix in server 6.3, and a more advanced fix is scheduled for server 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 server version 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.
• Known Issues: Server

• This General Availability release 6.0.0.3 contains all hotfixes deployed during the release candidate cycle.
• When upgrading to server version 6.0, you must either trim or wipe (zeroize) the Aerospike header on the devices. A modified record storage format was introduced by AER-6513, which adds protection against partially written records during an unclean shutdown.
• For upgrading, or the unlikely event of downgrading, please refer to Special Upgrades.
• BREAKING CHANGE: The truncate privilege is now a separate privilege and is no longer under write.
• The batch operations capability has been made comprehensive. We now fully support batch reads, writes, deletes, and UDF commands.
• The previously deprecated Predicate Expression API has been removed. Use Aerospike Filter Expressions (added in version 5.2).
• Service context configuration paxos-single-replica-limit has been removed.
• Configurations, Metrics, and Server Logs related to Scans are now referred to as Primary Index Queries (pi queries). For example, scan_basic_complete is now referred to as pi_query_long_basic_complete.
• The jobs info command is now officially deprecated and will continue to be supported through a deprecation period, after which it will be removed. jobs are now redundant with the new secondary index building methods and the following new info commands:
  • query-show replaces query-list and the deprecated scan-show command.
  • query-abort replaces query-kill and the deprecated scan-abort command.
• The batch-without-digests configuration parameter has been removed.
• A number of Best Practices will be checked at startup. The Best Practices can be enforced by enabling the new enforce-best-practices configuration item.
• Several configuration parameters have been renamed or removed. Please refer to Config, Metrics, and Info Changes in Aerospike Database 6.0.
• Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.

Bug Fixes

• Enterprise, Federal & Community
  • [AER-6555] - (UDF) For namespaces with data not in memory, a UDF that writes multiple bins and would exceed write-block-size may cause a crash.
• Enterprise & Federal Only
  • [AER-6553] - (XDR) A source node may never discover all destination nodes if it starts with partial visibility of the remote cluster.
  • [AER-6554] - (MIGRATION) For strong-consistency namespaces, a failed appeal may block a node from starting migrations.

Known Issues

• If you use equality secondary index queries that return a small number of records, you may see a latency increase in server releases 6.0-6.2. The inline-short-queries configuration option provides a partial fix in server 6.3, and a more advanced fix is scheduled for server 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 server version 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.
• Known Issues: Server

Updates

• aerospike-tools 7.0.5

• This General Availability release 6.0.0.2 contains all hotfixes deployed during the release candidate cycle.
• When upgrading to server version 6.0, you must either trim or wipe (zeroize) the Aerospike header on the devices. A modified record storage format was introduced by AER-6513, which adds protection against partially written records during an unclean shutdown.
• For upgrading, or the unlikely event of downgrading, please refer to Special Upgrades.
• BREAKING CHANGE: The truncate privilege is now a separate privilege and is no longer under write.
• The batch operations capability has been made comprehensive. We now fully support batch reads, writes, deletes, and UDF commands.
• The previously deprecated Predicate Expression API has been removed. Use Aerospike Filter Expressions (added in version 5.2).
• Service context configuration paxos-single-replica-limit has been removed.
• Configurations, Metrics, and Server Logs related to Scans are now referred to as Primary Index Queries (pi queries). For example, scan_basic_complete is now referred to as pi_query_long_basic_complete.
• The jobs info command is now officially deprecated and will continue to be supported through a deprecation period, after which it will be removed. jobs are now redundant with the new secondary index building methods and the following new info commands:
  • query-show replaces query-list and the deprecated scan-show command.
  • query-abort replaces query-kill and the deprecated scan-abort command.
• The batch-without-digests configuration parameter has been removed.
• A number of Best Practices will be checked at startup. The Best Practices can be enforced by enabling the new enforce-best-practices configuration item.
• Several configuration parameters have been renamed or removed. Please refer to Config, Metrics, and Info Changes in Aerospike Database 6.0.
• Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.

Bug Fixes

• Enterprise, Federal & Community
  • [AER-6541] - (EXPRESSIONS) A cond in an expression fails to set the return type, which may allow an illegal expression to build and cause an assertion.
  • [AER-6533] - (LOGGING) Set index memory is not included in 'total-bytes' and 'used-pct' on the memory-usage ticker line.
• Enterprise & Federal Only
  • [AER-6536] - (LOGGING) TLS I/O error may log incorrect errno.

Known Issues

• If you use equality secondary index queries that return a small number of records, you may see a latency increase in server releases 6.0-6.2. The inline-short-queries configuration option provides a partial fix in server 6.3, and a more advanced fix is scheduled for server 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 server version 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.
• Known Issues: Server

• This General Availability release 6.0.0.1 contains all hotfixes deployed during the release candidate cycle.
• When upgrading to server version 6.0, you must either trim or wipe (zeroize) the Aerospike header on the devices. A modified record storage format was introduced by AER-6513, which adds protection against partially written records during an unclean shutdown.
• For upgrading, or the unlikely event of downgrading, please refer to Special Upgrades.
• BREAKING CHANGE: The truncate privilege is now a separate privilege and is no longer under write.
• The batch operations capability has been made comprehensive. We now fully support batch reads, writes, deletes, and UDF commands.
• The previously deprecated Predicate Expression API has been removed. Use Aerospike Filter Expressions (added in version 5.2).
• Service context configuration paxos-single-replica-limit has been removed.
• Configurations, Metrics, and Server Logs related to Scans are now referred to as Primary Index Queries (pi queries). For example, scan_basic_complete is now referred to as pi_query_long_basic_complete.
• The jobs info command is now officially deprecated and will continue to be supported through a deprecation period, after which it will be removed. jobs are now redundant with the new secondary index building methods and the following new info commands:
  • query-show replaces query-list and the deprecated scan-show command.
  • query-abort replaces query-kill and the deprecated scan-abort command.
• The batch-without-digests configuration parameter has been removed.
• A number of Best Practices will be checked at startup. The Best Practices can be enforced by enabling the new enforce-best-practices configuration item.
• Several configuration parameters have been renamed or removed. Please refer to Config, Metrics, and Info Changes in Aerospike Database 6.0.
• Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.

Bug Fixes

• Enterprise, Federal & Community
  • [AER-6529] - (SINDEX) Garbage collection does not decrement memory_used_sindex_bytes, which may cause erroneous stop-writes or eviction.

Known Issues

• If you use equality secondary index queries that return a small number of records, you may see a latency increase in server releases 6.0-6.2. The inline-short-queries configuration option provides a partial fix in server 6.3, and a more advanced fix is scheduled for server 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 server version 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.
• Known Issues: Server

• This General Availability release 6.0.0.0 contains all hotfixes deployed during the release candidate cycle.
• When upgrading to server version 6.0, you must either trim or wipe (zeroize) the Aerospike header on the devices. A modified record storage format was introduced by AER-6513, which adds protection against partially written records during an unclean shutdown.
• For upgrading, or the unlikely event of downgrading, please refer to Special Upgrades.
• BREAKING CHANGE: The truncate privilege is now a separate privilege and is no longer under write.
• The batch operations capability has been made comprehensive. We now fully support batch reads, writes, deletes, and UDF commands.
• The previously deprecated Predicate Expression API has been removed. Use Aerospike Filter Expressions (added in version 5.2).
• Service context configuration paxos-single-replica-limit has been removed.
• Configurations, Metrics, and Server Logs related to Scans are now referred to as Primary Index Queries (pi queries). For example, scan_basic_complete is now referred to as pi_query_long_basic_complete.
• The jobs info command is now officially deprecated and will continue to be supported through a deprecation period, after which it will be removed. jobs are now redundant with the new secondary index building methods and the following new info commands:
  • query-show replaces query-list and the deprecated scan-show command.
  • query-abort replaces query-kill and the deprecated scan-abort command.
• The batch-without-digests configuration parameter has been removed.
• A number of Best Practices will be checked at startup. The Best Practices can be enforced by enabling the new enforce-best-practices configuration item.
• Several configuration parameters have been renamed or removed. Please refer to Config, Metrics, and Info Changes in Aerospike Database 6.0.
• Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.

New Features

• Enterprise, Federal & Community
  • [AER-6511] - (PACKAGING) Added support for Debian 11.
  • [AER-6512] - (PACKAGING) Removed support for Debian 8.
  • [AER-6500] - (QUERY) Enhanced secondary index queries: query by partition, paginate, throttle, apply quotas.

Improvements

• Enterprise, Federal & Community
  • [AER-6488] - (BALANCE) For AP namespaces, made namespace context configuration item replication-factor dynamic.
  • [AER-6489] - (BALANCE) Removed service context configuration item paxos-single-replica-limit.
  • [AER-6499] - (BATCH) Added support for batch writes, deletes, and UDFs.
  • [AER-6509] - (DEPLOYMENT) With auto-pin numa, handle client interfaces with differing numbers of queues.
  • [AER-6492] - (EXPRESSIONS) Removed support for predicate expressions.
  • [AER-6485] - (KVS) Fail duplicate resolutions if they are overwhelming the write queue.
  • [AER-6504] - (KVS) Check 'rw-hash' and 'proxy-hash' for timed out transactions more frequently, to help the client recycle sockets more efficiently.
  • [AER-6510] - (MIGRATION) Do not retransmit updated or deleted records.
  • [AER-6515] - (PACKAGING) Ensure that the 'aerospike' user has a secure nologin shell.
  • [AER-6506] - (SCAN) Unified scans with new queries.
  • [AER-6491] - (STATS) Latency histograms now include time spent processing other service epoll events that precede the transaction request.
  • [AER-6507] - (STATS) Base heap_efficiency_pct on active rather than mapped memory.
  • [AER-6513] - (STORAGE) Detect and mitigate records which are only partially written during an unclean shutdown.
  • [AER-6514] - (STORAGE) Verify that a device not previously used as an Aerospike storage device was erased before use.
  • [AER-6503] - (UDF) Removed unused 'gen' field from udf-get response, and added sanity check of 'content-len' field in udf-put command.
• Enterprise & Federal Only
  • [AER-6495] - (ACL) Added a separate 'truncate' privilege (no longer under 'write'), 'udf-admin' privilege, and 'sindex-admin' privilege.
  • [AER-6487] - (BALANCE) To restore availability, revived nodes now require all nodes to be trusted (i.e. no e-flags).
  • [AER-6505] - (LOGGING) Separated relevant XDR per-DC ticker line items into per-namespace lines.
  • [AER-6501] - (SECURITY) Added support for a special Enterprise build which is FIPS 140-2 compliant.
  • [AER-6483] - (XDR) Added DC namespace context configuration item compression-threshold to specify a size threshold for compression.
  • [AER-6490] - (XDR) Added value 'no-bins' to DC namespace context configuration item bin-policy, to ship record metadata only, including keys, to connectors.
  • [AER-6497] - (XDR) Reapply set shipping filters, and other configured filters, during retries.
  • [AER-6498] - (XDR) Changed automatic throttling to reduce throughput more quickly, with a lower floor.

Known Issues

• If you use equality secondary index queries that return a small number of records, you may see a latency increase in server releases 6.0-6.2. The inline-short-queries configuration option provides a partial fix in server 6.3, and a more advanced fix is scheduled for server 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 server version 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.
• Known Issues: Server

Updates

• aerospike-tools 7.0.3

• This is a Developer Preview Release.
• When upgrading to server version 6.0, you must either trim or wipe (zeroize) the Aerospike header on the devices. A modified record storage format was introduced by AER-6513, which adds protection against partially written records during an unclean shutdown.
• For upgrading, or the unlikely event of downgrading, please refer to Special Upgrades.
• BREAKING CHANGE: The truncate privilege is now a separate privilege and is no longer under write.
• The batch operations capability has been made comprehensive. We now fully support batch reads, writes, deletes, and UDF commands.
• The previously deprecated Predicate Expression API has been removed. Use Aerospike Filter Expressions (added in version 5.2).
• Service context configuration paxos-single-replica-limit has been removed.
• Configurations, Metrics, and Server Logs related to Scans are now referred to as Primary Index Queries (pi queries). For example, scan_basic_complete is now referred to as pi_query_long_basic_complete.
• The jobs info command is now officially deprecated and will continue to be supported through a deprecation period, after which it will be removed. jobs are now redundant with the new secondary index building methods and the following new info commands:
  • query-show replaces query-list and the deprecated scan-show command.
  • query-abort replaces query-kill and the deprecated scan-abort command.
• The batch-without-digests configuration parameter has been removed.
• A number of Best Practices will be checked at startup. The Best Practices can be enforced by enabling the new enforce-best-practices configuration item.
• Several configuration parameters have been renamed or removed. Please refer to Config, Metrics, and Info Changes in Aerospike Database 6.0.
• Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.

Bug Fixes

• Enterprise, Federal & Community
  • [AER-6526] - (SINDEX) Truncating a namespace or set with a secondary index, and more than 2 billion records per node, may overflow a garbage collection queue and crash.
• Enterprise & Federal Only
  • [AER-6527] - (XDR) Dynamically removing seed nodes while trying to connect may cause connections to be skipped or cause a crash.

Known Issues

• If you use equality secondary index queries that return a small number of records, you may see a latency increase in server releases 6.0-6.2. The inline-short-queries configuration option provides a partial fix in server 6.3, and a more advanced fix is scheduled for server 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 server version 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.
• Known Issues: Server

Updates

• aerospike-tools 7.0.2

• This is a Developer Preview Release.
• When upgrading to server version 6.0, you must either trim or wipe (zeroize) the Aerospike header on the devices. A modified record storage format was introduced by AER-6513, which adds protection against partially written records during an unclean shutdown.
• For upgrading, or the unlikely event of downgrading, please refer to Special Upgrades.
• BREAKING CHANGE: The truncate privilege is now a separate privilege and is no longer under write.
• The batch operations capability has been made comprehensive. We now fully support batch reads, writes, deletes, and UDF commands.
• The previously deprecated Predicate Expression API has been removed. Use Aerospike Filter Expressions (added in version 5.2).
• Service context configuration paxos-single-replica-limit has been removed.
• Configurations, Metrics, and Server Logs related to Scans are now referred to as Primary Index Queries (pi queries). For example, scan_basic_complete is now referred to as pi_query_long_basic_complete.
• The jobs info command is now officially deprecated and will continue to be supported through a deprecation period, after which it will be removed. jobs are now redundant with the new secondary index building methods and the following new info commands:
  • query-show replaces query-list and the deprecated scan-show command.
  • query-abort replaces query-kill and the deprecated scan-abort command.
• The batch-without-digests configuration parameter has been removed.
• A number of Best Practices will be checked at startup. The Best Practices can be enforced by enabling the new enforce-best-practices configuration item.
• Several configuration parameters have been renamed or removed. Please refer to Config, Metrics, and Info Changes in Aerospike Database 6.0.
• Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.

New Features

• Enterprise, Federal & Community
  • [AER-6511] - (PACKAGING) Added support for Debian 11.
  • [AER-6512] - (PACKAGING) Removed support for Debian 8.
  • [AER-6500] - (QUERY) Enhanced secondary index queries: query by partition, paginate, throttle, apply quotas.

Improvements

• Enterprise, Federal & Community
  • [AER-6488] - (BALANCE) For AP namespaces, made namespace context configuration item replication-factor dynamic.
  • [AER-6489] - (BALANCE) Removed service context configuration item paxos-single-replica-limit.
  • [AER-6499] - (BATCH) Added support for batch writes, deletes, and UDFs.
  • [AER-6509] - (DEPLOYMENT) With auto-pin numa, handle client interfaces with differing numbers of queues.
  • [AER-6492] - (EXPRESSIONS) Removed support for predicate expressions.
  • [AER-6485] - (KVS) Fail duplicate resolutions if they are overwhelming the write queue.
  • [AER-6504] - (KVS) Check 'rw-hash' and 'proxy-hash' for timed out transactions more frequently, to help the client recycle sockets more efficiently.
  • [AER-6510] - (MIGRATION) Do not retransmit updated or deleted records.
  • [AER-6515] - (PACKAGING) Ensure that the 'aerospike' user has a secure nologin shell.
  • [AER-6506] - (SCAN) Unified scans with new queries.
  • [AER-6491] - (STATS) Latency histograms now include time spent processing other service epoll events that precede the transaction request.
  • [AER-6507] - (STATS) Base heap_efficiency_pct on active rather than mapped memory.
  • [AER-6513] - (STORAGE) Detect and mitigate records which are only partially written during an unclean shutdown.
  • [AER-6514] - (STORAGE) Verify that a device not previously used as an Aerospike storage device was erased before use.
  • [AER-6503] - (UDF) Removed unused 'gen' field from udf-get response, and added sanity check of 'content-len' field in udf-put command.
• Enterprise & Federal Only
  • [AER-6495] - (ACL) Added a separate 'truncate' privilege (no longer under 'write'), 'udf-admin' privilege, and 'sindex-admin' privilege.
  • [AER-6487] - (BALANCE) To restore availability, revived nodes now require all nodes to be trusted (i.e. no e-flags).
  • [AER-6505] - (LOGGING) Separated relevant XDR per-DC ticker line items into per-namespace lines.
  • [AER-6501] - (SECURITY) Added support for a special Enterprise build which is FIPS 140-2 compliant.
  • [AER-6483] - (XDR) Added DC namespace context configuration item compression-threshold to specify a size threshold for compression.
  • [AER-6490] - (XDR) Added value 'no-bins' to DC namespace context configuration item bin-policy, to ship record metadata only, including keys, to connectors.
  • [AER-6497] - (XDR) Reapply set shipping filters, and other configured filters, during retries.
  • [AER-6498] - (XDR) Changed automatic throttling to reduce throughput more quickly, with a lower floor.

Known Issues

• If you use equality secondary index queries that return a small number of records, you may see a latency increase in server releases 6.0-6.2. The inline-short-queries configuration option provides a partial fix in server 6.3, and a more advanced fix is scheduled for server 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 server version 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.
• Known Issues: Server

Updates

• aerospike-tools 7.0.0