Aerospike Server Community Edition 8.0.0.1
January 22, 2025
Aerospike Database software version 8.0 is now available.
New in this version
This version implements the transactions feature.
New features
- Transactions: A transaction is several commands isolated from commands outside the transaction and executed atomically. Aerospike transactions guarantee one of two outcomes: either all commands succeed together, or one or more commands fail. In case of failure, all records roll back to the state prior to the attempted transaction. No commands outside the transaction can see the state changes being created inside the transaction. This allows you to enforce serializability requirements by putting all requests with such requirements into their own transactions.
:::note
- There are special considerations for downgrade if transactions were attempted. If you need to downgrade, see Downgrade from Database 8.0 before proceeding.
- 'mrt' in the names of new configuration and metrics items indicates that those items are associated with the new transactions feature.
:::
Updates
See Platform support and compatibility for all currently supported platforms.
Configuration items added or enhanced
| Item | Action | Notes |
|---|---|---|
disable-mrt-writes
| added | Static/dynamic, boolean, default false, blocks new transactions with writes by blocking monitor creates, can be used dynamically to let an XDR destination settle to a transaction-consistent state. |
mrt-duration
| added | Static/dynamic, seconds or time units, minimum 1, maximum 120, default 10, used if value not specified by client, determines deadline after which transactions can no longer be done in a transaction. |
Metrics changes
| Item | Action |
|---|---|
mrt_provisionals
| added |
mrt_monitors_active
| added |
mrt_verify_read_success
| added |
mrt_verify_read_error
| added |
mrt_verify_read_timeout
| added |
mrt_roll_forward_success
| added |
mrt_roll_forward_error
| added |
mrt_roll_forward_timeout
| added |
mrt_monitor_roll_forward_success
| added |
mrt_monitor_roll_forward_error
| added |
mrt_monitor_roll_forward_timeout
| added |
mrt_roll_back_success
| added |
mrt_roll_back_error
| added |
mrt_roll_back_timeout
| added |
mrt_monitor_roll_back_success
| added |
mrt_monitor_roll_back_error
| added |
mrt_monitor_roll_back_timeout
| added |
fail_mrt_blocked
| added |
fail_mrt_version_mismatch
| added |
mrt_monitor_roll_tombstone_creates
| added |
Histogram changes
| Item | Action |
|---|---|
writes-per-mrt
| added |
Server log changes
| Item | Action |
|---|---|
mrt-finish
| added |
mrt-monitor-finish
| added |
writes-per-mrt
| added |
monitor committing
| added |
monitor aborting
| added |
Error code changes
| Item | Action | Notes |
|---|---|---|
| 120 | MRT_BLOCKED | added |
| 121 | MRT_VERSION_MISMATCH | added |
| 122 | MRT_EXPIRED | added |
| 123 | MRT_TOO_MANY_WRITES | added |
| 124 | MRT_COMMITTED | added |
| 125 | MRT_ABORTED | added |
| 126 | MRT_ALREADY_LOCKED | added |
| 127 | MRT_MONITOR_EXISTS | added |
Tools changes
- Update to tools package 11.2.0
- Support for macOS 12 for all tools packages was removed in the tools 11.1.1 release.
See Tools 11.2.0 Release Notes.
Client/server feature compatibility
For a complete list of client features and the server versions that support them, see the Client Matrix.
Ecosystem compatibility
Compatible client versions
For full feature access in Database 8.0:
- Java client 9.0.3
- Python client 16.0.1
- C# client 8.0.1
- C client 7.0.2
- Go client 8.0
- Node.js client 6.0.1
Compatible connector versions
- Trino connector 1.2.0 or later
- Spark connector 3.1.1 or later
Prerequisites and notes
- For upgrade instructions, refer to Upgrade or Repair Server
- For special upgrade instructions, refer to Special upgrades and downgrades
Product lifecycle updates
Aerospike provides maintenance and support for 2 years (24 months) starting with database release 6.3.
See Platform Support for details.