Aerospike Server EE Release Notes

  • 6.0.0.22
    Release Date: August 30, 2023
    • 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

    Enterprise Download
  • 6.0.0.21
    Release Date: August 10, 2023
    • 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

  • 6.0.0.20
    Release Date: July 25, 2023
    • 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

    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

  • 6.0.0.19
    Release Date: June 12, 2023
    • 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

  • 6.0.0.18
    Release Date: May 23, 2023
    • 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

  • 6.0.0.17
    Release Date: May 16, 2023
    • 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

  • 6.0.0.16
    Release Date: April 28, 2023
    • 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

    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

  • 6.0.0.15
    Release Date: April 6, 2023
    • 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

    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

  • 6.0.0.14
    Release Date: March 16, 2023
    • 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

  • 6.0.0.13
    Release Date: March 8, 2023
    • 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

  • 6.0.0.11
    Release Date: January 24, 2023
    • 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

  • 6.0.0.10
    Release Date: December 15, 2022
    • 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

  • 6.0.0.9
    Release Date: December 2, 2022
    • 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

  • 6.0.0.8
    Release Date: November 11, 2022
    • 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

  • 6.0.0.7
    Release Date: October 3, 2022
    • 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

    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

  • 6.0.0.6
    Release Date: September 14, 2022
    • 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

  • 6.0.0.5
    Release Date: August 23, 2022
    • 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

  • 6.0.0.4
    Release Date: August 17, 2022
    • 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

  • 6.0.0.3
    Release Date: August 4, 2022
    • 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

  • 6.0.0.2
    Release Date: June 30, 2022
    • 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

  • 6.0.0.1
    Release Date: May 4, 2022
    • 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

  • 6.0.0.0
    Release Date: April 27, 2022
    • 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

  • 6.0.0.0-rc7
    Release Date: April 20, 2022
    • 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

  • 6.0.0.0-rc6
    Release Date: April 11, 2022
    • 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

  • 5.7.0.31
    Release Date: April 6, 2023
    • For upgrading, or the unlikely event of downgrading, please refer to Special Upgrades.
    • The Predicate Expression API is obsolete. The Aerospike Server and Client have scheduled removal with our next major Aerospike Server release. Use Aerospike Filter Expressions (added in version 5.2).
    • 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:
    • The configuration parameter batch-without-digests, now defaults to true, is deprecated and will be removed in six months. Customers using clients older than a year (around the time of Server 4.9 which introduced batch-without-digests) will now have to explicitly set the batch-without-digests configuration item to false.
    • 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.
    • The security context configuration items enable-security and enable-ldap have been removed. The Server will not start if either enable-security or enable-ldap is present in the configuration file.
    • Security will now be enabled simply by the presence of the security { } section in the configuration file. Similarly, LDAP will now be enabled simply by the presence of the ldap { } section within the security { } section of the configuration file.
    • To use XDR with ACL auth-mode must be explicitly configured.
    • We build on Red Hat Enterprise Linux (RHEL) 8 instead of CentOS 8 when creating rpm packages.
    • 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

    Known Issues

    Updates

    Enterprise Download
  • 5.7.0.30
    Release Date: March 16, 2023
    • For upgrading, or the unlikely event of downgrading, please refer to Special Upgrades.
    • The Predicate Expression API is obsolete. The Aerospike Server and Client have scheduled removal with our next major Aerospike Server release. Use Aerospike Filter Expressions (added in version 5.2).
    • 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:
    • The configuration parameter batch-without-digests, now defaults to true, is deprecated and will be removed in six months. Customers using clients older than a year (around the time of Server 4.9 which introduced batch-without-digests) will now have to explicitly set the batch-without-digests configuration item to false.
    • 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.
    • The security context configuration items enable-security and enable-ldap have been removed. The Server will not start if either enable-security or enable-ldap is present in the configuration file.
    • Security will now be enabled simply by the presence of the security { } section in the configuration file. Similarly, LDAP will now be enabled simply by the presence of the ldap { } section within the security { } section of the configuration file.
    • To use XDR with ACL auth-mode must be explicitly configured.
    • We build on Red Hat Enterprise Linux (RHEL) 8 instead of CentOS 8 when creating rpm packages.
    • Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.
    • This version and subsequent server 5.7.0.x Debian package software files (.deb) and Red Hat Package Manager files (.rpm) are now GPG Signed.

    Bug Fixes

    • Enterprise & 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 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

    Updates

  • 5.7.0.29
    Release Date: March 8, 2023
    • For upgrading, or the unlikely event of downgrading, please refer to Special Upgrades.
    • The Predicate Expression API is obsolete. The Aerospike Server and Client have scheduled removal with our next major Aerospike Server release. Use Aerospike Filter Expressions (added in version 5.2).
    • 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:
    • The configuration parameter batch-without-digests, now defaults to true, is deprecated and will be removed in six months. Customers using clients older than a year (around the time of Server 4.9 which introduced batch-without-digests) will now have to explicitly set the batch-without-digests configuration item to false.
    • 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.
    • The security context configuration items enable-security and enable-ldap have been removed. The Server will not start if either enable-security or enable-ldap is present in the configuration file.
    • Security will now be enabled simply by the presence of the security { } section in the configuration file. Similarly, LDAP will now be enabled simply by the presence of the ldap { } section within the security { } section of the configuration file.
    • To use XDR with ACL auth-mode must be explicitly configured.
    • We build on Red Hat Enterprise Linux (RHEL) 8 instead of CentOS 8 when creating rpm packages.
    • Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.

    Bug Fixes

    • Enterprise & 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

    Updates

  • 5.7.0.27
    Release Date: January 24, 2023
    • For upgrading, or the unlikely event of downgrading, please refer to Special Upgrades.
    • The Predicate Expression API is obsolete. The Aerospike Server and Client have scheduled removal with our next major Aerospike Server release. Use Aerospike Filter Expressions (added in version 5.2).
    • 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:
    • The configuration parameter batch-without-digests, now defaults to true, is deprecated and will be removed in six months. Customers using clients older than a year (around the time of Server 4.9 which introduced batch-without-digests) will now have to explicitly set the batch-without-digests configuration item to false.
    • 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.
    • The security context configuration items enable-security and enable-ldap have been removed. The Server will not start if either enable-security or enable-ldap is present in the configuration file.
    • Security will now be enabled simply by the presence of the security { } section in the configuration file. Similarly, LDAP will now be enabled simply by the presence of the ldap { } section within the security { } section of the configuration file.
    • To use XDR with ACL auth-mode must be explicitly configured.
    • We build on Red Hat Enterprise Linux (RHEL) 8 instead of CentOS 8 when creating rpm packages.
    • Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.

    Bug Fixes

    • Enterprise & 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

    Updates

  • 5.7.0.26
    Release Date: January 2, 2023
    • For upgrading, or the unlikely event of downgrading, please refer to Special Upgrades.
    • The Predicate Expression API is obsolete. The Aerospike Server and Client have scheduled removal with our next major Aerospike Server release. Use Aerospike Filter Expressions (added in version 5.2).
    • 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:
    • The configuration parameter batch-without-digests, now defaults to true, is deprecated and will be removed in six months. Customers using clients older than a year (around the time of Server 4.9 which introduced batch-without-digests) will now have to explicitly set the batch-without-digests configuration item to false.
    • 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.
    • The security context configuration items enable-security and enable-ldap have been removed. The Server will not start if either enable-security or enable-ldap is present in the configuration file.
    • Security will now be enabled simply by the presence of the security { } section in the configuration file. Similarly, LDAP will now be enabled simply by the presence of the ldap { } section within the security { } section of the configuration file.
    • To use XDR with ACL auth-mode must be explicitly configured.
    • We build on Red Hat Enterprise Linux (RHEL) 8 instead of CentOS 8 when creating rpm packages.
    • Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.

    Bug Fixes

    • Enterprise & Community
      • [AER-6593] - (SINDEX) If garbage collection pauses at a sub-tree boundary, elements may be skipped, causing later queries to assert or return incorrect results.

    Known Issues

    Updates

  • 5.7.0.25
    Release Date: December 2, 2022
    • For upgrading, or the unlikely event of downgrading, please refer to Special Upgrades.
    • The Predicate Expression API is obsolete. The Aerospike Server and Client have scheduled removal with our next major Aerospike Server release. Use Aerospike Filter Expressions (added in version 5.2).
    • 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:
    • The configuration parameter batch-without-digests, now defaults to true, is deprecated and will be removed in six months. Customers using clients older than a year (around the time of Server 4.9 which introduced batch-without-digests) will now have to explicitly set the batch-without-digests configuration item to false.
    • 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.
    • The security context configuration items enable-security and enable-ldap have been removed. The Server will not start if either enable-security or enable-ldap is present in the configuration file.
    • Security will now be enabled simply by the presence of the security { } section in the configuration file. Similarly, LDAP will now be enabled simply by the presence of the ldap { } section within the security { } section of the configuration file.
    • To use XDR with ACL auth-mode must be explicitly configured.
    • We build on Red Hat Enterprise Linux (RHEL) 8 instead of CentOS 8 when creating rpm packages.
    • Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.

    Bug Fixes

    • Enterprise Only
      • [AER-6582] - (XDR) Setting DC context configuration item tls-name after adding seed nodes which require it may cause a crash.

    Known Issues

    Updates

  • 5.7.0.24
    Release Date: November 11, 2022
    • For upgrading, or the unlikely event of downgrading, please refer to Special Upgrades.
    • The Predicate Expression API is obsolete. The Aerospike Server and Client have scheduled removal with our next major Aerospike Server release. Use Aerospike Filter Expressions (added in version 5.2).
    • 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:
    • The configuration parameter batch-without-digests, now defaults to true, is deprecated and will be removed in six months. Customers using clients older than a year (around the time of Server 4.9 which introduced batch-without-digests) will now have to explicitly set the batch-without-digests configuration item to false.
    • 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.
    • The security context configuration items enable-security and enable-ldap have been removed. The Server will not start if either enable-security or enable-ldap is present in the configuration file.
    • Security will now be enabled simply by the presence of the security { } section in the configuration file. Similarly, LDAP will now be enabled simply by the presence of the ldap { } section within the security { } section of the configuration file.
    • To use XDR with ACL auth-mode must be explicitly configured.
    • We build on Red Hat Enterprise Linux (RHEL) 8 instead of CentOS 8 when creating rpm packages.
    • Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.

    Bug Fixes

    • Enterprise Only
      • [AER-6572] - (XDR) Not setting DC context configuration item auth-user when auth-mode requires it will cause a crash.

    Known Issues

    Updates

  • 5.7.0.23
    Release Date: October 21, 2022
    • For upgrading, or the unlikely event of downgrading, please refer to Special Upgrades.
    • The Predicate Expression API is obsolete. The Aerospike Server and Client have scheduled removal with our next major Aerospike Server release. Use Aerospike Filter Expressions (added in version 5.2).
    • 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:
    • The configuration parameter batch-without-digests, now defaults to true, is deprecated and will be removed in six months. Customers using clients older than a year (around the time of Server 4.9 which introduced batch-without-digests) will now have to explicitly set the batch-without-digests configuration item to false.
    • 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.
    • The security context configuration items enable-security and enable-ldap have been removed. The Server will not start if either enable-security or enable-ldap is present in the configuration file.
    • Security will now be enabled simply by the presence of the security { } section in the configuration file. Similarly, LDAP will now be enabled simply by the presence of the ldap { } section within the security { } section of the configuration file.
    • To use XDR with ACL auth-mode must be explicitly configured.
    • We build on Red Hat Enterprise Linux (RHEL) 8 instead of CentOS 8 when creating rpm packages.
    • Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.

    Improvements

    Known Issues

    Updates

  • 5.7.0.22
    Release Date: October 3, 2022
    • For upgrading, or the unlikely event of downgrading, please refer to Special Upgrades.
    • The Predicate Expression API is obsolete. The Aerospike Server and Client have scheduled removal with our next major Aerospike Server release. Use Aerospike Filter Expressions (added in version 5.2).
    • 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:
    • The configuration parameter batch-without-digests, now defaults to true, is deprecated and will be removed in six months. Customers using clients older than a year (around the time of Server 4.9 which introduced batch-without-digests) will now have to explicitly set the batch-without-digests configuration item to false.
    • 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.
    • The security context configuration items enable-security and enable-ldap have been removed. The Server will not start if either enable-security or enable-ldap is present in the configuration file.
    • Security will now be enabled simply by the presence of the security { } section in the configuration file. Similarly, LDAP will now be enabled simply by the presence of the ldap { } section within the security { } section of the configuration file.
    • To use XDR with ACL auth-mode must be explicitly configured.
    • We build on Red Hat Enterprise Linux (RHEL) 8 instead of CentOS 8 when creating rpm packages.
    • Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.

    Improvements

    • Enterprise 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 Only

    Known Issues

  • 5.7.0.21
    Release Date: August 23, 2022
    • For upgrading, or the unlikely event of downgrading, please refer to Special Upgrades.
    • The Predicate Expression API is obsolete. The Aerospike Server and Client have scheduled removal with our next major Aerospike Server release. Use Aerospike Filter Expressions (added in version 5.2).
    • 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:
    • The configuration parameter batch-without-digests, now defaults to true, is deprecated and will be removed in six months. Customers using clients older than a year (around the time of Server 4.9 which introduced batch-without-digests) will now have to explicitly set the batch-without-digests configuration item to false.
    • 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.
    • The security context configuration items enable-security and enable-ldap have been removed. The Server will not start if either enable-security or enable-ldap is present in the configuration file.
    • Security will now be enabled simply by the presence of the security { } section in the configuration file. Similarly, LDAP will now be enabled simply by the presence of the ldap { } section within the security { } section of the configuration file.
    • To use XDR with ACL auth-mode must be explicitly configured.
    • We build on Red Hat Enterprise Linux (RHEL) 8 instead of CentOS 8 when creating rpm packages.
    • Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.

    Bug Fixes

    • Enterprise & 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 Only
      • [AER-6567] - (SINDEX) For index-type flash, a client non-durably deleting a secondary-indexed record may cause an assertion.

    Known Issues

  • 5.7.0.20
    Release Date: August 17, 2022
    • This release is superseded by 5.7.0.21.
    • For upgrading, or the unlikely event of downgrading, please refer to Special Upgrades.
    • The Predicate Expression API is obsolete. The Aerospike Server and Client have scheduled removal with our next major Aerospike Server release. Use Aerospike Filter Expressions (added in version 5.2).
    • 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:
    • The configuration parameter batch-without-digests, now defaults to true, is deprecated and will be removed in six months. Customers using clients older than a year (around the time of Server 4.9 which introduced batch-without-digests) will now have to explicitly set the batch-without-digests configuration item to false.
    • 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.
    • The security context configuration items enable-security and enable-ldap have been removed. The Server will not start if either enable-security or enable-ldap is present in the configuration file.
    • Security will now be enabled simply by the presence of the security { } section in the configuration file. Similarly, LDAP will now be enabled simply by the presence of the ldap { } section within the security { } section of the configuration file.
    • To use XDR with ACL auth-mode must be explicitly configured.
    • We build on Red Hat Enterprise Linux (RHEL) 8 instead of CentOS 8 when creating rpm packages.
    • Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.

    Bug Fixes

    • Enterprise & 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.
    • Enterprise 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.]

    Known Issues

  • 5.7.0.19
    Release Date: August 4, 2022
    • For upgrading, or the unlikely event of downgrading, please refer to Special Upgrades.
    • The Predicate Expression API is obsolete. The Aerospike Server and Client have scheduled removal with our next major Aerospike Server release. Use Aerospike Filter Expressions (added in version 5.2).
    • 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:
    • The configuration parameter batch-without-digests, now defaults to true, is deprecated and will be removed in six months. Customers using clients older than a year (around the time of Server 4.9 which introduced batch-without-digests) will now have to explicitly set the batch-without-digests configuration item to false.
    • 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.
    • The security context configuration items enable-security and enable-ldap have been removed. The Server will not start if either enable-security or enable-ldap is present in the configuration file.
    • Security will now be enabled simply by the presence of the security { } section in the configuration file. Similarly, LDAP will now be enabled simply by the presence of the ldap { } section within the security { } section of the configuration file.
    • To use XDR with ACL auth-mode must be explicitly configured.
    • We build on Red Hat Enterprise Linux (RHEL) 8 instead of CentOS 8 when creating rpm packages.
    • Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.

    Bug Fixes

    • Enterprise & 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 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

    Updates

  • 5.7.0.18
    Release Date: June 30, 2022
    • For upgrading, or the unlikely event of downgrading, please refer to Special Upgrades.
    • The Predicate Expression API is obsolete. The Aerospike Server and Client have scheduled removal with our next major Aerospike Server release. Use Aerospike Filter Expressions (added in version 5.2).
    • 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:
    • The configuration parameter batch-without-digests, now defaults to true, is deprecated and will be removed in six months. Customers using clients older than a year (around the time of Server 4.9 which introduced batch-without-digests) will now have to explicitly set the batch-without-digests configuration item to false.
    • 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.
    • The security context configuration items enable-security and enable-ldap have been removed. The Server will not start if either enable-security or enable-ldap is present in the configuration file.
    • Security will now be enabled simply by the presence of the security { } section in the configuration file. Similarly, LDAP will now be enabled simply by the presence of the ldap { } section within the security { } section of the configuration file.
    • To use XDR with ACL auth-mode must be explicitly configured.
    • We build on Red Hat Enterprise Linux (RHEL) 8 instead of CentOS 8 when creating rpm packages.
    • Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.

    Bug Fixes

    • Enterprise & Community
      • [AER-6539] - (EXPRESSIONS) Comparisons of expression trileans that include 'unknown' do not return 'unknown'.
      • [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 Only
      • [AER-6536] - (LOGGING) TLS I/O error may log incorrect errno.

    Known Issues

  • 5.7.0.17
    Release Date: April 20, 2022
    • For upgrading, or the unlikely event of downgrading, please refer to Special Upgrades.
    • The Predicate Expression API is obsolete. The Aerospike Server and Client have scheduled removal with our next major Aerospike Server release. Use Aerospike Filter Expressions (added in version 5.2).
    • 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:
    • The configuration parameter batch-without-digests, now defaults to true, is deprecated and will be removed in six months. Customers using clients older than a year (around the time of Server 4.9 which introduced batch-without-digests) will now have to explicitly set the batch-without-digests configuration item to false.
    • 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.
    • The security context configuration items enable-security and enable-ldap have been removed. The Server will not start if either enable-security or enable-ldap is present in the configuration file.
    • Security will now be enabled simply by the presence of the security { } section in the configuration file. Similarly, LDAP will now be enabled simply by the presence of the ldap { } section within the security { } section of the configuration file.
    • To use XDR with ACL auth-mode must be explicitly configured.
    • We build on Red Hat Enterprise Linux (RHEL) 8 instead of CentOS 8 when creating rpm packages.
    • Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.

    Bug Fixes

    • Enterprise & 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 Only
      • [AER-6527] - (XDR) Dynamically removing seed nodes while trying to connect may cause connections to be skipped or cause a crash.

    Known Issues

  • 5.7.0.16
    Release Date: April 4, 2022
    • For upgrading, or the unlikely event of downgrading, please refer to Special Upgrades.
    • The Predicate Expression API is obsolete. The Aerospike Server and Client have scheduled removal with our next major Aerospike Server release. Use Aerospike Filter Expressions (added in version 5.2).
    • 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:
    • The configuration parameter batch-without-digests, now defaults to true, is deprecated and will be removed in six months. Customers using clients older than a year (around the time of Server 4.9 which introduced batch-without-digests) will now have to explicitly set the batch-without-digests configuration item to false.
    • 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.
    • The security context configuration items enable-security and enable-ldap have been removed. The Server will not start if either enable-security or enable-ldap is present in the configuration file.
    • Security will now be enabled simply by the presence of the security { } section in the configuration file. Similarly, LDAP will now be enabled simply by the presence of the ldap { } section within the security { } section of the configuration file.
    • To use XDR with ACL auth-mode must be explicitly configured.
    • We build on Red Hat Enterprise Linux (RHEL) 8 instead of CentOS 8 when creating rpm packages.
    • Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.

    Bug Fixes

    • Enterprise Only
      • [AER-6525] - (XDR) For single-bin, data-in-memory namespaces, shipping records will corrupt the index and may cause a crash.

    Known Issues

  • 5.7.0.15
    Release Date: March 31, 2022
    • For upgrading, or the unlikely event of downgrading, please refer to Special Upgrades.
    • The Predicate Expression API is obsolete. The Aerospike Server and Client have scheduled removal with our next major Aerospike Server release. Use Aerospike Filter Expressions (added in version 5.2).
    • 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:
    • The configuration parameter batch-without-digests, now defaults to true, is deprecated and will be removed in six months. Customers using clients older than a year (around the time of Server 4.9 which introduced batch-without-digests) will now have to explicitly set the batch-without-digests configuration item to false.
    • 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.
    • The security context configuration items enable-security and enable-ldap have been removed. The Server will not start if either enable-security or enable-ldap is present in the configuration file.
    • Security will now be enabled simply by the presence of the security { } section in the configuration file. Similarly, LDAP will now be enabled simply by the presence of the ldap { } section within the security { } section of the configuration file.
    • To use XDR with ACL auth-mode must be explicitly configured.
    • We build on Red Hat Enterprise Linux (RHEL) 8 instead of CentOS 8 when creating rpm packages.
    • Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.

    Bug Fixes

    • Enterprise & Community
      • [AER-6523] - (EXPRESSIONS) An empty expression may cause a crash, and a 1-byte expression operation with value zero is misinterpreted as a legacy predexp filter.
      • [AER-6524] - (QUERY) Background UDF/ops queries will leak memory.
    • Enterprise Only
      • [AER-6521] - (STORAGE) For storage-engine pmem namespaces, dynamically setting defrag-lwm-pct will set one-eighth the intended threshold.
      • [AER-6520] - (XDR) Removing multiple connector seed nodes in rapid succession may cause an assertion.

    Known Issues

  • 5.7.0.12
    Release Date: March 21, 2022
    • For upgrading, or the unlikely event of downgrading, please refer to Special Upgrades.
    • The Predicate Expression API is obsolete. The Aerospike Server and Client have scheduled removal with our next major Aerospike Server release. Use Aerospike Filter Expressions (added in version 5.2).
    • 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:
    • The configuration parameter batch-without-digests, now defaults to true, is deprecated and will be removed in six months. Customers using clients older than a year (around the time of Server 4.9 which introduced batch-without-digests) will now have to explicitly set the batch-without-digests configuration item to false.
    • 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.
    • The security context configuration items enable-security and enable-ldap have been removed. The Server will not start if either enable-security or enable-ldap is present in the configuration file.
    • Security will now be enabled simply by the presence of the security { } section in the configuration file. Similarly, LDAP will now be enabled simply by the presence of the ldap { } section within the security { } section of the configuration file.
    • To use XDR with ACL auth-mode must be explicitly configured.
    • We build on Red Hat Enterprise Linux (RHEL) 8 instead of CentOS 8 when creating rpm packages.
    • Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.

    Bug Fixes

    • Enterprise & Community
      • [AER-6519] - (UDF) A UDF that tries to return a list or map containing an as_rec element will cause an assertion.
    • Enterprise Only
      • [AER-6518] - (XDR) Dynamically adding/removing seed nodes and changing the DC context configuration item connector may cause an assertion.

    Known Issues

  • 5.7.0.11
    Release Date: March 8, 2022
    • For upgrading, or the unlikely event of downgrading, please refer to Special Upgrades.
    • The Predicate Expression API is obsolete. The Aerospike Server and Client have scheduled removal with our next major Aerospike Server release. Use Aerospike Filter Expressions (added in version 5.2).
    • 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:
    • The configuration parameter batch-without-digests, now defaults to true, is deprecated and will be removed in six months. Customers using clients older than a year (around the time of Server 4.9 which introduced batch-without-digests) will now have to explicitly set the batch-without-digests configuration item to false.
    • 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.
    • The security context configuration items enable-security and enable-ldap have been removed. The Server will not start if either enable-security or enable-ldap is present in the configuration file.
    • Security will now be enabled simply by the presence of the security { } section in the configuration file. Similarly, LDAP will now be enabled simply by the presence of the ldap { } section within the security { } section of the configuration file.
    • To use XDR with ACL auth-mode must be explicitly configured.
    • We build on Red Hat Enterprise Linux (RHEL) 8 instead of CentOS 8 when creating rpm packages.
    • Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.

    Bug Fixes

    • Enterprise & Community
      • [AER-6517] - (QUERY) A no-bins query with an expression filter may return records that it should not.
    • Enterprise Only
      • [AER-6516] - (XDR) When a namespace is disabled, the lag, in_queue, and in_progress statistics are not properly cleared.

    Known Issues

  • 5.7.0.10
    Release Date: January 13, 2022
    • For upgrading, or the unlikely event of downgrading, please refer to Special Upgrades.
    • The Predicate Expression API is obsolete. The Aerospike Server and Client have scheduled removal with our next major Aerospike Server release. Use Aerospike Filter Expressions (added in version 5.2).
    • 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:
    • The configuration parameter batch-without-digests, now defaults to true, is deprecated and will be removed in six months. Customers using clients older than a year (around the time of Server 4.9 which introduced batch-without-digests) will now have to explicitly set the batch-without-digests configuration item to false.
    • 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.
    • The security context configuration items enable-security and enable-ldap have been removed. The Server will not start if either enable-security or enable-ldap is present in the configuration file.
    • Security will now be enabled simply by the presence of the security { } section in the configuration file. Similarly, LDAP will now be enabled simply by the presence of the ldap { } section within the security { } section of the configuration file.
    • To use XDR with ACL auth-mode must be explicitly configured.
    • We build on Red Hat Enterprise Linux (RHEL) 8 instead of CentOS 8 when creating rpm packages.
    • Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.

    Bug Fixes

    • Enterprise & Community
      • [AER-6508] - (TLS) Race between TLS handshake and changing the certificate chain may cause a crash.

    Known Issues

  • 5.7.0.9
    Release Date: December 13, 2021
    • For upgrading, or the unlikely event of downgrading, please refer to Special Upgrades.
    • The Predicate Expression API is obsolete. The Aerospike Server and Client have scheduled removal with our next major Aerospike Server release. Use Aerospike Filter Expressions (added in version 5.2).
    • 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:
    • The configuration parameter batch-without-digests, now defaults to true, is deprecated and will be removed in six months. Customers using clients older than a year (around the time of Server 4.9 which introduced batch-without-digests) will now have to explicitly set the batch-without-digests configuration item to false.
    • 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.
    • The security context configuration items enable-security and enable-ldap have been removed. The Server will not start if either enable-security or enable-ldap is present in the configuration file.
    • Security will now be enabled simply by the presence of the security { } section in the configuration file. Similarly, LDAP will now be enabled simply by the presence of the ldap { } section within the security { } section of the configuration file.
    • To use XDR with ACL auth-mode must be explicitly configured.
    • We build on Red Hat Enterprise Linux (RHEL) 8 instead of CentOS 8 when creating rpm packages.
    • Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.

    Bug Fixes

    • Enterprise & Community
      • [AER-6502] - (SINDEX) Garbage collector reads start key from secondary index without locking, which may cause an assertion.

    Known Issues

  • 5.7.0.8
    Release Date: October 30, 2021
    • For upgrading, or the unlikely event of downgrading, please refer to Special Upgrades.
    • The Predicate Expression API is obsolete. The Aerospike Server and Client have scheduled removal with our next major Aerospike Server release. Use Aerospike Filter Expressions (added in version 5.2).
    • 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:
    • The configuration parameter batch-without-digests, now defaults to true, is deprecated and will be removed in six months. Customers using clients older than a year (around the time of Server 4.9 which introduced batch-without-digests) will now have to explicitly set the batch-without-digests configuration item to false.
    • 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.
    • The security context configuration items enable-security and enable-ldap have been removed. The Server will not start if either enable-security or enable-ldap is present in the configuration file.
    • Security will now be enabled simply by the presence of the security { } section in the configuration file. Similarly, LDAP will now be enabled simply by the presence of the ldap { } section within the security { } section of the configuration file.
    • To use XDR with ACL auth-mode must be explicitly configured.
    • We build on Red Hat Enterprise Linux (RHEL) 8 instead of CentOS 8 when creating rpm packages.
    • Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.

    Improvements

    • Enterprise & Community
      • [AER-6484] - (LOGGING) Added a ticker warning for write-commit-level 'master' transactions overloading fabric send queues.

    Bug Fixes

    • Enterprise & Community
      • [AER-6496] - (QUERY) Info commands to show all queries may cause a crash.
    • Enterprise Only
      • [AER-6486] - (STATS) For strong-consistency namespaces, re-replications that time out while queued internally will be reflected in the latency histogram.
      • [AER-6493] - (UDF) The method aerospike:exists() incorrectly returns true for a tombstone.

    Known Issues

  • 5.7.0.7
    Release Date: September 27, 2021
    • For upgrading, or the unlikely event of downgrading, please refer to Special Upgrades.
    • The Predicate Expression API is obsolete. The Aerospike Server and Client have scheduled removal with our next major Aerospike Server release. Use Aerospike Filter Expressions (added in version 5.2).
    • 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:
    • The configuration parameter batch-without-digests, now defaults to true, is deprecated and will be removed in six months. Customers using clients older than a year (around the time of Server 4.9 which introduced batch-without-digests) will now have to explicitly set the batch-without-digests configuration item to false.
    • 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.
    • The security context configuration items enable-security and enable-ldap have been removed. The Server will not start if either enable-security or enable-ldap is present in the configuration file.
    • Security will now be enabled simply by the presence of the security { } section in the configuration file. Similarly, LDAP will now be enabled simply by the presence of the ldap { } section within the security { } section of the configuration file.
    • To use XDR with ACL auth-mode must be explicitly configured.
    • We build on Red Hat Enterprise Linux (RHEL) 8 instead of CentOS 8 when creating rpm packages.
    • Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.

    Improvements

    • Enterprise & Community
      • [AER-6429] - (BATCH) Changed default value of service context configuration item batch-without-digests to true - the item is now deprecated.
      • [AER-6430] - (CLUSTERING) Reject the recluster info command if already reclustering.
      • [AER-6461] - (DEPLOYMENT) Sanity-check various system settings and server configuration items at startup.
      • [AER-6432] - (FABRIC) Handle fabric node list with a more granular hash and an improved node id hash function.
      • [AER-6459] - (GEO) Changed namespace geo2dsphere-within context configuration item max-level default from 30 to 20.
      • [AER-6455] - (INFO) Replaced scan-list and query-list with scan-show and query-show, renamed query-kill to query-abort.
      • [AER-6433] - (KVS) Switch write transactions from write-commit-level 'master' to 'all' if fabric send queues are overwhelmed.
      • [AER-6441] - (KVS) Reject replica writes if they are overwhelming the write queue.
      • [AER-6447] - (KVS) By default, exclude group and 'other' permissions when creating files.
      • [AER-6452] - (KVS) Removed non-essential sprig element counters, saving three bytes of overhead per sprig.
      • [AER-6470] - (KVS) Replaced fabric idle connection queue and storage device open file descriptor queues with lockless pools.
      • [AER-6471] - (KVS) Upgraded JEMalloc submodule to 'stable-4' version, plus modifications for Valgrind.
      • [AER-6434] - (LOGGING) Do not truncate the log file when (re)opening it during log rotation.
      • [AER-6460] - (LOGGING) Improved logging around duplicate node-ids.
      • [AER-6428] - (MIGRATION) Pause immigrations if they are overwhelming the write queue.
      • [AER-6450] - (SCAN) Queue dynamic set-index population jobs, to serialize them and reduce CPU usage.
      • [AER-6464] - (SINDEX) Secondary indexes store primary index references instead of digests - reduces memory footprint and improves garbage collection.
      • [AER-6476] - (STATS) Added system_thp_mem_kbytes statistic.
      • [AER-6436] - (STORAGE) Added namespace context configuration item max-record-size.
      • [AER-6468] - (STORAGE) Allow value of 0 for storage context configuration item defrag-startup-minimum, and made that the default.
    • Enterprise Only
      • [AER-6454] - (ACL) Moved configuration item session-ttl from 'ldap' to 'security' context, and ldap-login-threads (renamed as login-threads) from 'security' to 'ldap' context.
      • [AER-6456] - (ACL) Removed security context configuration items enable-security and enable-ldap.
      • [AER-6462] - (ACL) Added support for PKI authentication.
      • [AER-6453] - (AUDIT) Added separate 'audit' logging context so that auditing via a regular log sink will not include all 'security' context logs.
      • [AER-6431] - (STATS) Added unreplicated_records statistic for strong-consistency namespaces.
      • [AER-6445] - (STORAGE) Added storage context configuration item encryption-old-key-file to support rotation of encryption keys.
      • [AER-6449] - (STORAGE) Updated storage compression submodules.
      • [AER-6440] - (XDR) Disallow DC context configuration items auth-user and auth-password-file for connector DCs.
      • [AER-6443] - (XDR) An 'xdr' context in the configuration file is no longer required in order to configure DCs dynamically.

    Known Issues

    Updates

  • 5.6.0.25
    Release Date: October 3, 2022
    • The older Aerospike Connect Outbound versions do not work with Aerospike Server version 5.6 or newer. If you are using Aerospike Connect Outbound, you should upgrade respectively to:
      • Aerospike Connect for JMS - Outbound version 3.0.0 or newer
      • Aerospike Connect for Kafka - Outbound version 4.0.0 or newer
      • Aerospike Connect for Pulsar - Outbound version 2.0.0 or newer
      • XDR Proxy version 1.1.0 or newer
    • In Aerospike Server 5.5 or earlier, a UDF returning a Boolean value as a bin would be converted to 1 or 0. In Aerospike 5.6 or newer the value returns as true or false.
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • As of Aerospike Server 4.9 scans are correct. The scan priority, fail_on_cluster_change, and scan percent options, that were deprecated in Aerospike Server 4.9 are removed in Aerospike Server 5.6.
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Predicate Expression API will be removed in the Aerospike Server version 6.0 release. Use Aerospike Filter Expressions (added in version 5.2).
    • We have removed support for Ubuntu 16.04.
    • Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.

    Bug Fixes

    • Enterprise & Federal Only

    Known Issues

    Enterprise Download
  • 5.6.0.24
    Release Date: August 17, 2022
    • The older Aerospike Connect Outbound versions do not work with Aerospike Server version 5.6 or newer. If you are using Aerospike Connect Outbound, you should upgrade respectively to:
      • Aerospike Connect for JMS - Outbound version 3.0.0 or newer
      • Aerospike Connect for Kafka - Outbound version 4.0.0 or newer
      • Aerospike Connect for Pulsar - Outbound version 2.0.0 or newer
      • XDR Proxy version 1.1.0 or newer
    • In Aerospike Server 5.5 or earlier, a UDF returning a Boolean value as a bin would be converted to 1 or 0. In Aerospike 5.6 or newer the value returns as true or false.
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • As of Aerospike Server 4.9 scans are correct. The scan priority, fail_on_cluster_change, and scan percent options, that were deprecated in Aerospike Server 4.9 are removed in Aerospike Server 5.6.
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Predicate Expression API will be removed in the Aerospike Server version 6.0 release. Use Aerospike Filter Expressions (added in version 5.2).
    • We have removed support for Ubuntu 16.04.
    • 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-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

  • 5.6.0.23
    Release Date: August 4, 2022
    • The older Aerospike Connect Outbound versions do not work with Aerospike Server version 5.6 or newer. If you are using Aerospike Connect Outbound, you should upgrade respectively to:
      • Aerospike Connect for JMS - Outbound version 3.0.0 or newer
      • Aerospike Connect for Kafka - Outbound version 4.0.0 or newer
      • Aerospike Connect for Pulsar - Outbound version 2.0.0 or newer
      • XDR Proxy version 1.1.0 or newer
    • In Aerospike Server 5.5 or earlier, a UDF returning a Boolean value as a bin would be converted to 1 or 0. In Aerospike 5.6 or newer the value returns as true or false.
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • As of Aerospike Server 4.9 scans are correct. The scan priority, fail_on_cluster_change, and scan percent options, that were deprecated in Aerospike Server 4.9 are removed in Aerospike Server 5.6.
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Predicate Expression API will be removed in the Aerospike Server version 6.0 release. Use Aerospike Filter Expressions (added in version 5.2).
    • We have removed support for Ubuntu 16.04.
    • Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.

    Bug Fixes

    • Enterprise & 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 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

  • 5.6.0.22
    Release Date: June 30, 2022
    • The older Aerospike Connect Outbound versions do not work with Aerospike Server version 5.6 or newer. If you are using Aerospike Connect Outbound, you should upgrade respectively to:
      • Aerospike Connect for JMS - Outbound version 3.0.0 or newer
      • Aerospike Connect for Kafka - Outbound version 4.0.0 or newer
      • Aerospike Connect for Pulsar - Outbound version 2.0.0 or newer
      • XDR Proxy version 1.1.0 or newer
    • In Aerospike Server 5.5 or earlier, a UDF returning a Boolean value as a bin would be converted to 1 or 0. In Aerospike 5.6 or newer the value returns as true or false.
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • As of Aerospike Server 4.9 scans are correct. The scan priority, fail_on_cluster_change, and scan percent options, that were deprecated in Aerospike Server 4.9 are removed in Aerospike Server 5.6.
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Predicate Expression API will be removed in the Aerospike Server version 6.0 release. Use Aerospike Filter Expressions (added in version 5.2).
    • We have removed support for Ubuntu 16.04.
    • Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.

    Bug Fixes

    • Enterprise & Community
      • [AER-6539] - (EXPRESSIONS) Comparisons of expression trileans that include 'unknown' do not return 'unknown'.
      • [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 Only
      • [AER-6536] - (LOGGING) TLS I/O error may log incorrect errno.

    Known Issues

  • 5.6.0.21
    Release Date: April 20, 2022
    • The older Aerospike Connect Outbound versions do not work with Aerospike Server version 5.6 or newer. If you are using Aerospike Connect Outbound, you should upgrade respectively to:
      • Aerospike Connect for JMS - Outbound version 3.0.0 or newer
      • Aerospike Connect for Kafka - Outbound version 4.0.0 or newer
      • Aerospike Connect for Pulsar - Outbound version 2.0.0 or newer
      • XDR Proxy version 1.1.0 or newer
    • In Aerospike Server 5.5 or earlier, a UDF returning a Boolean value as a bin would be converted to 1 or 0. In Aerospike 5.6 or newer the value returns as true or false.
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • As of Aerospike Server 4.9 scans are correct. The scan priority, fail_on_cluster_change, and scan percent options, that were deprecated in Aerospike Server 4.9 are removed in Aerospike Server 5.6.
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Predicate Expression API will be removed in the Aerospike Server version 6.0 release. Use Aerospike Filter Expressions (added in version 5.2).
    • We have removed support for Ubuntu 16.04.
    • Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.

    Bug Fixes

    • Enterprise & 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 Only
      • [AER-6527] - (XDR) Dynamically removing seed nodes while trying to connect may cause connections to be skipped or cause a crash.

    Known Issues

  • 5.6.0.20
    Release Date: April 4, 2022
    • The older Aerospike Connect Outbound versions do not work with Aerospike Server version 5.6 or newer. If you are using Aerospike Connect Outbound, you should upgrade respectively to:
      • Aerospike Connect for JMS - Outbound version 3.0.0 or newer
      • Aerospike Connect for Kafka - Outbound version 4.0.0 or newer
      • Aerospike Connect for Pulsar - Outbound version 2.0.0 or newer
      • XDR Proxy version 1.1.0 or newer
    • In Aerospike Server 5.5 or earlier, a UDF returning a Boolean value as a bin would be converted to 1 or 0. In Aerospike 5.6 or newer the value returns as true or false.
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • As of Aerospike Server 4.9 scans are correct. The scan priority, fail_on_cluster_change, and scan percent options, that were deprecated in Aerospike Server 4.9 are removed in Aerospike Server 5.6.
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Predicate Expression API will be removed in the Aerospike Server version 6.0 release. Use Aerospike Filter Expressions (added in version 5.2).
    • We have removed support for Ubuntu 16.04.
    • Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.

    Bug Fixes

    • Enterprise Only
      • [AER-6525] - (XDR) For single-bin, data-in-memory namespaces, shipping records will corrupt the index and may cause a crash.

    Known Issues

  • 5.6.0.19
    Release Date: March 30, 2022
    • The older Aerospike Connect Outbound versions do not work with Aerospike Server version 5.6 or newer. If you are using Aerospike Connect Outbound, you should upgrade respectively to:
      • Aerospike Connect for JMS - Outbound version 3.0.0 or newer
      • Aerospike Connect for Kafka - Outbound version 4.0.0 or newer
      • Aerospike Connect for Pulsar - Outbound version 2.0.0 or newer
      • XDR Proxy version 1.1.0 or newer
    • In Aerospike Server 5.5 or earlier, a UDF returning a Boolean value as a bin would be converted to 1 or 0. In Aerospike 5.6 or newer the value returns as true or false.
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • As of Aerospike Server 4.9 scans are correct. The scan priority, fail_on_cluster_change, and scan percent options, that were deprecated in Aerospike Server 4.9 are removed in Aerospike Server 5.6.
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Predicate Expression API will be removed in the Aerospike Server version 6.0 release. Use Aerospike Filter Expressions (added in version 5.2).
    • We have removed support for Ubuntu 16.04.
    • Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.

    Bug Fixes

    • Enterprise & Community
      • [AER-6523] - (EXPRESSIONS) An empty expression may cause a crash, and a 1-byte expression operation with value zero is misinterpreted as a legacy predexp filter.
    • Enterprise Only
      • [AER-6521] - (STORAGE) For storage-engine pmem namespaces, dynamically setting defrag-lwm-pct will set one-eighth the intended threshold.
      • [AER-6520] - (XDR) Removing multiple connector seed nodes in rapid succession may cause an assertion.

    Known Issues

  • 5.6.0.17
    Release Date: March 21, 2022
    • The older Aerospike Connect Outbound versions do not work with Aerospike Server version 5.6 or newer. If you are using Aerospike Connect Outbound, you should upgrade respectively to:
      • Aerospike Connect for JMS - Outbound version 3.0.0 or newer
      • Aerospike Connect for Kafka - Outbound version 4.0.0 or newer
      • Aerospike Connect for Pulsar - Outbound version 2.0.0 or newer
      • XDR Proxy version 1.1.0 or newer
    • In Aerospike Server 5.5 or earlier, a UDF returning a Boolean value as a bin would be converted to 1 or 0. In Aerospike 5.6 or newer the value returns as true or false.
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • As of Aerospike Server 4.9 scans are correct. The scan priority, fail_on_cluster_change, and scan percent options, that were deprecated in Aerospike Server 4.9 are removed in Aerospike Server 5.6.
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Predicate Expression API will be removed in the Aerospike Server version 6.0 release. Use Aerospike Filter Expressions (added in version 5.2).
    • We have removed support for Ubuntu 16.04.
    • Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.

    Bug Fixes

    • Enterprise & Community
      • [AER-6519] - (UDF) A UDF that tries to return a list or map containing an as_rec element will cause an assertion.
    • Enterprise Only
      • [AER-6518] - (XDR) Dynamically adding/removing seed nodes and changing the DC context configuration item connector may cause an assertion.

    Known Issues

  • 5.6.0.16
    Release Date: March 8, 2022
    • The older Aerospike Connect Outbound versions do not work with Aerospike Server version 5.6 or newer. If you are using Aerospike Connect Outbound, you should upgrade respectively to:
      • Aerospike Connect for JMS - Outbound version 3.0.0 or newer
      • Aerospike Connect for Kafka - Outbound version 4.0.0 or newer
      • Aerospike Connect for Pulsar - Outbound version 2.0.0 or newer
      • XDR Proxy version 1.1.0 or newer
    • In Aerospike Server 5.5 or earlier, a UDF returning a Boolean value as a bin would be converted to 1 or 0. In Aerospike 5.6 or newer the value returns as true or false.
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • As of Aerospike Server 4.9 scans are correct. The scan priority, fail_on_cluster_change, and scan percent options, that were deprecated in Aerospike Server 4.9 are removed in Aerospike Server 5.6.
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Predicate Expression API will be removed in the Aerospike Server version 6.0 release. Use Aerospike Filter Expressions (added in version 5.2).
    • We have removed support for Ubuntu 16.04.
    • Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.

    Bug Fixes

    • Enterprise Only
      • [AER-6516] - (XDR) When a namespace is disabled, the lag, in_queue, and in_progress statistics are not properly cleared.

    Known Issues

  • 5.6.0.15
    Release Date: January 13, 2022
    • The older Aerospike Connect Outbound versions do not work with Aerospike Server version 5.6 or newer. If you are using Aerospike Connect Outbound, you should upgrade respectively to:
      • Aerospike Connect for JMS - Outbound version 3.0.0 or newer
      • Aerospike Connect for Kafka - Outbound version 4.0.0 or newer
      • Aerospike Connect for Pulsar - Outbound version 2.0.0 or newer
      • XDR Proxy version 1.1.0 or newer
    • In Aerospike Server 5.5 or earlier, a UDF returning a Boolean value as a bin would be converted to 1 or 0. In Aerospike 5.6 or newer the value returns as true or false.
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • As of Aerospike Server 4.9 scans are correct. The scan priority, fail_on_cluster_change, and scan percent options, that were deprecated in Aerospike Server 4.9 are removed in Aerospike Server 5.6.
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Predicate Expression API will be removed in the Aerospike Server version 6.0 release. Use Aerospike Filter Expressions (added in version 5.2).
    • We have removed support for Ubuntu 16.04.
    • Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.

    Bug Fixes

    • Enterprise & Community
      • [AER-6508] - (TLS) Race between TLS handshake and changing the certificate chain may cause a crash.

    Known Issues

  • 5.6.0.14
    Release Date: October 30, 2021
    • The older Aerospike Connect Outbound versions do not work with Aerospike Server version 5.6 or newer. If you are using Aerospike Connect Outbound, you should upgrade respectively to:
      • Aerospike Connect for JMS - Outbound version 3.0.0 or newer
      • Aerospike Connect for Kafka - Outbound version 4.0.0 or newer
      • Aerospike Connect for Pulsar - Outbound version 2.0.0 or newer
      • XDR Proxy version 1.1.0 or newer
    • In Aerospike Server 5.5 or earlier, a UDF returning a Boolean value as a bin would be converted to 1 or 0. In Aerospike 5.6 or newer the value returns as true or false.
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • As of Aerospike Server 4.9 scans are correct. The scan priority, fail_on_cluster_change, and scan percent options, that were deprecated in Aerospike Server 4.9 are removed in Aerospike Server 5.6.
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Predicate Expression API will be removed in the Aerospike Server version 6.0 release. Use Aerospike Filter Expressions (added in version 5.2).
    • We have removed support for Ubuntu 16.04.
    • Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.

    Bug Fixes

    • Enterprise Only
      • [AER-6486] - (STATS) For strong-consistency namespaces, re-replications that time out while queued internally will be reflected in the latency histogram.
      • [AER-6493] - (UDF) The method aerospike:exists() incorrectly returns true for a tombstone.

    Known Issues

  • 5.6.0.13
    Release Date: September 20, 2021
    • The older Aerospike Connect Outbound versions do not work with Aerospike Server version 5.6 or newer. If you are using Aerospike Connect Outbound, you should upgrade respectively to:
      • Aerospike Connect for JMS - Outbound version 3.0.0 or newer
      • Aerospike Connect for Kafka - Outbound version 4.0.0 or newer
      • Aerospike Connect for Pulsar - Outbound version 2.0.0 or newer
      • XDR Proxy version 1.1.0 or newer
    • In Aerospike Server 5.5 or earlier, a UDF returning a Boolean value as a bin would be converted to 1 or 0. In Aerospike 5.6 or newer the value returns as true or false.
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • As of Aerospike Server 4.9 scans are correct. The scan priority, fail_on_cluster_change, and scan percent options, that were deprecated in Aerospike Server 4.9 are removed in Aerospike Server 5.6.
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Predicate Expression API will be removed in the Aerospike Server version 6.0 release. Use Aerospike Filter Expressions (added in version 5.2).
    • We have removed support for Ubuntu 16.04.
    • Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.

    Bug Fixes

    • Enterprise & Community
      • [AER-6479] - (EXPRESSIONS) For data-in-memory namespaces, an expression let which returns the value of one of its variables may leak memory.
      • [AER-6481] - (KVS) When a service thread exits, its epoll queue's event file descriptor leaks.
      • [AER-6480] - (SCAN) A paginated scan on a set which is indexed may not return the correct records.
      • [AER-6482] - (STORAGE) When a device runs completely out of space, defrag becomes ineffective.
    • Enterprise Only

    Known Issues

  • 5.6.0.12
    Release Date: September 15, 2021
    • The older Aerospike Connect Outbound versions do not work with Aerospike Server version 5.6 or newer. If you are using Aerospike Connect Outbound, you should upgrade respectively to:
      • Aerospike Connect for JMS - Outbound version 3.0.0 or newer
      • Aerospike Connect for Kafka - Outbound version 4.0.0 or newer
      • Aerospike Connect for Pulsar - Outbound version 2.0.0 or newer
      • XDR Proxy version 1.1.0 or newer
    • In Aerospike Server 5.5 or earlier, a UDF returning a Boolean value as a bin would be converted to 1 or 0. In Aerospike 5.6 or newer the value returns as true or false.
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • As of Aerospike Server 4.9 scans are correct. The scan priority, fail_on_cluster_change, and scan percent options, that were deprecated in Aerospike Server 4.9 are removed in Aerospike Server 5.6.
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Predicate Expression API will be removed in the Aerospike Server version 6.0 release. Use Aerospike Filter Expressions (added in version 5.2).
    • We have removed support for Ubuntu 16.04.
    • Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.

    Bug Fixes

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted.

    Known Issues

  • 5.6.0.11
    Release Date: September 2, 2021
    • The older Aerospike Connect Outbound versions do not work with Aerospike Server version 5.6 or newer. If you are using Aerospike Connect Outbound, you should upgrade respectively to:
      • Aerospike Connect for JMS - Outbound version 3.0.0 or newer
      • Aerospike Connect for Kafka - Outbound version 4.0.0 or newer
      • Aerospike Connect for Pulsar - Outbound version 2.0.0 or newer
      • XDR Proxy version 1.1.0 or newer
    • In Aerospike Server 5.5 or earlier, a UDF returning a Boolean value as a bin would be converted to 1 or 0. In Aerospike 5.6 or newer the value returns as true or false.
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • As of Aerospike Server 4.9 scans are correct. The scan priority, fail_on_cluster_change, and scan percent options, that were deprecated in Aerospike Server 4.9 are removed in Aerospike Server 5.6.
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Predicate Expression API will be removed in the Aerospike Server version 6.0 release. Use Aerospike Filter Expressions (added in version 5.2).
    • We have removed support for Ubuntu 16.04.
    • Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.

    Improvements

    • Enterprise & Community
      • [AER-6475] - (GEO) For data-in-memory namespaces, when trimming GeoJSON particles, reallocate into the appropriate namespace arena.

    Bug Fixes

    • Enterprise & Community
      • [AER-6473] - (EXPRESSIONS) For data-in-memory namespaces, an expression let which returns the value of one of its variables will cause a double-free.
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces.

    Known Issues

  • 5.6.0.10
    Release Date: August 4, 2021
    • The older Aerospike Connect Outbound versions do not work with Aerospike Server version 5.6 or newer. If you are using Aerospike Connect Outbound, you should upgrade respectively to:
      • Aerospike Connect for JMS - Outbound version 3.0.0 or newer
      • Aerospike Connect for Kafka - Outbound version 4.0.0 or newer
      • Aerospike Connect for Pulsar - Outbound version 2.0.0 or newer
      • XDR Proxy version 1.1.0 or newer
    • In Aerospike Server 5.5 or earlier, a UDF returning a Boolean value as a bin would be converted to 1 or 0. In Aerospike 5.6 or newer the value returns as true or false.
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • As of Aerospike Server 4.9 scans are correct. The scan priority, fail_on_cluster_change, and scan percent options, that were deprecated in Aerospike Server 4.9 are removed in Aerospike Server 5.6.
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Predicate Expression API will be removed in the Aerospike Server version 6.0 release. Use Aerospike Filter Expressions (added in version 5.2).
    • We have removed support for Ubuntu 16.04.
    • Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.

    Bug Fixes

    • Enterprise Only
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash.

    Known Issues

  • 5.6.0.9
    Release Date: July 22, 2021
    • The older Aerospike Connect Outbound versions do not work with Aerospike Server version 5.6 or newer. If you are using Aerospike Connect Outbound, you should upgrade respectively to:
      • Aerospike Connect for JMS - Outbound version 3.0.0 or newer
      • Aerospike Connect for Kafka - Outbound version 4.0.0 or newer
      • Aerospike Connect for Pulsar - Outbound version 2.0.0 or newer
      • XDR Proxy version 1.1.0 or newer
    • In Aerospike Server 5.5 or earlier, a UDF returning a Boolean value as a bin would be converted to 1 or 0. In Aerospike 5.6 or newer the value returns as true or false.
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • As of Aerospike Server 4.9 scans are correct. The scan priority, fail_on_cluster_change, and scan percent options, that were deprecated in Aerospike Server 4.9 are removed in Aerospike Server 5.6.
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Predicate Expression API will be removed in the Aerospike Server version 6.0 release. Use Aerospike Filter Expressions (added in version 5.2).
    • We have removed support for Ubuntu 16.04.
    • Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.

    Bug Fixes

    • Enterprise & Community
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash.

    Known Issues

  • 5.6.0.8
    Release Date: July 19, 2021
    • The older Aerospike Connect Outbound versions do not work with Aerospike Server version 5.6 or newer. If you are using Aerospike Connect Outbound, you should upgrade respectively to:
      • Aerospike Connect for JMS - Outbound version 3.0.0 or newer
      • Aerospike Connect for Kafka - Outbound version 4.0.0 or newer
      • Aerospike Connect for Pulsar - Outbound version 2.0.0 or newer
      • XDR Proxy version 1.1.0 or newer
    • In Aerospike Server 5.5 or earlier, a UDF returning a Boolean value as a bin would be converted to 1 or 0. In Aerospike 5.6 or newer the value returns as true or false.
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • As of Aerospike Server 4.9 scans are correct. The scan priority, fail_on_cluster_change, and scan percent options, that were deprecated in Aerospike Server 4.9 are removed in Aerospike Server 5.6.
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Predicate Expression API will be removed in the Aerospike Server version 6.0 release. Use Aerospike Filter Expressions (added in version 5.2).
    • We have removed support for Ubuntu 16.04.
    • Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.

    Bug Fixes

    • Enterprise Only
      • [AER-6451] - (KVS) Race condition between sprig element counters and changing sprig roots when rebuilding index during warm restart may cause a crash.

    Known Issues

  • 5.6.0.7
    Release Date: June 22, 2021
    • The older Aerospike Connect Outbound versions do not work with Aerospike Server version 5.6 or newer. If you are using Aerospike Connect Outbound, you should upgrade respectively to:
      • Aerospike Connect for JMS - Outbound version 3.0.0 or newer
      • Aerospike Connect for Kafka - Outbound version 4.0.0 or newer
      • Aerospike Connect for Pulsar - Outbound version 2.0.0 or newer
      • XDR Proxy version 1.1.0 or newer
    • In Aerospike Server 5.5 or earlier, a UDF returning a Boolean value as a bin would be converted to 1 or 0. In Aerospike 5.6 or newer the value returns as true or false.
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • As of Aerospike Server 4.9 scans are correct. The scan priority, fail_on_cluster_change, and scan percent options, that were deprecated in Aerospike Server 4.9 are removed in Aerospike Server 5.6.
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Predicate Expression API will be removed in the Aerospike Server version 6.0 release. Use Aerospike Filter Expressions (added in version 5.2).
    • We have removed support for Ubuntu 16.04.
    • Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.

    Bug Fixes

    • Enterprise & Community
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps.
    • Enterprise Only
      • [AER-6446] - (SCAN) Race condition when populating set indexes during warm restarts may cause a crash.

    Known Issues

  • 5.6.0.5
    Release Date: May 27, 2021
    • The older Aerospike Connect Outbound versions do not work with Aerospike Server version 5.6 or newer. If you are using Aerospike Connect Outbound, you should upgrade respectively to:
      • Aerospike Connect for JMS - Outbound version 3.0.0 or newer
      • Aerospike Connect for Kafka - Outbound version 4.0.0 or newer
      • Aerospike Connect for Pulsar - Outbound version 2.0.0 or newer
      • XDR Proxy version 1.1.0 or newer
    • In Aerospike Server 5.5 or earlier, a UDF returning a Boolean value as a bin would be converted to 1 or 0. In Aerospike 5.6 or newer the value returns as true or false.
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • As of Aerospike Server 4.9 scans are correct. The scan priority, fail_on_cluster_change, and scan percent options, that were deprecated in Aerospike Server 4.9 are removed in Aerospike Server 5.6.
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Predicate Expression API will be removed in the Aerospike Server version 6.0 release. Use Aerospike Filter Expressions (added in version 5.2).
    • We have removed support for Ubuntu 16.04.
    • Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.

    Bug Fixes

    • Enterprise & Community
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes.
      • [AER-6439] - (SCAN) Disabling a set index while it is being populated may result in a deadlock.

    Known Issues

  • 5.6.0.4
    Release Date: May 24, 2021
    • The older Aerospike Connect Outbound versions do not work with Aerospike Server version 5.6 or newer. If you are using Aerospike Connect Outbound, you should upgrade respectively to:
      • Aerospike Connect for JMS - Outbound version 3.0.0 or newer
      • Aerospike Connect for Kafka - Outbound version 4.0.0 or newer
      • Aerospike Connect for Pulsar - Outbound version 2.0.0 or newer
      • XDR Proxy version 1.1.0 or newer
    • In Aerospike Server 5.5 or earlier, a UDF returning a Boolean value as a bin would be converted to 1 or 0. In Aerospike 5.6 or newer the value returns as true or false.
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • As of Aerospike Server 4.9 scans are correct. The scan priority, fail_on_cluster_change, and scan percent options, that were deprecated in Aerospike Server 4.9 are removed in Aerospike Server 5.6.
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Predicate Expression API will be removed in the Aerospike Server version 6.0 release. Use Aerospike Filter Expressions (added in version 5.2).
    • We have removed support for Ubuntu 16.04.
    • Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.

    Bug Fixes

    • Enterprise Only
      • [AER-6427] - (KVS) For data-in-index namespaces, durable deletes will cause an unnecessary assertion on a warm restart.
      • [AER-6437] - (KVS) Improper initialization of set index trees during warm restart may eventually cause a crash.

    Known Issues

  • 5.6.0.3
    Release Date: May 10, 2021
    • Aerospike Server release 5.6.0.3 contained a bug that may cause a server crash (AER-6437).
      • If you are running Aerospike Server version 5.6, we recommend that you upgrade to the latest release (currently 5.6.0.4).
    • The older Aerospike Connect Outbound versions do not work with Aerospike Server version 5.6 or newer. If you are using Aerospike Connect Outbound, you should upgrade respectively to:
      • Aerospike Connect for JMS - Outbound version 3.0.0 or newer
      • Aerospike Connect for Kafka - Outbound version 4.0.0 or newer
      • Aerospike Connect for Pulsar - Outbound version 2.0.0 or newer
      • XDR Proxy version 1.1.0 or newer
    • In Aerospike Server 5.5 or earlier, a UDF returning a Boolean value as a bin would be converted to 1 or 0. In Aerospike 5.6 or newer the value returns as true or false.
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • As of Aerospike Server 4.9 scans are correct. The scan priority, fail_on_cluster_change, and scan percent options, that were deprecated in Aerospike Server 4.9 are removed in Aerospike Server 5.6.
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Predicate Expression API will be removed in the Aerospike Server version 6.0 release. Use Aerospike Filter Expressions (added in version 5.2).
    • We have removed support for Ubuntu 16.04.
    • Use Prometheus Exporter version 1.2.1 or later to run Prometheus Exporter with this version of Aerospike Server.

    New Features

    • Enterprise & Community
      • [AER-6400] - (EXPRESSIONS) Added support for Operation Expressions.
      • [AER-6399] - (EXPRESSIONS) Added support for arithmetic, branching, and variables to expressions.
      • [AER-6392] - (KVS) Added support for Boolean particle type.
      • [AER-6421] - (SCAN) Added set context configuration item enable-index to maintain a set-specific index for scans of the set.
    • Enterprise Only
      • [AER-6416] - (ACL) Added support for rate quotas, including per-user rate statistics.

    Improvements

    • Enterprise & Community
      • [AER-6422] - (EXPRESSIONS) Added a ticker warning for use of the deprecated predexp API.
      • [AER-6398] - (FABRIC) Handle fabric node list with more granular locking.
      • [AER-6407] - (KVS) Added service context configuration item os-group-perms to add group permissions when creating files.
      • [AER-6415] - (KVS) Removed 'set-' prefix from configuration items in the namespace 'set' context.
      • [AER-6425] - (KVS) Changed transient detached threads to run from a thread pool.
      • [AER-6409] - (NETWORK) Added network service context configuration item disable-localhost to prevent listening on localhost.
      • [AER-6408] - (SCAN) Removed support for non partition-based basic scans, and deprecated scan options.
      • [AER-6424] - (STATS) Added more complete file descriptor stats for client, heartbeat, and fabric.
    • Enterprise Only
      • [AER-6393] - (AUDIT) Added 'log' and 'syslog' context configuration items 'report-data-op-role' and 'report-data-op-user' to audit by role or user.
      • [AER-6394] - (AUDIT) Made all 'log' and 'syslog' context 'report-...' configuration items dynamic and properly echoed via get-config.
      • [AER-6417] - (ACL) Included number of per-user open connections in 'show user(s)' output.
      • [AER-6410] - (STATS) Added index_flash_alloc_bytes and index_flash_alloc_pct statistics.
      • [AER-6405] - (XDR) Added new stats for tracking bin-convergence conflicts.
      • [AER-6406] - (XDR) Always send the record last-update-time to connector destinations.

    Known Issues

    Updates

  • 5.5.0.27
    Release Date: April 20, 2022
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise & 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 Only
      • [AER-6527] - (XDR) Dynamically removing seed nodes while trying to connect may cause connections to be skipped or cause a crash.

    Known Issues

    Enterprise Download
  • 5.5.0.26
    Release Date: April 4, 2022
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise Only
      • [AER-6525] - (XDR) For single-bin, data-in-memory namespaces, shipping records will corrupt the index and may cause a crash.

    Known Issues

  • 5.5.0.25
    Release Date: March 30, 2022
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise & Community
      • [AER-6523] - (EXPRESSIONS) An empty expression may cause a crash, and a 1-byte expression operation with value zero is misinterpreted as a legacy predexp filter.
    • Enterprise Only
      • [AER-6521] - (STORAGE) For storage-engine pmem namespaces, dynamically setting defrag-lwm-pct will set one-eighth the intended threshold.
      • [AER-6520] - (XDR) Removing multiple connector seed nodes in rapid succession may cause an assertion.

    Known Issues

  • 5.5.0.23
    Release Date: March 21, 2022
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise & Community
      • [AER-6519] - (UDF) A UDF that tries to return a list or map containing an as_rec element will cause an assertion.
    • Enterprise Only
      • [AER-6518] - (XDR) Dynamically adding/removing seed nodes and changing the DC context configuration item connector may cause an assertion.

    Known Issues

  • 5.5.0.22
    Release Date: March 8, 2022
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise Only
      • [AER-6516] - (XDR) When a namespace is disabled, the lag, in_queue, and in_progress statistics are not properly cleared.

    Known Issues

  • 5.5.0.21
    Release Date: January 13, 2022
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise & Community
      • [AER-6508] - (TLS) Race between TLS handshake and changing the certificate chain may cause a crash.

    Known Issues

  • 5.5.0.20
    Release Date: October 30, 2021
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise Only
      • [AER-6486] - (STATS) For strong-consistency namespaces, re-replications that time out while queued internally will be reflected in the latency histogram.
      • [AER-6493] - (UDF) The method aerospike:exists() incorrectly returns true for a tombstone.

    Known Issues

  • 5.5.0.19
    Release Date: September 20, 2021
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise & Community
      • [AER-6481] - (KVS) When a service thread exits, its epoll queue's event file descriptor leaks.
      • [AER-6482] - (STORAGE) When a device runs completely out of space, defrag becomes ineffective.
    • Enterprise Only

    Known Issues

  • 5.5.0.18
    Release Date: September 15, 2021
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted.

    Known Issues

  • 5.5.0.17
    Release Date: September 2, 2021
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Improvements

    • Enterprise & Community
      • [AER-6475] - (GEO) For data-in-memory namespaces, when trimming GeoJSON particles, reallocate into the appropriate namespace arena.

    Bug Fixes

    • Enterprise & Community
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces.

    Known Issues

  • 5.5.0.16
    Release Date: August 4, 2021
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise Only
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash.

    Known Issues

  • 5.5.0.15
    Release Date: July 22, 2021
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise & Community
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash.

    Known Issues

  • 5.5.0.14
    Release Date: July 19, 2021
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise Only
      • [AER-6451] - (KVS) Race condition between sprig element counters and changing sprig roots when rebuilding index during warm restart may cause a crash.

    Known Issues

  • 5.5.0.13
    Release Date: June 24, 2021
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise & Community
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps.

    Known Issues

  • 5.5.0.12
    Release Date: May 28, 2021
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise & Community
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes.

    Known Issues

  • 5.5.0.11
    Release Date: May 25, 2021
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise Only
      • [AER-6427] - (KVS) For data-in-index namespaces, durable deletes will cause an unnecessary assertion on a warm restart.

    Known Issues

  • 5.5.0.10
    Release Date: May 10, 2021
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise Only
      • [AER-6420] - (DEPLOYMENT) Feature key parser does not handle DOS line endings.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing.

    Known Issues

  • 5.5.0.9
    Release Date: April 6, 2021
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Improvements

    • Enterprise Only
      • [AER-6419] - (DEPLOYMENT) Use only non-zero values when combining cluster-nodes-limit from different feature key files to determine the effective limit.

    Bug Fixes

    • Enterprise & Community
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory.

    Known Issues

  • 5.5.0.8
    Release Date: April 2, 2021
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise & Community
      • [AER-6414] - (UDF) For namespaces with data not in memory, UDF replications will not adjust the secondary index.

    Known Issues

  • 5.5.0.7
    Release Date: March 29, 2021
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise & Community
      • [AER-6412] - (QUERY) If a query transaction setup fails in certain ways, improper cleanup may cause a crash.
    • Enterprise Only
      • [AER-6413] - (LDAP) Small memory leak during LDAP login process.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash.

    Known Issues

  • 5.5.0.4
    Release Date: March 12, 2021
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise & Community
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical.
      • [AER-6402] - (SINDEX) When iterating through secondary indexes to adjust for changing list bin values, inactive indexes are incorrectly skipped, which may cause a crash.
      • [AER-6396] - (STATS) The dup_res_ask statistic may be incorrect for write transactions.
    • Enterprise Only
      • [AER-6403] - (KVS) Corrupt bin-ops from clients are not properly checked before endian swapping, and may cause a crash.
      • [AER-6404] - (KVS) For single-bin, data-in-memory namespaces, durable deletes may cause a crash on writing replicas or on subsequent restarts.

    Known Issues

  • 5.5.0.3
    Release Date: February 12, 2021
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise Only
      • [AER-6390] - (XDR) For strong-consistency namespaces, when DC namespace context configuration item bin-policy is not 'all', shipping records that are unreplicated may miss some bins.

    Known Issues

  • 5.5.0.2
    Release Date: February 5, 2021
    • Downgrading from Aerospike Database version 5.5 or newer to version 5.4 or version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.4 to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    New Features

    • Enterprise & Community
      • [AER-6389] - (PACKAGING) Removed support for CentOS 6.

    Improvements

    • Enterprise & Community
      • [AER-6388] - (DEPLOYMENT) When starting Aerospike under systemd, wait for the network to be available.
      • [AER-6387] - (STATS) Added duplicate resolution statistics and log ticker line.
      • [AER-6385] - (UDF) Unpack msgpack booleans as booleans instead of converting them to integers.
    • Enterprise Only
      • [AER-6386] - (DEPLOYMENT) Added support for fetching and using multiple feature keys in one server instance.
      • [AER-6370] - (XDR) Added support for record deletion with bin level convergence.
      • [AER-6384] - (XDR) Added DC context configuration item max-recoveries-interleaved to limit the number of partitions to recover concurrently.

    Known Issues

    Updates

  • 5.4.0.23
    Release Date: January 13, 2022
    • Downgrading from Aerospike Database version 5.4 or newer to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise & Community
      • [AER-6508] - (TLS) Race between TLS handshake and changing the certificate chain may cause a crash.

    Known Issues

    Enterprise Download
  • 5.4.0.22
    Release Date: October 30, 2021
    • Downgrading from Aerospike Database version 5.4 or newer to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise Only
      • [AER-6486] - (STATS) For strong-consistency namespaces, re-replications that time out while queued internally will be reflected in the latency histogram.
      • [AER-6493] - (UDF) The method aerospike:exists() incorrectly returns true for a tombstone.

    Known Issues

  • 5.4.0.21
    Release Date: September 20, 2021
    • Downgrading from Aerospike Database version 5.4 or newer to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise & Community
      • [AER-6481] - (KVS) When a service thread exits, its epoll queue's event file descriptor leaks.
      • [AER-6482] - (STORAGE) When a device runs completely out of space, defrag becomes ineffective.
    • Enterprise Only

    Known Issues

  • 5.4.0.20
    Release Date: September 15, 2021
    • Downgrading from Aerospike Database version 5.4 or newer to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted.

    Known Issues

  • 5.4.0.19
    Release Date: September 2, 2021
    • Downgrading from Aerospike Database version 5.4 or newer to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Improvements

    • Enterprise & Community
      • [AER-6475] - (GEO) For data-in-memory namespaces, when trimming GeoJSON particles, reallocate into the appropriate namespace arena.

    Bug Fixes

    • Enterprise & Community
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces.

    Known Issues

  • 5.4.0.18
    Release Date: August 4, 2021
    • Downgrading from Aerospike Database version 5.4 or newer to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise Only
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash.

    Known Issues

  • 5.4.0.17
    Release Date: July 22, 2021
    • Downgrading from Aerospike Database version 5.4 or newer to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise & Community
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash.

    Known Issues

  • 5.4.0.16
    Release Date: July 19, 2021
    • Downgrading from Aerospike Database version 5.4 or newer to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise Only
      • [AER-6451] - (KVS) Race condition between sprig element counters and changing sprig roots when rebuilding index during warm restart may cause a crash.

    Known Issues

  • 5.4.0.15
    Release Date: June 24, 2021
    • Downgrading from Aerospike Database version 5.4 or newer to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise & Community
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps.

    Known Issues

  • 5.4.0.14
    Release Date: May 28, 2021
    • Downgrading from Aerospike Database version 5.4 or newer to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise & Community
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes.

    Known Issues

  • 5.4.0.13
    Release Date: May 25, 2021
    • Downgrading from Aerospike Database version 5.4 or newer to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise Only
      • [AER-6427] - (KVS) For data-in-index namespaces, durable deletes will cause an unnecessary assertion on a warm restart.

    Known Issues

  • 5.4.0.12
    Release Date: May 10, 2021
    • Downgrading from Aerospike Database version 5.4 or newer to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise Only
      • [AER-6420] - (DEPLOYMENT) Feature key parser does not handle DOS line endings.
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing.

    Known Issues

  • 5.4.0.11
    Release Date: April 6, 2021
    • Downgrading from Aerospike Database version 5.4 or newer to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise & Community
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory.

    Known Issues

  • 5.4.0.10
    Release Date: April 2, 2021
    • Downgrading from Aerospike Database version 5.4 or newer to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise & Community
      • [AER-6414] - (UDF) For namespaces with data not in memory, UDF replications will not adjust the secondary index.

    Known Issues

  • 5.4.0.9
    Release Date: March 29, 2021
    • Downgrading from Aerospike Database version 5.4 or newer to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise & Community
      • [AER-6412] - (QUERY) If a query transaction setup fails in certain ways, improper cleanup may cause a crash.
    • Enterprise Only
      • [AER-6413] - (LDAP) Small memory leak during LDAP login process.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash.

    Known Issues

  • 5.4.0.6
    Release Date: March 12, 2021
    • Downgrading from Aerospike Database version 5.4 or newer to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise & Community
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical.
      • [AER-6402] - (SINDEX) When iterating through secondary indexes to adjust for changing list bin values, inactive indexes are incorrectly skipped, which may cause a crash.
    • Enterprise Only
      • [AER-6403] - (KVS) Corrupt bin-ops from clients are not properly checked before endian swapping, and may cause a crash.
      • [AER-6404] - (KVS) For single-bin, data-in-memory namespaces, durable deletes may cause a crash on writing replicas or on subsequent restarts.

    Known Issues

  • 5.4.0.5
    Release Date: February 12, 2021
    • Downgrading from Aerospike Database version 5.4 or newer to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise Only
      • [AER-6390] - (XDR) For strong-consistency namespaces, when DC namespace context configuration item bin-policy is not 'all', shipping records that are unreplicated may miss some bins.

    Known Issues

  • 5.4.0.4
    Release Date: January 30, 2021
    • Downgrading from Aerospike Database version 5.4 or newer to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise & Community
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated.
    • Enterprise Only
      • [AER-6382] - (LDAP) When connecting to LDAP server, TLS handshake occasionally fails.
      • [AER-6381] - (XDR) If a record expires between XDR reading and shipping, improper TTL will be shipped.
      • [AER-6383] - (XDR) If using bin convergence, UDF writes may be incorrectly rejected.

    Known Issues

  • 5.4.0.3
    Release Date: January 25, 2021
    • Downgrading from Aerospike Database version 5.4 or newer to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Improvements

    • Enterprise Only
      • [AER-6377] - (XDR) Added service context configuration item downgrading, to enable stripping bin metadata from records sent to older nodes.

    Bug Fixes

    • Enterprise Only
      • [AER-6376] - (LDAP) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library.
      • [AER-6378] - (ACL) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges.

    Known Issues

  • 5.4.0.2
    Release Date: January 15, 2021
    • Downgrading from Aerospike Database version 5.4 or newer to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise Only
      • [AER-6366] - (XDR) Dynamically removing a connector seed node may cause a crash.
      • [AER-6369] - (XDR) When shipping the first record on a connection, if all bins are filtered out, a crash may result.

    Known Issues

  • 5.4.0.1
    Release Date: January 13, 2021
    • Downgrading from Aerospike Database version 5.4 or newer to version 5.3 or version 5.2 (where XDR bin convergence has been used). Refer to Special Upgrades.
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    New Features

    • Enterprise Only
      • [AER-6299] - (XDR) Added bin level convergence for active-active scenarios.

    Improvements

    • Enterprise & Community
      • [AER-6367] - (KVS) For namespaces with data-in-memory true, reduced memory cost per bin by one byte.
      • [AER-6359] - (LOGGING) Changed warnings to detail level for CDT, HLL, and bitwise blob operations that fail due to policy violations.
      • [AER-6364] - (LOGGING) Changed logging level for 'starting/finished basic scan job...' messages from info to debug.
    • Enterprise Only
      • [AER-6354] - (DEPLOYMENT) Added support for fetching feature key from Vault or from an environment variable.
      • [AER-6355] - (DEPLOYMENT) Added support for feature-key-version 2.
      • [AER-6362] - (XDR) The xdr-get-filter info command now displays filter expressions in a logical language instead of as a base64 string.

    Bug Fixes

    • Enterprise & Community
      • [AER-6340] - (KVS) HLL string or blob elements sized 31 to 254 bytes may be treated differently depending on msgpack standard.

    Known Issues

  • 5.3.0.28
    Release Date: January 13, 2022
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise & Community
      • [AER-6508] - (TLS) Race between TLS handshake and changing the certificate chain may cause a crash.

    Known Issues

    Enterprise Download
  • 5.3.0.27
    Release Date: October 30, 2021
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise Only
      • [AER-6486] - (STATS) For strong-consistency namespaces, re-replications that time out while queued internally will be reflected in the latency histogram.
      • [AER-6493] - (UDF) The method aerospike:exists() incorrectly returns true for a tombstone.

    Known Issues

  • 5.3.0.26
    Release Date: September 20, 2021
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise & Community
      • [AER-6481] - (KVS) When a service thread exits, its epoll queue's event file descriptor leaks.
      • [AER-6482] - (STORAGE) When a device runs completely out of space, defrag becomes ineffective.
    • Enterprise Only

    Known Issues

  • 5.3.0.25
    Release Date: September 15, 2021
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted.

    Known Issues

  • 5.3.0.24
    Release Date: September 2, 2021
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Improvements

    • Enterprise & Community
      • [AER-6475] - (GEO) For data-in-memory namespaces, when trimming GeoJSON particles, reallocate into the appropriate namespace arena.

    Bug Fixes

    • Enterprise & Community
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces.

    Known Issues

  • 5.3.0.23
    Release Date: August 4, 2021
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise Only
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash.

    Known Issues

  • 5.3.0.22
    Release Date: July 22, 2021
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise & Community
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash.

    Known Issues

  • 5.3.0.21
    Release Date: July 19, 2021
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise Only
      • [AER-6451] - (KVS) Race condition between sprig element counters and changing sprig roots when rebuilding index during warm restart may cause a crash.

    Known Issues

  • 5.3.0.20
    Release Date: June 24, 2021
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise & Community
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps.

    Known Issues

  • 5.3.0.19
    Release Date: May 28, 2021
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise & Community
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes.

    Known Issues

  • 5.3.0.18
    Release Date: May 25, 2021
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise Only
      • [AER-6427] - (KVS) For data-in-index namespaces, durable deletes will cause an unnecessary assertion on a warm restart.

    Known Issues

  • 5.3.0.17
    Release Date: May 10, 2021
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise Only
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing.

    Known Issues

  • 5.3.0.16
    Release Date: April 6, 2021
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise & Community
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory.

    Known Issues

  • 5.3.0.15
    Release Date: April 2, 2021
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise & Community
      • [AER-6414] - (UDF) For namespaces with data not in memory, UDF replications will not adjust the secondary index.

    Known Issues

  • 5.3.0.14
    Release Date: March 29, 2021
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise & Community
      • [AER-6412] - (QUERY) If a query transaction setup fails in certain ways, improper cleanup may cause a crash.
    • Enterprise Only
      • [AER-6413] - (LDAP) Small memory leak during LDAP login process.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash.

    Known Issues

  • 5.3.0.11
    Release Date: March 12, 2021
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise & Community
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical.
      • [AER-6402] - (SINDEX) When iterating through secondary indexes to adjust for changing list bin values, inactive indexes are incorrectly skipped, which may cause a crash.
    • Enterprise Only
      • [AER-6404] - (KVS) For single-bin, data-in-memory namespaces, durable deletes may cause a crash on writing replicas or on subsequent restarts.

    Known Issues

  • 5.3.0.10
    Release Date: February 12, 2021
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise Only
      • [AER-6390] - (XDR) For strong-consistency namespaces, when DC namespace context configuration item bin-policy is not 'all', shipping records that are unreplicated may miss some bins.

    Known Issues

  • 5.3.0.9
    Release Date: January 30, 2021
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise & Community
      • [AER-6380] - (STATS) The 'batch-sub-restart' microbenchmark histogram is never populated.
    • Enterprise Only
      • [AER-6382] - (LDAP) When connecting to LDAP server, TLS handshake occasionally fails.
      • [AER-6381] - (XDR) If a record expires between XDR reading and shipping, improper TTL will be shipped.

    Known Issues

  • 5.3.0.8
    Release Date: January 25, 2021
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Improvements

    • Enterprise Only
      • [AER-6377] - (XDR) Added service context configuration item downgrading, to enable stripping bin metadata from records sent to older nodes.

    Bug Fixes

    • Enterprise Only
      • [AER-6376] - (LDAP) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library.
      • [AER-6378] - (ACL) When a user’s permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges.

    Known Issues

  • 5.3.0.7
    Release Date: January 15, 2021
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise Only
      • [AER-6366] - (XDR) Dynamically removing a connector seed node may cause a crash.
      • [AER-6369] - (XDR) When shipping the first record on a connection, if all bins are filtered out, a crash may result.

    Known Issues

  • 5.3.0.6
    Release Date: January 7, 2021
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise Only
      • [AER-6365] - (XDR) Reverts behavior change in AER-6240 as empty node addition may reject a lagging last ship time from the acting master, which may result in records not shipping.

    Known Issues

  • 5.3.0.5
    Release Date: January 4, 2021
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Improvements

    • Enterprise & Community
      • [AER-6357] - (KVS) Handle exceeding the OS file descriptor limit gracefully, without asserting.
    • Enterprise Only
      • [AER-6360] - (XDR) Close idle connections when DC context configuration item max-used-service-threads is decreased dynamically.

    Bug Fixes

    • Enterprise & Community
      • [AER-6358] - (KVS) For single-bin, data-in-memory namespaces, unwinding on failing a write operation may incorrectly free the original bin particle.
    • Enterprise Only
      • [AER-6363] - (KVS) A write or a UDF that deletes all of a record's bins may result in a tombstone with a non-zero void-time.
      • [AER-6361] - (LDAP) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item.
      • [AER-6356] - (XDR) When DC namespace context configuration item bin-policy is not 'all', locally written bins may not get shipped during recovery.

    Known Issues

  • 5.3.0.3
    Release Date: December 17, 2020
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise & Community
      • [AER-6351] - (SCAN) When generating sub-transactions for background scans and queries, the record TTL of the parent transaction is ignored.
    • Enterprise Only
      • [AER-6353] - (TLS) If network TLS context configuration items cert-file or key-file point to environment variables, the server will not start.
      • [AER-6350] - (XDR) If a DC is dynamically removed and another added, handling of authentication configuration items may cause a double-free.

    Known Issues

  • 5.3.0.2
    Release Date: December 10, 2020
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • The Cross-Datacenter Replication (XDR) feature now includes the ability to filter using Expressions.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.

    New Features

    • Enterprise Only
      • [AER-6300] - (XDR) Added expression filtering for XDR.

    Improvements

    • Enterprise & Community
      • [AER-6329] - (BALANCE) Clear irrelevant cluster-related information on non-roster and orphaned nodes.
      • [AER-6296] - (CDT) Added check for duplicate keys in unordered maps.
      • [AER-5852] - (CLUSTERING) tip-clear info command must specify seed as it was configured (DNS name or IP address).
      • [AER-6297] - (CLUSTERING) Added heartbeat context configuration item connect-timeout-ms to enable multi-site clustering with round trip latency more than 100 ms.
      • [AER-6333] - (CLUSTERING) Stop heartbeat on shutdown, to get node kicked out of the cluster in case it was not quiesced and shutdown takes a long time.
      • [AER-6342] - (CLUSTERING) Periodically re-resolve inactive seeds that were configured by DNS name.
      • [AER-6320] - (EXPRESSIONS) Added as_exp_memory_size() operation to use a record's data-in-memory size in expressions.
      • [AER-6344] - (SCAN) Scans now reuse threads from a pool instead of always using fresh system threads.
      • [AER-6345] - (SINDEX) Added storage context configuration item sindex-startup-device-scan to build secondary indexes at startup by scanning devices.
      • [AER-3284] - (STATS) Added object size histograms for storage-engine memory namespaces.
      • [AER-6317] - (UDF) Implemented record.memory_size().
    • Enterprise Only
      • [AER-6349] - (DEPLOYMENT) Added cluster-nodes-limit feature key to restrict cluster size.
      • [AER-6324] - (KVS) Added support for fetching configuration items specified via file path from environment variables.
      • [AER-6337] - (STATS) Included tomb raider device reads and commit-to-device writes in storage benchmark histograms.
      • [AER-6346] - (STATS) Added nodes count in XDR DC stats and log ticker line.
      • [AER-6305] - (XDR) Removed support for 'only-specified' value of DC namespace context configuration item bin-policy.
      • [AER-6319] - (XDR) Added throttling to limit how often SMD saves XDR information to file.
      • [AER-6321] - (XDR) Changed default value of namespace context configuration item xdr-bin-tombstone-ttl to 24 hours.
      • [AER-6328] - (XDR) Added DC context configuration item max-used-service-threads to limit the number of connections to the DC.
      • [AER-6331] - (XDR) When selecting service threads for XDR transactions, ensure all versions of a record ship on the same service thread.

    Known Issues

    Updates

  • 5.2.0.37
    Release Date: October 30, 2021
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support Aerospike Expression filters. Aerospike Expression filters give access to the full data type APIs (List, Map, Bit, HyperLogLog, Geospatial) and expanded metadata based filtering, to increase the power of filters in selecting records.
    • Support for the info command latency has been removed and replaced with a new info command latencies to track all latency histograms.
    • Support for the XDR bin-policy value 'only-specified', which replaced the configuration item ship-only-specified-bins in the 5.0 and 5.1 releases, will be removed in 5.3 and above. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise Only
      • [AER-6486] - (STATS) For strong-consistency namespaces, re-replications that time out while queued internally will be reflected in the latency histogram.
      • [AER-6493] - (UDF) The method aerospike:exists() incorrectly returns true for a tombstone.

    Known Issues

    Enterprise Download
  • 5.2.0.36
    Release Date: September 20, 2021
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support Aerospike Expression filters. Aerospike Expression filters give access to the full data type APIs (List, Map, Bit, HyperLogLog, Geospatial) and expanded metadata based filtering, to increase the power of filters in selecting records.
    • Support for the info command latency has been removed and replaced with a new info command latencies to track all latency histograms.
    • Support for the XDR bin-policy value 'only-specified', which replaced the configuration item ship-only-specified-bins in the 5.0 and 5.1 releases, will be removed in 5.3 and above. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise & Community
      • [AER-6481] - (KVS) When a service thread exits, its epoll queue's event file descriptor leaks.
      • [AER-6482] - (STORAGE) When a device runs completely out of space, defrag becomes ineffective.
    • Enterprise Only

    Known Issues

  • 5.2.0.35
    Release Date: September 15, 2021
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support Aerospike Expression filters. Aerospike Expression filters give access to the full data type APIs (List, Map, Bit, HyperLogLog, Geospatial) and expanded metadata based filtering, to increase the power of filters in selecting records.
    • Support for the info command latency has been removed and replaced with a new info command latencies to track all latency histograms.
    • Support for the XDR bin-policy value 'only-specified', which replaced the configuration item ship-only-specified-bins in the 5.0 and 5.1 releases, will be removed in 5.3 and above. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise & Community
      • [AER-6477] - (UDF) When a UDF write fails due to a stop-writes condition, the record may be erroneously deleted.

    Known Issues

  • 5.2.0.34
    Release Date: September 2, 2021
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support Aerospike Expression filters. Aerospike Expression filters give access to the full data type APIs (List, Map, Bit, HyperLogLog, Geospatial) and expanded metadata based filtering, to increase the power of filters in selecting records.
    • Support for the info command latency has been removed and replaced with a new info command latencies to track all latency histograms.
    • Support for the XDR bin-policy value 'only-specified', which replaced the configuration item ship-only-specified-bins in the 5.0 and 5.1 releases, will be removed in 5.3 and above. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Improvements

    • Enterprise & Community
      • [AER-6475] - (GEO) For data-in-memory namespaces, when trimming GeoJSON particles, reallocate into the appropriate namespace arena.

    Bug Fixes

    • Enterprise & Community
      • [AER-6472] - (SINDEX) If a replica record is expired or truncated, but not yet actually deleted, it is skipped when building a secondary index, but may also be skipped by a replica write.
    • Enterprise Only
      • [AER-6474] - (XDR) DC throughput statistic may be incorrect when there are multiple namespaces.

    Known Issues

  • 5.2.0.33
    Release Date: August 4, 2021
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support Aerospike Expression filters. Aerospike Expression filters give access to the full data type APIs (List, Map, Bit, HyperLogLog, Geospatial) and expanded metadata based filtering, to increase the power of filters in selecting records.
    • Support for the info command latency has been removed and replaced with a new info command latencies to track all latency histograms.
    • Support for the XDR bin-policy value 'only-specified', which replaced the configuration item ship-only-specified-bins in the 5.0 and 5.1 releases, will be removed in 5.3 and above. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise Only
      • [AER-6467] - (SINDEX) With storage compression, replicas and existing records are decompressed into the same buffer, which may result in an incorrect secondary index or a crash.

    Known Issues

  • 5.2.0.32
    Release Date: July 22, 2021
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support Aerospike Expression filters. Aerospike Expression filters give access to the full data type APIs (List, Map, Bit, HyperLogLog, Geospatial) and expanded metadata based filtering, to increase the power of filters in selecting records.
    • Support for the info command latency has been removed and replaced with a new info command latencies to track all latency histograms.
    • Support for the XDR bin-policy value 'only-specified', which replaced the configuration item ship-only-specified-bins in the 5.0 and 5.1 releases, will be removed in 5.3 and above. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise & Community
      • [AER-6457] - (CDT) Improper CDT operation initialization may access out of scope stack memory and crash.

    Known Issues

  • 5.2.0.31
    Release Date: July 19, 2021
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support Aerospike Expression filters. Aerospike Expression filters give access to the full data type APIs (List, Map, Bit, HyperLogLog, Geospatial) and expanded metadata based filtering, to increase the power of filters in selecting records.
    • Support for the info command latency has been removed and replaced with a new info command latencies to track all latency histograms.
    • Support for the XDR bin-policy value 'only-specified', which replaced the configuration item ship-only-specified-bins in the 5.0 and 5.1 releases, will be removed in 5.3 and above. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise Only
      • [AER-6451] - (KVS) Race condition between sprig element counters and changing sprig roots when rebuilding index during warm restart may cause a crash.

    Known Issues

  • 5.2.0.30
    Release Date: June 24, 2021
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support Aerospike Expression filters. Aerospike Expression filters give access to the full data type APIs (List, Map, Bit, HyperLogLog, Geospatial) and expanded metadata based filtering, to increase the power of filters in selecting records.
    • Support for the info command latency has been removed and replaced with a new info command latencies to track all latency histograms.
    • Support for the XDR bin-policy value 'only-specified', which replaced the configuration item ship-only-specified-bins in the 5.0 and 5.1 releases, will be removed in 5.3 and above. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise & Community
      • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps.

    Known Issues

  • 5.2.0.29
    Release Date: May 28, 2021
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support Aerospike Expression filters. Aerospike Expression filters give access to the full data type APIs (List, Map, Bit, HyperLogLog, Geospatial) and expanded metadata based filtering, to increase the power of filters in selecting records.
    • Support for the info command latency has been removed and replaced with a new info command latencies to track all latency histograms.
    • Support for the XDR bin-policy value 'only-specified', which replaced the configuration item ship-only-specified-bins in the 5.0 and 5.1 releases, will be removed in 5.3 and above. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise & Community
      • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes.

    Known Issues

  • 5.2.0.28
    Release Date: May 25, 2021
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support Aerospike Expression filters. Aerospike Expression filters give access to the full data type APIs (List, Map, Bit, HyperLogLog, Geospatial) and expanded metadata based filtering, to increase the power of filters in selecting records.
    • Support for the info command latency has been removed and replaced with a new info command latencies to track all latency histograms.
    • Support for the XDR bin-policy value 'only-specified', which replaced the configuration item ship-only-specified-bins in the 5.0 and 5.1 releases, will be removed in 5.3 and above. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise Only
      • [AER-6427] - (KVS) For data-in-index namespaces, durable deletes will cause an unnecessary assertion on a warm restart.

    Known Issues

  • 5.2.0.27
    Release Date: May 10, 2021
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support Aerospike Expression filters. Aerospike Expression filters give access to the full data type APIs (List, Map, Bit, HyperLogLog, Geospatial) and expanded metadata based filtering, to increase the power of filters in selecting records.
    • Support for the info command latency has been removed and replaced with a new info command latencies to track all latency histograms.
    • Support for the XDR bin-policy value 'only-specified', which replaced the configuration item ship-only-specified-bins in the 5.0 and 5.1 releases, will be removed in 5.3 and above. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise Only
      • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing.

    Known Issues

  • 5.2.0.26
    Release Date: April 6, 2021
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support Aerospike Expression filters. Aerospike Expression filters give access to the full data type APIs (List, Map, Bit, HyperLogLog, Geospatial) and expanded metadata based filtering, to increase the power of filters in selecting records.
    • Support for the info command latency has been removed and replaced with a new info command latencies to track all latency histograms.
    • Support for the XDR bin-policy value 'only-specified', which replaced the configuration item ship-only-specified-bins in the 5.0 and 5.1 releases, will be removed in 5.3 and above. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise & Community
      • [AER-6418] - (UDF) For namespaces with data not in memory, executing a UDF with an expression filter that evaluates false will leak memory.

    Known Issues

  • 5.2.0.25
    Release Date: April 2, 2021
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support Aerospike Expression filters. Aerospike Expression filters give access to the full data type APIs (List, Map, Bit, HyperLogLog, Geospatial) and expanded metadata based filtering, to increase the power of filters in selecting records.
    • Support for the info command latency has been removed and replaced with a new info command latencies to track all latency histograms.
    • Support for the XDR bin-policy value 'only-specified', which replaced the configuration item ship-only-specified-bins in the 5.0 and 5.1 releases, will be removed in 5.3 and above. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise & Community
      • [AER-6414] - (UDF) For namespaces with data not in memory, UDF replications will not adjust the secondary index.

    Known Issues

  • 5.2.0.24
    Release Date: March 29, 2021
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support Aerospike Expression filters. Aerospike Expression filters give access to the full data type APIs (List, Map, Bit, HyperLogLog, Geospatial) and expanded metadata based filtering, to increase the power of filters in selecting records.
    • Support for the info command latency has been removed and replaced with a new info command latencies to track all latency histograms.
    • Support for the XDR bin-policy value 'only-specified', which replaced the configuration item ship-only-specified-bins in the 5.0 and 5.1 releases, will be removed in 5.3 and above. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise & Community
      • [AER-6412] - (QUERY) If a query transaction setup fails in certain ways, improper cleanup may cause a crash.
    • Enterprise Only
      • [AER-6413] - (LDAP) Small memory leak during LDAP login process.
      • [AER-6411] - (XDR) Race when dynamically adding a DC under write load may cause a crash.

    Known Issues

  • 5.2.0.21
    Release Date: March 12, 2021
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support Aerospike Expression filters. Aerospike Expression filters give access to the full data type APIs (List, Map, Bit, HyperLogLog, Geospatial) and expanded metadata based filtering, to increase the power of filters in selecting records.
    • Support for the info command latency has been removed and replaced with a new info command latencies to track all latency histograms.
    • Support for the XDR bin-policy value 'only-specified', which replaced the configuration item ship-only-specified-bins in the 5.0 and 5.1 releases, will be removed in 5.3 and above. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise & Community
      • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical.
      • [AER-6402] - (SINDEX) When iterating through secondary indexes to adjust for changing list bin values, inactive indexes are incorrectly skipped, which may cause a crash.
    • Enterprise Only
      • [AER-6404] - (KVS) For single-bin, data-in-memory namespaces, durable deletes may cause a crash on writing replicas or on subsequent restarts.

    Known Issues

  • 5.2.0.20
    Release Date: February 22, 2021
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support Aerospike Expression filters. Aerospike Expression filters give access to the full data type APIs (List, Map, Bit, HyperLogLog, Geospatial) and expanded metadata based filtering, to increase the power of filters in selecting records.
    • Support for the info command latency has been removed and replaced with a new info command latencies to track all latency histograms.
    • Support for the XDR bin-policy value 'only-specified', which replaced the configuration item ship-only-specified-bins in the 5.0 and 5.1 releases, will be removed in 5.3 and above. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise Only
      • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers.

    Known Issues

  • 5.2.0.19
    Release Date: February 12, 2021
    • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Support Aerospike Expression filters. Aerospike Expression filters give access to the full data type APIs (List, Map, Bit, HyperLogLog, Geospatial) and expanded metadata based filtering, to increase the power of filters in selecting records.
    • Support for the info command latency has been removed and replaced with a new info command latencies to track all latency histograms.
    • Support for the XDR bin-policy value 'only-specified', which replaced the configuration item ship-only-specified-bins in the 5.0 and 5.1 releases, will be removed in 5.3 and above. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
      • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled.
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
    • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
      • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
      • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.