Aerospike Server CE 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

  • 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

  • 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

  • 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

  • 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

  • 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

  • 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

  • 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.
    • 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.2.0.18
    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 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-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.2.0.17
    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 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 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.2.0.16
    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 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-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.2.0.15
    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 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-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.2.0.14
    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 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-6357] - (KVS) Handle exceeding the OS file descriptor limit gracefully, without asserting.

    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.2.0.12
    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 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-6351] - (SCAN) When generating sub-transactions for background scans and queries, the record TTL of the parent transaction is ignored.
    • Enterprise Only
      • [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.2.0.11
    Release Date: December 4, 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 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.

    Bug Fixes

    • Enterprise & Community
      • [AER-6343] - (UDF) In single-bin namespaces, UDFs cannot read or write bin values.
    • Enterprise Only
      • [AER-6341] - (XDR) Source node may fail to discover the entire destination cluster when destination nodes restart.

    Known Issues

  • 5.2.0.10
    Release Date: November 25, 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 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.

    Improvements

    • Enterprise Only
      • [AER-6338] - (TLS) Added support with Centos 7 for certain stronger ciphers.

    Bug Fixes

    • Enterprise & Community
      • [AER-6339] - (KVS) On certain bitwise blob operations (and, or, xor), an out of bounds byte may be accessed and cause a crash.

    Known Issues

  • 5.2.0.9
    Release Date: November 19, 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 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.

    Bug Fixes

    • Enterprise & Community
      • [AER-6330] - (KVS) Invalid HLL element list parameter may cause a crash.
      • [AER-6332] - (KVS) An HLL union operation on an existing bin will overflow the stack.
      • [AER-6334] - (EXPRESSIONS) A map value (as opposed to a map bin) in a compare expression results in an improper error.
      • [AER-6336] - (BATCH) If both filters and bin selection are used in a batch request, proxied sub-transactions are malformed and will fail.

    Known Issues

  • 5.2.0.7
    Release Date: November 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.
    • 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.

    Bug Fixes

    • Enterprise & Community
      • [AER-6326] - (KVS) When Aerospike runs as the init process (e.g. in some container scenarios), signals do not stop Aerospike as intended.
    • Enterprise Only
      • [AER-6327] - (TLS) When refreshing certificates, older chained certificates are not cleared.
      • [AER-6325] - (XDR) DCs with connector true do not properly disconnect when all namespaces are dynamically removed.

    Known Issues

  • 5.2.0.6
    Release Date: October 31, 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 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.

    Improvements

    • Enterprise & Community
      • [AER-6323] - (KVS) With debug-allocations enabled, adjust every logged site address for easier association with source code.

    Bug Fixes

    • Enterprise & Community
    • Enterprise Only
      • [AER-6322] - (XDR) When TLS handshake fails or times out, security authentication request buffer may be double freed, which may cause a crash.

    Known Issues

  • 5.2.0.5
    Release Date: October 21, 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 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.

    Improvements

    • Enterprise & Community
      • [AER-6311] - (SCAN) Do not start more threads for a scan than there are partitions requested.
      • [AER-6312] - (SECONDARY INDEX) When populating secondary indexes at startup, only read records in sets which have indexes.
    • Community Only
      • [AER-6314] - (PACKAGING) Removed Python dependency in Debian Community Edition builds.

    Bug Fixes

    • Enterprise & Community
      • [AER-6316] - (EXPRESSIONS) Expressions may erroneously compare different blob types sent from the client.
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range.
    • Enterprise Only
      • [AER-6313] - (XDR) Small memory leak when XDR client connects to seed node.

    Known Issues

  • 5.2.0.4
    Release Date: October 14, 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 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.

    Improvements

    • Enterprise & Community
      • [AER-6303] - (KVS) With debug-allocations enabled, adjust output site addresses for easier association with source code.

    Bug Fixes

    • Enterprise & Community
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert.
      • [AER-6309] - (CDT) For ordered lists, get_all_by_value_list operation with result type value always returns an empty list.
      • [AER-6308] - (EXPRESSIONS) Miscellaneous issues in new expressions, which are not yet accessible from clients.
    • Enterprise Only
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions.
      • [AER-6302] - (XDR) Namespace context configuration item xdr-tomb-raider-period cannot be set using time units.
      • [AER-6310] - (XDR) When connection to seed node fails, TLS name will be double freed and may cause a crash.

    Known Issues

  • 5.2.0.2
    Release Date: October 1, 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 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.

    New Features

    • Enterprise & Community
      • [AER-6292] - (EXPRESSIONS) Redesigned predicate expressions, expanding their scope and capabilities.
    • Enterprise Only
      • [AER-6272] - (XDR) Added DC namespace context configuration item bin-policy to determine which bins to ship.

    Improvements

    • Enterprise & Community
      • [AER-6291] - (LOGGING) Changed warning to detail level on failure to write to storage, and changed 'out of space' warning to ticker warning.
      • [AER-6283] - (SINDEX) For namespaces with data-in-memory true, adjust secondary indexes when records expire or are evicted.
      • [AER-6285] - (QUERY) Use bin IDs instead of names internally for scans and queries with bin selection, to improve performance.
      • [AER-5487] - (STATS) Added device_data_bytes statistic for sets.
      • [AER-6282] - (STATS) Removed latency info command.
      • [AER-6277] - (UDF) Implemented record.device_size().
      • [AER-6279] - (UDF) Only load records from storage if necessary (speeds up metadata-only read-only UDFs).
      • [AER-6293] - (UDF) Explicitly forbid record UDF policies that were previously ignored.
    • Enterprise Only
      • [AER-6280] - (BALANCE) Added service context configuration item stay-quiesced.
      • [AER-6274] - (MIGRATION) Added namespace context configuration item ignore-migrate-fill-delay.
      • [AER-6281] - (UDF) Validate a UDF transaction's durable-delete flag for UDFs that delete the record.
      • [AER-6273] - (XDR) Added DC namespace context configuration item remote-namespace to ship a local namespace to a different remote namespace.

    Known Issues

    Updates

  • 5.1.0.42
    Release Date: September 20, 2021
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • For the info command latency support has been deprecated and will be removed in the next major release.
      • Please use the new replacement info command latencies to track all latency histograms.
    • 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.

    Known Issues

  • 5.1.0.41
    Release Date: September 15, 2021
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • For the info command latency support has been deprecated and will be removed in the next major release.
      • Please use the new replacement info command latencies to track all latency histograms.
    • 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.1.0.40
    Release Date: September 2, 2021
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • For the info command latency support has been deprecated and will be removed in the next major release.
      • Please use the new replacement info command latencies to track all latency histograms.
    • 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.1.0.39
    Release Date: August 4, 2021
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • For the info command latency support has been deprecated and will be removed in the next major release.
      • Please use the new replacement info command latencies to track all latency histograms.
    • 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.1.0.38
    Release Date: July 19, 2021
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • For the info command latency support has been deprecated and will be removed in the next major release.
      • Please use the new replacement info command latencies to track all latency histograms.
    • 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.1.0.37
    Release Date: June 24, 2021
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • For the info command latency support has been deprecated and will be removed in the next major release.
      • Please use the new replacement info command latencies to track all latency histograms.
    • 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.1.0.36
    Release Date: May 28, 2021
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • For the info command latency support has been deprecated and will be removed in the next major release.
      • Please use the new replacement info command latencies to track all latency histograms.
    • 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.1.0.35
    Release Date: May 25, 2021
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • For the info command latency support has been deprecated and will be removed in the next major release.
      • Please use the new replacement info command latencies to track all latency histograms.
    • 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.1.0.34
    Release Date: May 10, 2021
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • For the info command latency support has been deprecated and will be removed in the next major release.
      • Please use the new replacement info command latencies to track all latency histograms.
    • 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.1.0.33
    Release Date: April 6, 2021
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • For the info command latency support has been deprecated and will be removed in the next major release.
      • Please use the new replacement info command latencies to track all latency histograms.
    • 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.1.0.32
    Release Date: April 2, 2021
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • For the info command latency support has been deprecated and will be removed in the next major release.
      • Please use the new replacement info command latencies to track all latency histograms.
    • 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.1.0.31
    Release Date: March 29, 2021
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • For the info command latency support has been deprecated and will be removed in the next major release.
      • Please use the new replacement info command latencies to track all latency histograms.
    • 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.1.0.28
    Release Date: March 12, 2021
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • For the info command latency support has been deprecated and will be removed in the next major release.
      • Please use the new replacement info command latencies to track all latency histograms.
    • 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.1.0.27
    Release Date: February 22, 2021
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • For the info command latency support has been deprecated and will be removed in the next major release.
      • Please use the new replacement info command latencies to track all latency histograms.
    • 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.1.0.26
    Release Date: January 30, 2021
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • For the info command latency support has been deprecated and will be removed in the next major release.
      • Please use the new replacement info command latencies to track all latency histograms.
    • 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.1.0.25
    Release Date: January 25, 2021
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • For the info command latency support has been deprecated and will be removed in the next major release.
      • Please use the new replacement info command latencies to track all latency histograms.
    • 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-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.1.0.24
    Release Date: January 15, 2021
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • For the info command latency support has been deprecated and will be removed in the next major release.
      • Please use the new replacement info command latencies to track all latency histograms.
    • 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.1.0.23
    Release Date: January 7, 2021
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • For the info command latency support has been deprecated and will be removed in the next major release.
      • Please use the new replacement info command latencies to track all latency histograms.
    • 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.1.0.22
    Release Date: January 4, 2021
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • For the info command latency support has been deprecated and will be removed in the next major release.
      • Please use the new replacement info command latencies to track all latency histograms.
    • 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.

    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.

    Known Issues

  • 5.1.0.20
    Release Date: December 17, 2020
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • For the info command latency support has been deprecated and will be removed in the next major release.
      • Please use the new replacement info command latencies to track all latency histograms.
    • 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-6350] - (XDR) If a DC is dynamically removed and another added, handling of authentication configuration items may cause a double-free.

    Known Issues

  • 5.1.0.19
    Release Date: December 4, 2020
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • For the info command latency support has been deprecated and will be removed in the next major release.
      • Please use the new replacement info command latencies to track all latency histograms.
    • 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.

    Bug Fixes

    • Enterprise & Community
      • [AER-6343] - (UDF) In single-bin namespaces, UDFs cannot read or write bin values.
    • Enterprise Only
      • [AER-6341] - (XDR) Source node may fail to discover the entire destination cluster when destination nodes restart.

    Known Issues

  • 5.1.0.18
    Release Date: November 25, 2020
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • For the info command latency support has been deprecated and will be removed in the next major release.
      • Please use the new replacement info command latencies to track all latency histograms.
    • 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.

    Improvements

    • Enterprise Only
      • [AER-6338] - (TLS) Added support with Centos 7 for certain stronger ciphers.

    Bug Fixes

    • Enterprise & Community
      • [AER-6339] - (KVS) On certain bitwise blob operations (and, or, xor), an out of bounds byte may be accessed and cause a crash.

    Known Issues

  • 5.1.0.17
    Release Date: November 19, 2020
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • For the info command latency support has been deprecated and will be removed in the next major release.
      • Please use the new replacement info command latencies to track all latency histograms.
    • 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.

    Bug Fixes

    • Enterprise & Community
      • [AER-6330] - (KVS) Invalid HLL element list parameter may cause a crash.
      • [AER-6332] - (KVS) An HLL union operation on an existing bin will overflow the stack.
      • [AER-6336] - (BATCH) If both filters and bin selection are used in a batch request, proxied sub-transactions are malformed and will fail.

    Known Issues

  • 5.1.0.15
    Release Date: November 10, 2020
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • For the info command latency support has been deprecated and will be removed in the next major release.
      • Please use the new replacement info command latencies to track all latency histograms.
    • 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.

    Bug Fixes

    • Enterprise & Community
      • [AER-6326] - (KVS) When Aerospike runs as the init process (e.g. in some container scenarios), signals do not stop Aerospike as intended.
    • Enterprise Only
      • [AER-6327] - (TLS) When refreshing certificates, older chained certificates are not cleared.
      • [AER-6325] - (XDR) DCs with connector true do not properly disconnect when all namespaces are dynamically removed.

    Known Issues

  • 5.1.0.14
    Release Date: October 31, 2020
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • For the info command latency support has been deprecated and will be removed in the next major release.
      • Please use the new replacement info command latencies to track all latency histograms.
    • 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.

    Improvements

    • Enterprise & Community
      • [AER-6323] - (KVS) With debug-allocations enabled, adjust every logged site address for easier association with source code.

    Bug Fixes

    • Enterprise Only
      • [AER-6322] - (XDR) When TLS handshake fails or times out, security authentication request buffer may be double freed, which may cause a crash.

    Known Issues

  • 5.1.0.13
    Release Date: October 21, 2020
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • For the info command latency support has been deprecated and will be removed in the next major release.
      • Please use the new replacement info command latencies to track all latency histograms.
    • 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.

    Improvements

    • Enterprise & Community
      • [AER-6311] - (SCAN) Do not start more threads for a scan than there are partitions requested.
      • [AER-6312] - (SECONDARY INDEX) When populating secondary indexes at startup, only read records in sets which have indexes.
    • Community Only
      • [AER-6314] - (PACKAGING) Removed Python dependency in Debian Community Edition builds.

    Bug Fixes

    • Enterprise & Community
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range.
    • Enterprise Only
      • [AER-6313] - (XDR) Small memory leak when XDR client connects to seed node.

    Known Issues

  • 5.1.0.12
    Release Date: October 14, 2020
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • For the info command latency support has been deprecated and will be removed in the next major release.
      • Please use the new replacement info command latencies to track all latency histograms.
    • 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.

    Improvements

    • Enterprise & Community
      • [AER-6303] - (KVS) With debug-allocations enabled, adjust output site addresses for easier association with source code.

    Bug Fixes

    • Enterprise & Community
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert.
      • [AER-6309] - (CDT) For ordered lists, get_all_by_value_list operation with result type value always returns an empty list.
    • Enterprise Only
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions.
      • [AER-6302] - (XDR) Namespace context configuration item xdr-tomb-raider-period cannot be set using time units.
      • [AER-6310] - (XDR) When connection to seed node fails, TLS name will be double freed and may cause a crash.

    Known Issues

  • 5.1.0.10
    Release Date: September 18, 2020
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • For the info command latency support has been deprecated and will be removed in the next major release.
      • Please use the new replacement info command latencies to track all latency histograms.
    • 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.

    Improvements

    • Enterprise & Community
    • Enterprise Only
      • [AER-6288] - (XDR) Keep the last ship time of non-owned partitions relatively current.

    Bug Fixes

    • Enterprise & Community
      • [AER-6289] - (KVS) Concurrently reading and writing a new bin or set name may access a pointer which crosses a cache line boundary, causing a crash.
      • [AER-6290] - (KVS) For namespaces with data not in memory, failure when reading a record from 'flat' format may cause a crash.
    • Enterprise Only
      • [AER-6287] - (KVS) When writing over a tombstone with Time-To-Live (TTL) value -2 (i.e. do not update TTL), the write fails to apply the namespace default-ttl.
    • Community Only
      • [AER-6286] - (TELEMETRY) Telemetry fails to start on Amazon Elastic Compute Cloud (Amazon EC2) on Amazon Linux 2 with Python 3 installed.

    Known Issues

  • 5.1.0.7
    Release Date: August 24, 2020
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • For the info command latency support has been deprecated and will be removed in the next major release.
      • Please use the new replacement info command latencies to track all latency histograms.
    • 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.

    Bug Fixes

    • Enterprise & Community
      • [AER-6278] - (UDF) For namespaces with data not in memory, executing a UDF on a record with more than ~3750 bins will overflow the stack.

    Known Issues

  • 5.1.0.6
    Release Date: August 17, 2020
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • For the info command latency support has been deprecated and will be removed in the next major release.
      • Please use the new replacement info command latencies to track all latency histograms.
    • 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.

    Improvements

    • Enterprise & Community
      • [AER-6238] - (SECURITY) Added service context configuration item disable-udf-execution as a mitigation option for Lua security vulnerabilities.

    Bug Fixes

    • Enterprise & Community
      • [AER-6276] - (STORAGE) At startup, setting storage context configuration item max-write-cache too large will cause an integer overflow when calculating maximum write queue depth.

    Known Issues

  • 5.1.0.5
    Release Date: August 11, 2020
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • For the info command latency support has been deprecated and will be removed in the next major release.
      • Please use the new replacement info command latencies to track all latency histograms.
    • 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.

    Bug Fixes

    • Enterprise Only
      • [AER-6275] - (LDAP) Escaping characters prevents binding to LDAP (escaping should only be done for role queries).

    Known Issues

  • 5.1.0.4
    Release Date: August 5, 2020
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • For the info command latency support has been deprecated and will be removed in the next major release.
      • Please use the new replacement info command latencies to track all latency histograms.
    • 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.

    Bug Fixes

    • Enterprise Only
      • [AER-6267] - (XDR) Setting DC context configuration item auth-user without setting auth-password-file will cause a crash.
      • [AER-6268] - (LDAP) Setting LDAP context configuration item query-user-password-file dynamically may cause a crash.
      • [AER-6269] - (XDR) Setting DC context configuration item auth-password-file while connected to DC may cause a crash.
      • [AER-6270] - (XDR) If dynamically adding a DC, configuring a TLS specification containing a key-file without a required key-file-password will cause a crash.
      • [AER-6271] - (ACL) When fetching various configured items, file descriptors leak and may eventually exhaust the system and cause a crash.

    Known Issues

  • 5.1.0.3
    Release Date: July 31, 2020
    • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
    • Thanks to Matt S. for discovering the issue CVE-2020-13151.
      • To address the UDF security vulnerabilities, we are making a few changes on the server:
        • Lua’s io library has been removed, and the os library only retains time-related functions.
        • We will no longer construct/use a sandbox for each invoked record or stream UDF.
    • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
    • For the info command latency support has been deprecated and will be removed in the next major release.
      • Please use the new replacement info command latencies to track all latency histograms.
    • 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 & Community
      • [AER-6262] - (PACKAGING) Added support for Ubuntu 20, and removed support for Ubuntu 14.
    • Enterprise Only
      • [AER-6247] - (SECRETS) Added support for storing various configuration items in Vault.

    Improvements

    • Enterprise & Community
      • [AER-6229] - (KVS) When retransmitting replica writes, recalculate the destination nodes in case they changed due to a rebalance.
      • [AER-6244] - (KVS) Changed default value of proto-fd-idle-ms to 0 (i.e. never reap idle connections).
      • [AER-6249] - (KVS) Improved handling of record bins.
      • [AER-6264] - (FABRIC) Added fabric context configuration item channel-rw-recv-pools to specify multiple rw channel receive thread pools.
      • [AER-6234] - (STORAGE) Added throttling to prevent defrag from overwhelming the write queue.
      • [AER-6243] - (SECURITY) Addressed Lua security vulnerabilities by denying access to unsafe Lua library functions.
      • [AER-6257] - (UDF) UDFs unwind correctly on failure.
      • [AER-6265] - (GEO) Use stricter bounds checking for latitude and longitude.
      • [AER-4100] - (STATS) Added service context configuration item microsecond-histograms to generate high resolution latency histograms.
      • [AER-6242] - (STATS) Replaced info command latency with new command latencies to track all latency histograms.
    • Enterprise Only
      • [AER-6064] - (LDAP) Escape problematic characters in the user Distinguished Name (DN) before giving it to the LDAP server.
      • [AER-6252] - (LDAP) LDAP context configuration item query-user-password-file is now dynamic and is re-read whenever the password is used.
      • [AER-6253] - (ACL) The write privilege now includes permission to run truncate commands.
      • [AER-6255] - (STORAGE) For storage-engine pmem namespaces, set default service-threads to number of CPUs.
      • [AER-6263] - (STORAGE) Keep storage-engine pmem data blocks read-only except when they are being filled.
      • [AER-6233] - (XDR) Added DC namespace context configuration item write-policy.
      • [AER-6240] - (XDR) If the SMD-persisted last ship time is missing at startup, ship from the current time.
      • [AER-6241] - (XDR) Added retry_no_node stat.
      • [AER-6245] - (XDR) Added DC context configuration item period-ms.
      • [AER-6246] - (XDR) Added DC namespace context configuration item sc-replication-wait-ms.
      • [AER-6266] - (XDR) Added DC namespace context configuration item compression-level.

    Known Issues

    Updates

  • 5.0.0.38
    Release Date: July 19, 2021
    • 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 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.
      • Aerospike Server version 5.0 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.0.0.37
    Release Date: June 24, 2021
    • 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 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.
      • Aerospike Server version 5.0 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.0.0.36
    Release Date: May 28, 2021
    • 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 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.
      • Aerospike Server version 5.0 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.0.0.35
    Release Date: May 25, 2021
    • 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 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.
      • Aerospike Server version 5.0 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.0.0.34
    Release Date: May 10, 2021
    • 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 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.
      • Aerospike Server version 5.0 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.0.0.33
    Release Date: March 29, 2021
    • 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 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.
      • Aerospike Server version 5.0 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.0.0.30
    Release Date: March 12, 2021
    • 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 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.
      • Aerospike Server version 5.0 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.

    Known Issues

  • 5.0.0.29
    Release Date: February 22, 2021
    • 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 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.
      • Aerospike Server version 5.0 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.0.0.28
    Release Date: January 30, 2021
    • 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 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.
      • Aerospike Server version 5.0 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.0.0.27
    Release Date: January 25, 2021
    • 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 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.
      • Aerospike Server version 5.0 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-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.0.0.26
    Release Date: January 15, 2021
    • 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 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.
      • Aerospike Server version 5.0 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.0.0.25
    Release Date: January 4, 2021
    • 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 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.
      • Aerospike Server version 5.0 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.

    Bug Fixes

    • 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.

    Known Issues

  • 5.0.0.23
    Release Date: December 17, 2020
    • 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 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.
      • Aerospike Server version 5.0 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-6350] - (XDR) If a DC is dynamically removed and another added, handling of authentication configuration items may cause a double-free.

    Known Issues

  • 5.0.0.22
    Release Date: December 4, 2020
    • 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 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.
      • Aerospike Server version 5.0 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.

    Bug Fixes

    • Enterprise Only
      • [AER-6341] - (XDR) Source node may fail to discover the entire destination cluster when destination nodes restart.

    Known Issues

  • 5.0.0.21
    Release Date: November 25, 2020
    • 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 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.
      • Aerospike Server version 5.0 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.

    Improvements

    • Enterprise Only
      • [AER-6338] - (TLS) Added support with Centos 7 for certain stronger ciphers.

    Bug Fixes

    • Enterprise & Community
      • [AER-6339] - (KVS) On certain bitwise blob operations (and, or, xor), an out of bounds byte may be accessed and cause a crash.

    Known Issues

  • 5.0.0.20
    Release Date: November 19, 2020
    • 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 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.
      • Aerospike Server version 5.0 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.

    Bug Fixes

    • Enterprise & Community
      • [AER-6330] - (KVS) Invalid HLL element list parameter may cause a crash.
      • [AER-6332] - (KVS) An HLL union operation on an existing bin will overflow the stack.
      • [AER-6336] - (BATCH) If both filters and bin selection are used in a batch request, proxied sub-transactions are malformed and will fail.

    Known Issues

  • 5.0.0.18
    Release Date: November 10, 2020
    • 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 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.
      • Aerospike Server version 5.0 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.

    Bug Fixes

    • Enterprise & Community
      • [AER-6326] - (KVS) When Aerospike runs as the init process (e.g. in some container scenarios), signals do not stop Aerospike as intended.
    • Enterprise Only
      • [AER-6325] - (XDR) DCs with connector true do not properly disconnect when all namespaces are dynamically removed.

    Known Issues

  • 5.0.0.17
    Release Date: October 31, 2020
    • 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 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.
      • Aerospike Server version 5.0 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.

    Improvements

    • Enterprise & Community
      • [AER-6323] - (KVS) With debug-allocations enabled, adjust every logged site address for easier association with source code.

    Bug Fixes

    • Enterprise Only
      • [AER-6322] - (XDR) When TLS handshake fails or times out, security authentication request buffer may be double freed, which may cause a crash.

    Known Issues

  • 5.0.0.16
    Release Date: October 21, 2020
    • 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 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.
      • Aerospike Server version 5.0 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.

    Improvements

    • Enterprise & Community
      • [AER-6311] - (SCAN) Do not start more threads for a scan than there are partitions requested.
      • [AER-6312] - (SECONDARY INDEX) When populating secondary indexes at startup, only read records in sets which have indexes.
    • Community Only
      • [AER-6314] - (PACKAGING) Removed Python dependency in Debian Community Edition builds.

    Bug Fixes

    • Enterprise & Community
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range.
    • Enterprise Only
      • [AER-6313] - (XDR) Small memory leak when XDR client connects to seed node.

    Known Issues

  • 5.0.0.15
    Release Date: October 14, 2020
    • 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 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.
      • Aerospike Server version 5.0 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.

    Improvements

    • Enterprise & Community
      • [AER-6303] - (KVS) With debug-allocations enabled, adjust output site addresses for easier association with source code.

    Bug Fixes

    • Enterprise & Community
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert.
      • [AER-6309] - (CDT) For ordered lists, get_all_by_value_list operation with result type value always returns an empty list.
    • Enterprise Only
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions.
      • [AER-6302] - (XDR) Namespace context configuration item xdr-tomb-raider-period cannot be set using time units.
      • [AER-6310] - (XDR) When connection to seed node fails, TLS name will be double freed and may cause a crash.

    Known Issues

  • 5.0.0.13
    Release Date: September 18, 2020
    • 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 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.
      • Aerospike Server version 5.0 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.

    Improvements

    • Enterprise & Community
    • Enterprise Only
      • [AER-6288] - (XDR) Keep the last ship time of non-owned partitions relatively current.

    Bug Fixes

    • Enterprise & Community
      • [AER-6289] - (KVS) Concurrently reading and writing a new bin or set name may access a pointer which crosses a cache line boundary, causing a crash.
    • Enterprise Only
      • [AER-6287] - (KVS) When writing over a tombstone with Time-To-Live (TTL) value -2 (i.e. do not update TTL), the write fails to apply the namespace default-ttl.

    Known Issues

  • 5.0.0.11
    Release Date: August 5, 2020
    • 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 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.
      • Aerospike Server version 5.0 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.

    Bug Fixes

    • Enterprise Only
      • [AER-6269] - (XDR) Setting DC context configuration item auth-password-file while connected to DC may cause a crash.
      • [AER-6270] - (XDR) If dynamically adding a DC, configuring a TLS spec containing a key-file without a required key-file-password will cause a crash.

    Known Issues

  • 5.0.0.10
    Release Date: July 14, 2020
    • 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 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.
      • Aerospike Server version 5.0 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.

    Bug Fixes

    • Enterprise Only
      • [AER-6258] - (XDR) For low or intermittent load, a race may cause unnecessary timeouts.
      • [AER-6259] - (XDR) When visibility of remote DC is lost, race between shipping and reconnection may cause an assertion.

    Known Issues

  • 5.0.0.9
    Release Date: July 7, 2020
    • 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 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.
      • Aerospike Server version 5.0 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.

    Bug Fixes

    • Enterprise & Community
      • [AER-6251] - (UDF) When a record UDF does not pass a predicate expression metadata filter, the server will deadlock.
    • Enterprise Only
      • [AER-6250] - (UDF) Race between a background UDF scan/query internal transaction and a durable delete may cause a deadlock.

    Known Issues

  • 5.0.0.8
    Release Date: June 25, 2020
    • 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 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.
      • Aerospike Server version 5.0 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.
    • XDR, using ACL, in server versions between 4.1.0.1 and 4.3.0.6 cannot ship to this version. The simplest workaround is to avoid using those versions.

    Bug Fixes

    • Enterprise Only
      • [AER-6248] - (XDR) Wrong node may be selected when connecting, resulting in bad load balance (connectors) or proxies (Aerospike destinations).

    Known Issues

  • 5.0.0.7
    Release Date: June 18, 2020
    • 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 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.
      • Aerospike Server version 5.0 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.
    • XDR, using ACL, in server versions between 4.1.0.1 and 4.3.0.6 cannot ship to this version. The simplest workaround is to avoid using those versions.

    Improvements

    • Enterprise & Community
      • [AER-6238] - (SECURITY) Added service context configuration item disable-udf-execution as a mitigation option for Lua security vulnerabilities.

    Bug Fixes

    • Enterprise & Community
      • [AER-6239] - (INFO) Invalid log-set command parameters may cause a crash.
    • Enterprise Only
      • [AER-6235] - (XDR) If DC context configuration item tls-name is not set, a TLS name in DC context configuration item node-address-port will cause a crash.
      • [AER-6236] - (XDR) DC throughput stat is always zero when retrieved via info command.
      • [AER-6237] - (XDR) Rare race between replication and migration may cause XDR submission at replica to fail.

    Known Issues

  • 5.0.0.4
    Release Date: May 21, 2020
    • 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 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.
      • Aerospike Server version 5.0 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.
    • XDR, using ACL, in server versions between 4.1.0.1 and 4.3.0.6 cannot ship to this version. The simplest workaround is to avoid using those versions.

    Improvements

    • Enterprise Only
      • [AER-6231] - (XDR) Avoid sending redundant XDR information during replication.

    Bug Fixes

    • Enterprise & Community
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated.

    Known Issues

  • 5.0.0.3
    Release Date: May 14, 2020
    • If using XDR, it is strongly advised to upgrade to version 5.0.0.4 or above. Refer to AER-6231 and the 5.0.0.4 release notes for details.
    • The Cross-Datacenter Replication (XDR) feature has been redesigned for improvements in speed and simplicity. Refer to:
    • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 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.
      • Aerospike Server version 5.0 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).
    • The maximum cluster size is now increased to 256 nodes. However, the actual limit when using multicast heartbeat mode will depend on the Maximum Transmission Unit (MTU).
      • There is a 132 node limit with MTU of 1500. A 256 node limit can be achieved with an MTU of 9000.
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • XDR, using ACL, in server versions between 4.1.0.1 and 4.3.0.6 cannot ship to this version. The simplest workaround is to avoid using those versions.
    • Community Edition clusters now limit the maximum amount of data to 5TB of unique data. Refer to:

    New Features

    • Community Only
      • [AER-6226] - (DEPLOYMENT) Limited Community Edition clusters to 5TB of unique data.

    Improvements

    • Enterprise & Community
      • [AER-6202] - (KVS) Increased maximum supported configuration file line length to 1024 characters.
      • [AER-6217] - (KVS) Increased bin_names_quota to 65535.
      • [AER-6218] - (KVS) Service context configuration item proto-fd-max may now be dynamically set as high as the system's current process file descriptor limit.
      • [AER-6219] - (KVS) Removed support for very old clients that sent key without digest.
      • [AER-6222] - (KVS) Do not start the server if the configuration file contains obsolete items.
      • [AER-6221] - (LOGGING) Streamlined cold start storage load ticker logging.
    • Enterprise Only
      • [AER-6225] - (DEPLOYMENT) Increased maximum cluster size to 256.
      • [AER-6200] - (XDR) Redesigned XDR system, including significant changes to configuration and statistics.

    Known Issues

    Updates

  • 4.9.0.37
    Release Date: April 4, 2022
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Aerospike Server will not start If the value of default-ttl is non-zero and nsup-period is zero (the default).
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • Support added for HyperLogLog (HLL) probabilistic data types.
      • Clusters connected using Cross Datacenter Replication (XDR) all clusters must have been upgraded to Aerospike Server 4.9 prior to using the HyperLogLog (HLL) data type.
      • Before downgrading from Aerospike Server 4.9 all HyperLogLog (HLL) bins must be removed by the application.
      • During the unlikely case of a downgrade the drives would need to be wiped. It is advised to review your Aerospike Server 4.9 environment prior to implementing the usage of HyperLogLog (HLL) data type bins.
    • When upgrading to Aerospike Server v4.9.0.7 or newer to ensure migrations complete refer to the Special Upgrades document section Avoiding partition ownership disagreement that prevents migrations from completing.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise Only
      • [AER-6521] - (STORAGE) For storage-engine pmem namespaces, dynamically setting defrag-lwm-pct will set one-eighth the intended threshold.
      • [AER-6522[ - (XDR) Dynamically removing a DC may cause a crash.

    Known Issues

  • 4.9.0.36
    Release Date: October 25, 2021
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Aerospike Server will not start If the value of default-ttl is non-zero and nsup-period is zero (the default).
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • Support added for HyperLogLog (HLL) probabilistic data types.
      • Clusters connected using Cross Datacenter Replication (XDR) all clusters must have been upgraded to Aerospike Server 4.9 prior to using the HyperLogLog (HLL) data type.
      • Before downgrading from Aerospike Server 4.9 all HyperLogLog (HLL) bins must be removed by the application.
      • During the unlikely case of a downgrade the drives would need to be wiped. It is advised to review your Aerospike Server 4.9 environment prior to implementing the usage of HyperLogLog (HLL) data type bins.
    • When upgrading to Aerospike Server v4.9.0.7 or newer to ensure migrations complete refer to the Special Upgrades document section Avoiding partition ownership disagreement that prevents migrations from completing.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise Only
      • [AER-6494] - (XDR) For a pipeline connection, a timeout occurring between a retry signal and the actual retry may cause a crash.

    Known Issues

  • 4.9.0.35
    Release Date: August 4, 2021
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Aerospike Server will not start If the value of default-ttl is non-zero and nsup-period is zero (the default).
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • Support added for HyperLogLog (HLL) probabilistic data types.
      • Clusters connected using Cross Datacenter Replication (XDR) all clusters must have been upgraded to Aerospike Server 4.9 prior to using the HyperLogLog (HLL) data type.
      • Before downgrading from Aerospike Server 4.9 all HyperLogLog (HLL) bins must be removed by the application.
      • During the unlikely case of a downgrade the drives would need to be wiped. It is advised to review your Aerospike Server 4.9 environment prior to implementing the usage of HyperLogLog (HLL) data type bins.
    • When upgrading to Aerospike Server v4.9.0.7 or newer to ensure migrations complete refer to the Special Upgrades document section Avoiding partition ownership disagreement that prevents migrations from completing.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • 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

  • 4.9.0.34
    Release Date: July 19, 2021
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Aerospike Server will not start If the value of default-ttl is non-zero and nsup-period is zero (the default).
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • Support added for HyperLogLog (HLL) probabilistic data types.
      • Clusters connected using Cross Datacenter Replication (XDR) all clusters must have been upgraded to Aerospike Server 4.9 prior to using the HyperLogLog (HLL) data type.
      • Before downgrading from Aerospike Server 4.9 all HyperLogLog (HLL) bins must be removed by the application.
      • During the unlikely case of a downgrade the drives would need to be wiped. It is advised to review your Aerospike Server 4.9 environment prior to implementing the usage of HyperLogLog (HLL) data type bins.
    • When upgrading to Aerospike Server v4.9.0.7 or newer to ensure migrations complete refer to the Special Upgrades document section Avoiding partition ownership disagreement that prevents migrations from completing.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • 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

  • 4.9.0.33
    Release Date: May 28, 2021
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Aerospike Server will not start If the value of default-ttl is non-zero and nsup-period is zero (the default).
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • Support added for HyperLogLog (HLL) probabilistic data types.
      • Clusters connected using Cross Datacenter Replication (XDR) all clusters must have been upgraded to Aerospike Server 4.9 prior to using the HyperLogLog (HLL) data type.
      • Before downgrading from Aerospike Server 4.9 all HyperLogLog (HLL) bins must be removed by the application.
      • During the unlikely case of a downgrade the drives would need to be wiped. It is advised to review your Aerospike Server 4.9 environment prior to implementing the usage of HyperLogLog (HLL) data type bins.
    • When upgrading to Aerospike Server v4.9.0.7 or newer to ensure migrations complete refer to the Special Upgrades document section Avoiding partition ownership disagreement that prevents migrations from completing.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • 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

  • 4.9.0.32
    Release Date: May 25, 2021
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Aerospike Server will not start If the value of default-ttl is non-zero and nsup-period is zero (the default).
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • Support added for HyperLogLog (HLL) probabilistic data types.
      • Clusters connected using Cross Datacenter Replication (XDR) all clusters must have been upgraded to Aerospike Server 4.9 prior to using the HyperLogLog (HLL) data type.
      • Before downgrading from Aerospike Server 4.9 all HyperLogLog (HLL) bins must be removed by the application.
      • During the unlikely case of a downgrade the drives would need to be wiped. It is advised to review your Aerospike Server 4.9 environment prior to implementing the usage of HyperLogLog (HLL) data type bins.
    • When upgrading to Aerospike Server v4.9.0.7 or newer to ensure migrations complete refer to the Special Upgrades document section Avoiding partition ownership disagreement that prevents migrations from completing.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • 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

  • 4.9.0.31
    Release Date: May 10, 2021
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Aerospike Server will not start If the value of default-ttl is non-zero and nsup-period is zero (the default).
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • Support added for HyperLogLog (HLL) probabilistic data types.
      • Clusters connected using Cross Datacenter Replication (XDR) all clusters must have been upgraded to Aerospike Server 4.9 prior to using the HyperLogLog (HLL) data type.
      • Before downgrading from Aerospike Server 4.9 all HyperLogLog (HLL) bins must be removed by the application.
      • During the unlikely case of a downgrade the drives would need to be wiped. It is advised to review your Aerospike Server 4.9 environment prior to implementing the usage of HyperLogLog (HLL) data type bins.
    • When upgrading to Aerospike Server v4.9.0.7 or newer to ensure migrations complete refer to the Special Upgrades document section Avoiding partition ownership disagreement that prevents migrations from completing.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • 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

  • 4.9.0.30
    Release Date: March 29, 2021
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Aerospike Server will not start If the value of default-ttl is non-zero and nsup-period is zero (the default).
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • Support added for HyperLogLog (HLL) probabilistic data types.
      • Clusters connected using Cross Datacenter Replication (XDR) all clusters must have been upgraded to Aerospike Server 4.9 prior to using the HyperLogLog (HLL) data type.
      • Before downgrading from Aerospike Server 4.9 all HyperLogLog (HLL) bins must be removed by the application.
      • During the unlikely case of a downgrade the drives would need to be wiped. It is advised to review your Aerospike Server 4.9 environment prior to implementing the usage of HyperLogLog (HLL) data type bins.
    • When upgrading to Aerospike Server v4.9.0.7 or newer to ensure migrations complete refer to the Special Upgrades document section Avoiding partition ownership disagreement that prevents migrations from completing.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • 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.

    Known Issues

  • 4.9.0.28
    Release Date: March 12, 2021
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Aerospike Server will not start If the value of default-ttl is non-zero and nsup-period is zero (the default).
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • Support added for HyperLogLog (HLL) probabilistic data types.
      • Clusters connected using Cross Datacenter Replication (XDR) all clusters must have been upgraded to Aerospike Server 4.9 prior to using the HyperLogLog (HLL) data type.
      • Before downgrading from Aerospike Server 4.9 all HyperLogLog (HLL) bins must be removed by the application.
      • During the unlikely case of a downgrade the drives would need to be wiped. It is advised to review your Aerospike Server 4.9 environment prior to implementing the usage of HyperLogLog (HLL) data type bins.
    • When upgrading to Aerospike Server v4.9.0.7 or newer to ensure migrations complete refer to the Special Upgrades document section Avoiding partition ownership disagreement that prevents migrations from completing.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • 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.

    Known Issues

  • 4.9.0.27
    Release Date: February 22, 2021
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Aerospike Server will not start If the value of default-ttl is non-zero and nsup-period is zero (the default).
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • Support added for HyperLogLog (HLL) probabilistic data types.
      • Clusters connected using Cross Datacenter Replication (XDR) all clusters must have been upgraded to Aerospike Server 4.9 prior to using the HyperLogLog (HLL) data type.
      • Before downgrading from Aerospike Server 4.9 all HyperLogLog (HLL) bins must be removed by the application.
      • During the unlikely case of a downgrade the drives would need to be wiped. It is advised to review your Aerospike Server 4.9 environment prior to implementing the usage of HyperLogLog (HLL) data type bins.
    • When upgrading to Aerospike Server v4.9.0.7 or newer to ensure migrations complete refer to the Special Upgrades document section Avoiding partition ownership disagreement that prevents migrations from completing.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • 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

  • 4.9.0.26
    Release Date: February 12, 2021
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Aerospike Server will not start If the value of default-ttl is non-zero and nsup-period is zero (the default).
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • Support added for HyperLogLog (HLL) probabilistic data types.
      • Clusters connected using Cross Datacenter Replication (XDR) all clusters must have been upgraded to Aerospike Server 4.9 prior to using the HyperLogLog (HLL) data type.
      • Before downgrading from Aerospike Server 4.9 all HyperLogLog (HLL) bins must be removed by the application.
      • During the unlikely case of a downgrade the drives would need to be wiped. It is advised to review your Aerospike Server 4.9 environment prior to implementing the usage of HyperLogLog (HLL) data type bins.
    • When upgrading to Aerospike Server v4.9.0.7 or newer to ensure migrations complete refer to the Special Upgrades document section Avoiding partition ownership disagreement that prevents migrations from completing.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    Bug Fixes

    • Enterprise Only
      • [AER-6391] - (XDR) When restarting storage-backed data-in-memory namespaces after XDR writes have been accepted on the node, records will be improperly deleted.

    Known Issues

  • 4.9.0.25
    Release Date: January 30, 2021
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Aerospike Server will not start If the value of default-ttl is non-zero and nsup-period is zero (the default).
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • Support added for HyperLogLog (HLL) probabilistic data types.
      • Clusters connected using Cross Datacenter Replication (XDR) all clusters must have been upgraded to Aerospike Server 4.9 prior to using the HyperLogLog (HLL) data type.
      • Before downgrading from Aerospike Server 4.9 all HyperLogLog (HLL) bins must be removed by the application.
      • During the unlikely case of a downgrade the drives would need to be wiped. It is advised to review your Aerospike Server 4.9 environment prior to implementing the usage of HyperLogLog (HLL) data type bins.
    • When upgrading to Aerospike Server v4.9.0.7 or newer to ensure migrations complete refer to the Special Upgrades document section Avoiding partition ownership disagreement that prevents migrations from completing.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • 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.

    Known Issues

  • 4.9.0.24
    Release Date: January 25, 2021
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Aerospike Server will not start If the value of default-ttl is non-zero and nsup-period is zero (the default).
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • Support added for HyperLogLog (HLL) probabilistic data types.
      • Clusters connected using Cross Datacenter Replication (XDR) all clusters must have been upgraded to Aerospike Server 4.9 prior to using the HyperLogLog (HLL) data type.
      • Before downgrading from Aerospike Server 4.9 all HyperLogLog (HLL) bins must be removed by the application.
      • During the unlikely case of a downgrade the drives would need to be wiped. It is advised to review your Aerospike Server 4.9 environment prior to implementing the usage of HyperLogLog (HLL) data type bins.
    • When upgrading to Aerospike Server v4.9.0.7 or newer to ensure migrations complete refer to the Special Upgrades document section Avoiding partition ownership disagreement that prevents migrations from completing.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    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

  • 4.9.0.23
    Release Date: January 4, 2021
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Aerospike Server will not start If the value of default-ttl is non-zero and nsup-period is zero (the default).
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • Support added for HyperLogLog (HLL) probabilistic data types.
      • Clusters connected using Cross Datacenter Replication (XDR) all clusters must have been upgraded to Aerospike Server 4.9 prior to using the HyperLogLog (HLL) data type.
      • Before downgrading from Aerospike Server 4.9 all HyperLogLog (HLL) bins must be removed by the application.
      • During the unlikely case of a downgrade the drives would need to be wiped. It is advised to review your Aerospike Server 4.9 environment prior to implementing the usage of HyperLogLog (HLL) data type bins.
    • When upgrading to Aerospike Server v4.9.0.7 or newer to ensure migrations complete refer to the Special Upgrades document section Avoiding partition ownership disagreement that prevents migrations from completing.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • 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.

    Bug Fixes

    • 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.

    Known Issues

  • 4.9.0.21
    Release Date: December 17, 2020
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Aerospike Server will not start If the value of default-ttl is non-zero and nsup-period is zero (the default).
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • Support added for HyperLogLog (HLL) probabilistic data types.
      • Clusters connected using Cross Datacenter Replication (XDR) all clusters must have been upgraded to Aerospike Server 4.9 prior to using the HyperLogLog (HLL) data type.
      • Before downgrading from Aerospike Server 4.9 all HyperLogLog (HLL) bins must be removed by the application.
      • During the unlikely case of a downgrade the drives would need to be wiped. It is advised to review your Aerospike Server 4.9 environment prior to implementing the usage of HyperLogLog (HLL) data type bins.
    • When upgrading to Aerospike Server v4.9.0.7 or newer to ensure migrations complete refer to the Special Upgrades document section Avoiding partition ownership disagreement that prevents migrations from completing.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • 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.

    Known Issues

  • 4.9.0.20
    Release Date: November 25, 2020
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Aerospike Server will not start If the value of default-ttl is non-zero and nsup-period is zero (the default).
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • Support added for HyperLogLog (HLL) probabilistic data types.
      • Clusters connected using Cross Datacenter Replication (XDR) all clusters must have been upgraded to Aerospike Server 4.9 prior to using the HyperLogLog (HLL) data type.
      • Before downgrading from Aerospike Server 4.9 all HyperLogLog (HLL) bins must be removed by the application.
      • During the unlikely case of a downgrade the drives would need to be wiped. It is advised to review your Aerospike Server 4.9 environment prior to implementing the usage of HyperLogLog (HLL) data type bins.
    • When upgrading to Aerospike Server v4.9.0.7 or newer to ensure migrations complete refer to the Special Upgrades document section Avoiding partition ownership disagreement that prevents migrations from completing.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Improvements

    • Enterprise Only
      • [AER-6338] - (TLS) Added support with Centos 7 for certain stronger ciphers.

    Bug Fixes

    • Enterprise & Community
      • [AER-6339] - (KVS) On certain bitwise blob operations (and, or, xor), an out of bounds byte may be accessed and cause a crash.

    Known Issues

  • 4.9.0.19
    Release Date: November 19, 2020
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Aerospike Server will not start If the value of default-ttl is non-zero and nsup-period is zero (the default).
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • Support added for HyperLogLog (HLL) probabilistic data types.
      • Clusters connected using Cross Datacenter Replication (XDR) all clusters must have been upgraded to Aerospike Server 4.9 prior to using the HyperLogLog (HLL) data type.
      • Before downgrading from Aerospike Server 4.9 all HyperLogLog (HLL) bins must be removed by the application.
      • During the unlikely case of a downgrade the drives would need to be wiped. It is advised to review your Aerospike Server 4.9 environment prior to implementing the usage of HyperLogLog (HLL) data type bins.
    • When upgrading to Aerospike Server v4.9.0.7 or newer to ensure migrations complete refer to the Special Upgrades document section Avoiding partition ownership disagreement that prevents migrations from completing.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-6330] - (KVS) Invalid HLL element list parameter may cause a crash.
      • [AER-6332] - (KVS) An HLL union operation on an existing bin will overflow the stack.
      • [AER-6336] - (BATCH) If both filters and bin selection are used in a batch request, proxied sub-transactions are malformed and will fail.
    • Enterprise Only
      • [AER-6335] - (XDR) Replica writes which are XDR writes are written to the digest log and may be shipped even if forwarding is off.

    Known Issues

  • 4.9.0.17
    Release Date: November 10, 2020
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Aerospike Server will not start If the value of default-ttl is non-zero and nsup-period is zero (the default).
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • Support added for HyperLogLog (HLL) probabilistic data types.
      • Clusters connected using Cross Datacenter Replication (XDR) all clusters must have been upgraded to Aerospike Server 4.9 prior to using the HyperLogLog (HLL) data type.
      • Before downgrading from Aerospike Server 4.9 all HyperLogLog (HLL) bins must be removed by the application.
      • During the unlikely case of a downgrade the drives would need to be wiped. It is advised to review your Aerospike Server 4.9 environment prior to implementing the usage of HyperLogLog (HLL) data type bins.
    • When upgrading to Aerospike Server v4.9.0.7 or newer to ensure migrations complete refer to the Special Upgrades document section Avoiding partition ownership disagreement that prevents migrations from completing.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-6326] - (KVS) When Aerospike runs as the init process (e.g. in some container scenarios), signals do not stop Aerospike as intended.

    Known Issues

  • 4.9.0.16
    Release Date: October 31, 2020
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Aerospike Server will not start If the value of default-ttl is non-zero and nsup-period is zero (the default).
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • Support added for HyperLogLog (HLL) probabilistic data types.
      • Clusters connected using Cross Datacenter Replication (XDR) all clusters must have been upgraded to Aerospike Server 4.9 prior to using the HyperLogLog (HLL) data type.
      • Before downgrading from Aerospike Server 4.9 all HyperLogLog (HLL) bins must be removed by the application.
      • During the unlikely case of a downgrade the drives would need to be wiped. It is advised to review your Aerospike Server 4.9 environment prior to implementing the usage of HyperLogLog (HLL) data type bins.
    • When upgrading to Aerospike Server v4.9.0.7 or newer to ensure migrations complete refer to the Special Upgrades document section Avoiding partition ownership disagreement that prevents migrations from completing.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Improvements

    • Enterprise & Community
      • [AER-6323] - (KVS) With debug-allocations enabled, adjust every logged site address for easier association with source code.

    Known Issues

  • 4.9.0.15
    Release Date: October 21, 2020
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Aerospike Server will not start If the value of default-ttl is non-zero and nsup-period is zero (the default).
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • Support added for HyperLogLog (HLL) probabilistic data types.
      • Clusters connected using Cross Datacenter Replication (XDR) all clusters must have been upgraded to Aerospike Server 4.9 prior to using the HyperLogLog (HLL) data type.
      • Before downgrading from Aerospike Server 4.9 all HyperLogLog (HLL) bins must be removed by the application.
      • During the unlikely case of a downgrade the drives would need to be wiped. It is advised to review your Aerospike Server 4.9 environment prior to implementing the usage of HyperLogLog (HLL) data type bins.
    • When upgrading to Aerospike Server v4.9.0.7 or newer to ensure migrations complete refer to the Special Upgrades document section Avoiding partition ownership disagreement that prevents migrations from completing.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Improvements

    • Enterprise & Community
      • [AER-6311] - (SCAN) Do not start more threads for a scan than there are partitions requested.
      • [AER-6312] - (SECONDARY INDEX) When populating secondary indexes at startup, only read records in sets which have indexes.
    • Community Only
      • [AER-6314] - (PACKAGING) Removed Python dependency in Debian Community Edition builds.

    Bug Fixes

    • Enterprise & Community
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range.

    Known Issues

  • 4.9.0.14
    Release Date: October 14, 2020
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Aerospike Server will not start If the value of default-ttl is non-zero and nsup-period is zero (the default).
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • Support added for HyperLogLog (HLL) probabilistic data types.
      • Clusters connected using Cross Datacenter Replication (XDR) all clusters must have been upgraded to Aerospike Server 4.9 prior to using the HyperLogLog (HLL) data type.
      • Before downgrading from Aerospike Server 4.9 all HyperLogLog (HLL) bins must be removed by the application.
      • During the unlikely case of a downgrade the drives would need to be wiped. It is advised to review your Aerospike Server 4.9 environment prior to implementing the usage of HyperLogLog (HLL) data type bins.
    • When upgrading to Aerospike Server v4.9.0.7 or newer to ensure migrations complete refer to the Special Upgrades document section Avoiding partition ownership disagreement that prevents migrations from completing.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Improvements

    • Enterprise & Community
      • [AER-6303] - (KVS) With debug-allocations enabled, adjust output site addresses for easier association with source code.

    Bug Fixes

    • Enterprise & Community
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert.
      • [AER-6309] - (CDT) For ordered lists, get_all_by_value_list operation with result type value always returns an empty list.
    • Enterprise Only
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions.

    Known Issues

  • 4.9.0.12
    Release Date: September 18, 2020
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Aerospike Server will not start If the value of default-ttl is non-zero and nsup-period is zero (the default).
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • Support added for HyperLogLog (HLL) probabilistic data types.
      • Clusters connected using Cross Datacenter Replication (XDR) all clusters must have been upgraded to Aerospike Server 4.9 prior to using the HyperLogLog (HLL) data type.
      • Before downgrading from Aerospike Server 4.9 all HyperLogLog (HLL) bins must be removed by the application.
      • During the unlikely case of a downgrade the drives would need to be wiped. It is advised to review your Aerospike Server 4.9 environment prior to implementing the usage of HyperLogLog (HLL) data type bins.
    • When upgrading to Aerospike Server v4.9.0.7 or newer to ensure migrations complete refer to the Special Upgrades document section Avoiding partition ownership disagreement that prevents migrations from completing.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Improvements

    Bug Fixes

    • Enterprise & Community
      • [AER-6289] - (KVS) Concurrently reading and writing a new bin or set name may access a pointer which crosses a cache line boundary, causing a crash.
    • Enterprise Only
      • [AER-6287] - (KVS) When writing over a tombstone with Time-To-Live (TTL) value -2 (i.e. do not update TTL), the write fails to apply the namespace default-ttl.

    Known Issues

  • 4.9.0.11
    Release Date: July 7, 2020
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Aerospike Server will not start If the value of default-ttl is non-zero and nsup-period is zero (the default).
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • Support added for HyperLogLog (HLL) probabilistic data types.
      • Clusters connected using Cross Datacenter Replication (XDR) all clusters must have been upgraded to Aerospike Server 4.9 prior to using the HyperLogLog (HLL) data type.
      • Before downgrading from Aerospike Server 4.9 all HyperLogLog (HLL) bins must be removed by the application.
      • During the unlikely case of a downgrade the drives would need to be wiped. It is advised to review your Aerospike Server 4.9 environment prior to implementing the usage of HyperLogLog (HLL) data type bins.
    • When upgrading to Aerospike Server v4.9.0.7 or newer to ensure migrations complete refer to the Special Upgrades document section Avoiding partition ownership disagreement that prevents migrations from completing.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-6251] - (UDF) When a record UDF does not pass a predicate expression metadata filter, the server will deadlock.
    • Enterprise Only
      • [AER-6250] - (UDF) Race between a background UDF scan/query internal transaction and a durable delete may cause a deadlock.

    Known Issues

  • 4.9.0.10
    Release Date: June 18, 2020
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Aerospike Server will not start If the value of default-ttl is non-zero and nsup-period is zero (the default).
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • Support added for HyperLogLog (HLL) probabilistic data types.
      • Clusters connected using Cross Datacenter Replication (XDR) all clusters must have been upgraded to Aerospike Server 4.9 prior to using the HyperLogLog (HLL) data type.
      • Before downgrading from Aerospike Server 4.9 all HyperLogLog (HLL) bins must be removed by the application.
      • During the unlikely case of a downgrade the drives would need to be wiped. It is advised to review your Aerospike Server 4.9 environment prior to implementing the usage of HyperLogLog (HLL) data type bins.
    • XDR, using ACL, in server versions between 4.1.0.1 and 4.3.0.6 cannot ship to this version. The simplest workaround is to avoid using those versions.
    • When upgrading to Aerospike Server v4.9.0.7 or newer to ensure migrations complete refer to the Special Upgrades document section Avoiding partition ownership disagreement that prevents migrations from completing.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Improvements

    • Enterprise & Community
      • [AER-6238] - (SECURITY) Added service context configuration item disable-udf-execution as a mitigation option for Lua security vulnerabilities.

    Bug Fixes

    • Enterprise & Community
      • [AER-6239] - (INFO) Invalid log-set command parameters may cause a crash.

    Known Issues

  • 4.9.0.8
    Release Date: May 22, 2020
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Aerospike Server will not start If the value of default-ttl is non-zero and nsup-period is zero (the default).
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • Support added for HyperLogLog (HLL) probabilistic data types.
      • Clusters connected using Cross Datacenter Replication (XDR) all clusters must have been upgraded to Aerospike Server 4.9 prior to using the HyperLogLog (HLL) data type.
      • Before downgrading from Aerospike Server 4.9 all HyperLogLog (HLL) bins must be removed by the application.
      • During the unlikely case of a downgrade the drives would need to be wiped. It is advised to review your Aerospike Server 4.9 environment prior to implementing the usage of HyperLogLog (HLL) data type bins.
    • XDR, using ACL, in server versions between 4.1.0.1 and 4.3.0.6 cannot ship to this version. The simplest workaround is to avoid using those versions.
    • When upgrading to Aerospike Server v4.9.0.7 or newer to ensure migrations complete refer to the Special Upgrades document section Avoiding partition ownership disagreement that prevents migrations from completing.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated.

    Known Issues

  • 4.9.0.7
    Release Date: May 14, 2020
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Aerospike Server will not start If the value of default-ttl is non-zero and nsup-period is zero (the default).
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • Support added for HyperLogLog (HLL) probabilistic data types.
      • Clusters connected using Cross Datacenter Replication (XDR) all clusters must have been upgraded to Aerospike Server 4.9 prior to using the HyperLogLog (HLL) data type.
      • Before downgrading from Aerospike Server 4.9 all HyperLogLog (HLL) bins must be removed by the application.
      • During the unlikely case of a downgrade the drives would need to be wiped. It is advised to review your Aerospike Server 4.9 environment prior to implementing the usage of HyperLogLog (HLL) data type bins.
    • XDR, using ACL, in server versions between 4.1.0.1 and 4.3.0.6 cannot ship to this version. The simplest workaround is to avoid using those versions.
    • When upgrading to Aerospike Server v4.9.0.7 or newer to ensure migrations complete refer to the Special Upgrades document section Avoiding partition ownership disagreement that prevents migrations from completing.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise Only
      • [AER-6227] - (BALANCE) When applying uniform balance, a misused stack variable may cause an inaccurate balance and prevent migrations from completing.

    Known Issues

  • 4.9.0.6
    Release Date: April 29, 2020
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Aerospike Server will not start If the value of default-ttl is non-zero and nsup-period is zero (the default).
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • Support added for HyperLogLog (HLL) probabilistic data types.
      • Clusters connected using Cross Datacenter Replication (XDR) all clusters must have been upgraded to Aerospike Server 4.9 prior to using the HyperLogLog (HLL) data type.
      • Before downgrading from Aerospike Server 4.9 all HyperLogLog (HLL) bins must be removed by the application.
      • During the unlikely case of a downgrade the drives would need to be wiped. It is advised to review your Aerospike Server 4.9 environment prior to implementing the usage of HyperLogLog (HLL) data type bins.
    • XDR, using ACL, in server versions between 4.1.0.1 and 4.3.0.6 cannot ship to this version. The simplest workaround is to avoid using those versions.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-6223] - (KVS) Poor intersect count estimate when intersecting more than two HyperLogLog sets.
      • [AER-6224] - (KVS) Incorrect parsing of signed integers in certain CDT operations (e.g. range operations) or bitwise BLOB operations (e.g. with negative offsets) may cause failures or bad results.

    Known Issues

  • 4.9.0.5
    Release Date: April 21, 2020
    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Aerospike Server will not start If the value of default-ttl is non-zero and nsup-period is zero (the default).
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • Support added for HyperLogLog (HLL) probabilistic data types.
      • Clusters connected using Cross Datacenter Replication (XDR) all clusters must have been upgraded to Aerospike Server 4.9 prior to using the HyperLogLog (HLL) data type.
      • Before downgrading from Aerospike Server 4.9 all HyperLogLog (HLL) bins must be removed by the application.
      • During the unlikely case of a downgrade the drives would need to be wiped. It is advised to review your Aerospike Server 4.9 environment prior to implementing the usage of HyperLogLog (HLL) data type bins.
    • XDR, using ACL, in server versions between 4.1.0.1 and 4.3.0.6 cannot ship to this version. The simplest workaround is to avoid using those versions.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Community Only
      • [AER-6220] - (STORAGE) In Community Edition, uninitialized storage bit may cause pre-4.9 nodes to reject records sent by 4.9 nodes.

    Known Issues

  • 4.9.0.4
    Release Date: April 17, 2020

    COMMUNITY EDITION USERS: Please use release 4.9.0.5 or newer in lieu of this version.

    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Aerospike Server will not start If the value of default-ttl is non-zero and nsup-period is zero (the default).
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • Support added for HyperLogLog (HLL) probabilistic data types.
      • Clusters connected using Cross Datacenter Replication (XDR) all clusters must have been upgraded to Aerospike Server 4.9 prior to using the HyperLogLog (HLL) data type.
      • Before downgrading from Aerospike Server 4.9 all HyperLogLog (HLL) bins must be removed by the application.
      • During the unlikely case of a downgrade the drives would need to be wiped. It is advised to review your Aerospike Server 4.9 environment prior to implementing the usage of HyperLogLog (HLL) data type bins.
    • XDR, using ACL, in server versions between 4.1.0.1 and 4.3.0.6 cannot ship to this version. The simplest workaround is to avoid using those versions.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-6215] - (KVS) HyperLogLog similarity estimates are inconsistent when all sets are empty.
      • [AER-6216] - (KVS) Dynamically increasing service context configuration item service-threads may cause an assert.
    • Enterprise Only
      • [AER-6214] - (ACL) Specifying a whitelist with a maximum set of (32) networks causes a stack memory stomp.

    Known Issues

  • 4.9.0.3
    Release Date: April 8, 2020

    COMMUNITY EDITION USERS: Please use release 4.9.0.5 or newer in lieu of this version.

    • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.
    • The Aerospike Server will not start If the value of default-ttl is non-zero and nsup-period is zero (the default).
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • Support added for HyperLogLog (HLL) probabilistic data types.
      • Clusters connected using Cross Datacenter Replication (XDR) all clusters must have been upgraded to Aerospike Server 4.9 prior to using the HyperLogLog (HLL) data type.
      • Before downgrading from Aerospike Server 4.9 all HyperLogLog (HLL) bins must be removed by the application.
      • During the unlikely case of a downgrade the drives would need to be wiped. It is advised to review your Aerospike Server 4.9 environment prior to implementing the usage of HyperLogLog (HLL) data type bins.
    • Added support for:
      • Partition-based basic scans, enabling accurate scans during migrations.
      • Added a max records option for sampling with basic scans.
      • Optional element creation in nested CDT operations.
    • XDR, using ACL, in server versions between 4.1.0.1 and 4.3.0.6 cannot ship to this version. The simplest workaround is to avoid using those versions.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    New Features

    • Enterprise & Community
      • [AER-6199] - (KVS) Added support for HyperLogLog (HLL) data types.
      • [AER-5474] - (SCAN) Basic scans now based on lists of partitions and/or digests sent by client.
      • [AER-6193] - (SCAN) Added a max records option for sampling with basic scans.
      • [AER-6203] - (CDT) Added support for optional element creation in nested CDT operations.

    Improvements

    • Enterprise & Community
      • [AER-6184] - (KVS) Configuring any eviction threshold (e.g. high-water-memory-pct) to 0 disables that eviction threshold.
      • [AER-6186] - (KVS) Changed eviction-related high water percentage configuration defaults to 0, so that eviction is inactive by default.
      • [AER-6187] - (KVS) Changed default value of nsup-period to 0, and added namespace context configuration item allow-ttl-without-nsup to allow records with TTLs when nsup-period is 0.
      • [AER-6185] - (BATCH) Added service context configuration item batch-without-digests to exclude digests from batch responses.
      • [AER-6209] - (NETWORK) Ignore additional addresses for an interface once the limit (20) is reached.
      • [AER-6192] - (MIGRATION) Increased metadata batch size and maximum outstanding data size limit, to help performance across longer links.
      • [AER-6191] - (LOGGING) Changed warning message about failure to resolve a mount point to a detail level message.
      • [AER-6210] - (LOGGING) Changed default logging level to 'critical' for all contexts.
      • [AER-6116] - (STATS) Converted 'batch-index' histogram to tracked histogram.
      • [AER-6183] - (STATS) Added delay count to batch-index log ticker line.
    • Enterprise Only
      • [AER-6205] - (KVS) Changed response (zlib) compression level to 1.
      • [AER-6208] - (KVS) Non-durable deletes will now ignore tombstones and return Not Found.
      • [AER-6158] - (TLS) Increased socket accept timeout to accommodate heartbeat across longer links.
      • [AER-6206] - (XDR) Changed (zlib) compression level to 1.

    Bug Fixes

    • Enterprise & Community
      • [AER-6211] - (KVS) Dynamically increasing both the system file descriptor limit and service context configuration item proto-fd-max to a value larger than the system limit at startup may cause an assert.

    Known Issues

    Updates

  • 4.8.0.31
    Release Date: March 29, 2021
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • 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.

    Known Issues

  • 4.8.0.29
    Release Date: March 12, 2021
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • 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-6401] - (CDT) When unwinding an index for a nested CDT op which turns out to be a no-op, the index may be corrupted.
      • [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.

    Known Issues

  • 4.8.0.28
    Release Date: February 22, 2021
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • 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

  • 4.8.0.27
    Release Date: January 30, 2021
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • 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.

    Known Issues

  • 4.8.0.26
    Release Date: January 25, 2021
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • CentOS Linux 8 End of Life is scheduled for December 2021.

    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

  • 4.8.0.25
    Release Date: January 4, 2021
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • 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.

    Bug Fixes

    • 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.

    Known Issues

  • 4.8.0.23
    Release Date: December 17, 2020
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • 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.

    Known Issues

  • 4.8.0.22
    Release Date: November 25, 2020
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Improvements

    • Enterprise Only
      • [AER-6338] - (TLS) Added support with Centos 7 for certain stronger ciphers.

    Bug Fixes

    • Enterprise & Community
      • [AER-6339] - (KVS) On certain bitwise blob operations (and, or, xor), an out of bounds byte may be accessed and cause a crash.

    Known Issues

  • 4.8.0.21
    Release Date: November 19, 2020
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-6336] - (BATCH) If both filters and bin selection are used in a batch request, proxied sub-transactions are malformed and will fail.

    Known Issues

  • 4.8.0.19
    Release Date: November 10, 2020
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-6326] - (KVS) When Aerospike runs as the init process (e.g. in some container scenarios), signals do not stop Aerospike as intended.

    Known Issues

  • 4.8.0.18
    Release Date: October 21, 2020
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Improvements

    • Enterprise & Community
      • [AER-6312] - (SECONDARY INDEX) When populating secondary indexes at startup, only read records in sets which have indexes.
    • Community Only
      • [AER-6314] - (PACKAGING) Removed Python dependency in Debian Community Edition builds.

    Bug Fixes

    • Enterprise & Community
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range.

    Known Issues

  • 4.8.0.17
    Release Date: October 14, 2020
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert.
      • [AER-6309] - (CDT) For ordered lists, get_all_by_value_list operation with result type value always returns an empty list.
    • Enterprise Only
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions.

    Known Issues

  • 4.8.0.15
    Release Date: September 18, 2020
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-6289] - (KVS) Concurrently reading and writing a new bin or set name may access a pointer which crosses a cache line boundary, causing a crash.
    • Enterprise Only
      • [AER-6287] - (KVS) When writing over a tombstone with Time-To-Live (TTL) value -2 (i.e. do not update TTL), the write fails to apply the namespace default-ttl.

    Known Issues

  • 4.8.0.14
    Release Date: July 7, 2020
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-6251] - (UDF) When a record UDF does not pass a predicate expression metadata filter, the server will deadlock.
    • Enterprise Only
      • [AER-6250] - (UDF) Race between a background UDF scan/query internal transaction and a durable delete may cause a deadlock.

    Known Issues

  • 4.8.0.13
    Release Date: June 18, 2020
    • XDR, using ACL, in server versions between 4.1.0.1 and 4.3.0.6 cannot ship to this version. The simplest workaround is to avoid using those versions.
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Improvements

    • Enterprise & Community
      • [AER-6238] - (SECURITY) Added service context configuration item disable-udf-execution as a mitigation option for Lua security vulnerabilities.

    Known Issues

  • 4.8.0.11
    Release Date: May 22, 2020
    • XDR, using ACL, in server versions between 4.1.0.1 and 4.3.0.6 cannot ship to this version. The simplest workaround is to avoid using those versions.
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated.

    Known Issues

  • 4.8.0.10
    Release Date: May 15, 2020
    • XDR, using ACL, in server versions between 4.1.0.1 and 4.3.0.6 cannot ship to this version. The simplest workaround is to avoid using those versions.
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise Only
      • [AER-6227] - (BALANCE) When applying uniform balance, a misused stack variable may cause an inaccurate balance and prevent migrations from completing.

    Known Issues

  • 4.8.0.9
    Release Date: April 17, 2020
    • XDR, using ACL, in server versions between 4.1.0.1 and 4.3.0.6 cannot ship to this version. The simplest workaround is to avoid using those versions.
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-6211] - (KVS) Dynamically increasing both the system file descriptor limit and service context configuration item proto-fd-max to a value larger than the system limit at startup may cause an assert.
      • [AER-6216] - (KVS) Dynamically increasing service context configuration item service-threads may cause an assert.
    • Enterprise Only
      • [AER-6214] - (ACL) Specifying a whitelist with a maximum set of (32) networks causes a stack memory stomp.

    Known Issues

  • 4.8.0.8
    Release Date: March 19, 2020
    • XDR, using ACL, in server versions between 4.1.0.1 and 4.3.0.6 cannot ship to this version. The simplest workaround is to avoid using those versions.
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive.
      • [AER-6194] - (GEO) For namespaces with data-in-memory true, GeoJSON particles allocate up to 2KB more than the reported particle size.
    • Enterprise Only
      • [AER-6195] - (MIGRATION) Theoretical race condition may cause delta migration to complete without sending all records.

    Known Issues

  • 4.8.0.6
    Release Date: February 28, 2020
    • XDR, using ACL, in server versions between 4.1.0.1 and 4.3.0.6 cannot ship to this version. The simplest workaround is to avoid using those versions.
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-6181] - (INFO) Namespace context configuration item enable-benchmarks-ops-sub is not returned by get-config.
      • [AER-6189] - (UDF) List creation via UDF does not initialize list flags, which may inadvertently flag the list as ordered.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF.
    • Enterprise Only
      • [AER-6178] - (STORAGE) Setting storage context configuration item compression dynamically for storage-engine memory namespaces is not prevented and may cause a crash.

    Known Issues

  • 4.8.0.5
    Release Date: January 21, 2020
    • XDR, using ACL, in server versions between 4.1.0.1 and 4.3.0.6 cannot ship to this version. The simplest workaround is to avoid using those versions.
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-6179] - (KVS) When upgrading from version earlier than 4.5.1, pre-existing eviction depth is not used during startup.
    • Enterprise Only
      • [AER-6170] - (XDR) Source node may crash when adding or removing namespaces in a destination cluster.
      • [AER-6172] - (XDR) Increasing datacenter context configuration item dc-connections dynamically may cause crash.

    Known Issues

  • 4.8.0.4
    Release Date: January 15, 2020
    • XDR, using ACL, in server versions between 4.1.0.1 and 4.3.0.6 cannot ship to this version. The simplest workaround is to avoid using those versions.
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise Only
      • [AER-6175] - (BALANCE) For strong-consistency namespaces, appeal subsystem leaks memory, and has rare races which may cause crash or deadlock.

    Known Issues

  • 4.8.0.3
    Release Date: January 6, 2020
    • XDR, using ACL, in server versions between 4.1.0.1 and 4.3.0.6 cannot ship to this version. The simplest workaround is to avoid using those versions.
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-6174] - (KVS) For namespaces with data-in-memory true, a delete record op applied to a record with more than one bin may cause a crash.

    Known Issues

  • 4.8.0.2
    Release Date: December 16, 2019
    • XDR, using ACL, in server versions between 4.1.0.1 and 4.3.0.6 cannot ship to this version. The simplest workaround is to avoid using those versions.
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise Only
      • [AER-6169] - (AUDIT) Reporting of login failures erroneously requires setting security log/syslog context configuration item report-authentication true.

    Known Issues

  • 4.8.0.1
    Release Date: December 12, 2019
    • XDR, using ACL, in server versions between 4.1.0.1 and 4.3.0.6 cannot ship to this version. The simplest workaround is to avoid using those versions.
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    New Features

    • Enterprise & Community
      • [AER-6145] - (PACKAGING) Added support for CentOS 8.
    • Enterprise Only
      • [AER-6136] - (KVS) Added support for client/server compression.
      • [AER-6164] - (STORAGE) Added value pmem for namespace context configuration item storage-engine, to use persistent memory for data storage.

    Improvements

    • Enterprise & Community
      • [AER-6134] - (KVS) Use separate write buffers for replicated and migrated records, to avoid polluting the post-write queue.
      • [AER-6141] - (KVS) Use keep-alive for client sockets.
      • [AER-6161] - (INFO) Added info command 'sindex-exists' to indicate whether a specified index exists.
      • [AER-6142] - (STATS) Removed 'svc-demarshal' and 'svc-queue' benchmark histograms, and added namespace context batch-sub-prestart benchmark histogram.
    • Enterprise Only
      • [AER-6167] - (DEPLOYMENT) Added pmem feature key to cover both index-type pmem and storage-engine pmem, deprecated 'pmem-index' and 'all-flash' feature keys.
      • [AER-6118] - (LOGGING) Changed warning text for internal user attempting login with external authentication mode to not mention 'ldap'.

    Bug Fixes

    • Enterprise Only
      • [AER-6155] - (XDR) Allow only 'v1' for the datacenter context configuration item http-version to avoid issues in HTTP v2.

    Known Issues

    Updates

  • 4.7.0.26
    Release Date: November 25, 2020
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Improvements

    • Enterprise Only
      • [AER-6338] - (TLS) Added support with Centos 7 for certain stronger ciphers.

    Bug Fixes

    • Enterprise & Community
      • [AER-6339] - (KVS) On certain bitwise blob operations (and, or, xor), an out of bounds byte may be accessed and cause a crash.

    Known Issues

  • 4.7.0.25
    Release Date: November 19, 2020
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-6336] - (BATCH) If both filters and bin selection are used in a batch request, proxied sub-transactions are malformed and will fail.

    Known Issues

  • 4.7.0.23
    Release Date: November 10, 2020
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-6326] - (KVS) When Aerospike runs as the init process (e.g. in some container scenarios), signals do not stop Aerospike as intended.

    Known Issues

  • 4.7.0.22
    Release Date: October 21, 2020
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Improvements

    • Enterprise & Community
      • [AER-6312] - (SECONDARY INDEX) When populating secondary indexes at startup, only read records in sets which have indexes.

    Bug Fixes

    • Enterprise & Community
      • [AER-6315] - (STATS) Initial TTL histogram collected for a set does not have the correct range.

    Known Issues

  • 4.7.0.21
    Release Date: October 14, 2020
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-6307] - (CDT) Operations comparing a msgpack 32-bit float will cause an assert.
      • [AER-6309] - (CDT) For ordered lists, get_all_by_value_list operation with result type value always returns an empty list.
    • Enterprise Only
      • [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions.

    Known Issues

  • 4.7.0.19
    Release Date: September 18, 2020
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-6289] - (KVS) Concurrently reading and writing a new bin or set name may access a pointer which crosses a cache line boundary, causing a crash.
    • Enterprise Only
      • [AER-6287] - (KVS) When writing over a tombstone with Time-To-Live (TTL) value -2 (i.e. do not update TTL), the write fails to apply the namespace default-ttl.

    Known Issues

  • 4.7.0.18
    Release Date: July 7, 2020
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-6251] - (UDF) When a record UDF does not pass a predicate expression metadata filter, the server will deadlock.
    • Enterprise Only
      • [AER-6250] - (UDF) Race between a background UDF scan/query internal transaction and a durable delete may cause a deadlock.

    Known Issues

  • 4.7.0.17
    Release Date: June 18, 2020
    • XDR, using ACL, in server versions between 4.1.0.1 and 4.3.0.6 cannot ship to this version. The simplest workaround is to avoid using those versions.
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Improvements

    • Enterprise & Community
      • [AER-6238] - (SECURITY) Added service context configuration item disable-udf-execution as a mitigation option for Lua security vulnerabilities.

    Known Issues

  • 4.7.0.15
    Release Date: May 22, 2020
    • XDR, using ACL, in server versions between 4.1.0.1 and 4.3.0.6 cannot ship to this version. The simplest workaround is to avoid using those versions.
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated.

    Known Issues

  • 4.7.0.14
    Release Date: May 15, 2020
    • XDR, using ACL, in server versions between 4.1.0.1 and 4.3.0.6 cannot ship to this version. The simplest workaround is to avoid using those versions.
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise Only
      • [AER-6227] - (BALANCE) When applying uniform balance, a misused stack variable may cause an inaccurate balance and prevent migrations from completing.

    Known Issues

  • 4.7.0.13
    Release Date: April 17, 2020
    • XDR, using ACL, in server versions between 4.1.0.1 and 4.3.0.6 cannot ship to this version. The simplest workaround is to avoid using those versions.
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-6211] - (KVS) Dynamically increasing both the system file descriptor limit and service context configuration item proto-fd-max to a value larger than the system limit at startup may cause an assert.
      • [AER-6216] - (KVS) Dynamically increasing service context configuration item service-threads may cause an assert.
    • Enterprise Only
      • [AER-6214] - (ACL) Specifying a whitelist with a maximum set of (32) networks causes a stack memory stomp.

    Known Issues

  • 4.7.0.12
    Release Date: March 19, 2020
    • XDR, using ACL, in server versions between 4.1.0.1 and 4.3.0.6 cannot ship to this version. The simplest workaround is to avoid using those versions.
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive.
      • [AER-6194] - (GEO) For namespaces with data-in-memory true, GeoJSON particles allocate up to 2KB more than the reported particle size.
    • Enterprise Only
      • [AER-6195] - (MIGRATION) Theoretical race condition may cause delta migration to complete without sending all records.

    Known Issues

  • 4.7.0.11
    Release Date: February 28, 2020
    • XDR, using ACL, in server versions between 4.1.0.1 and 4.3.0.6 cannot ship to this version. The simplest workaround is to avoid using those versions.
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-6181] - (INFO) Namespace context configuration item enable-benchmarks-ops-sub is not returned by get-config.
      • [AER-6189] - (UDF) List creation via UDF does not initialize list flags, which may inadvertently flag the list as ordered.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF.
    • Enterprise Only
      • [AER-6178] - (STORAGE) Setting storage context configuration item compression dynamically for storage-engine memory namespaces is not prevented and may cause a crash.

    Known Issues

  • 4.7.0.10
    Release Date: January 21, 2020
    • XDR, using ACL, in server versions between 4.1.0.1 and 4.3.0.6 cannot ship to this version. The simplest workaround is to avoid using those versions.
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-6179] - (KVS) When upgrading from version earlier than 4.5.1, pre-existing eviction depth is not used during startup.
    • Enterprise Only
      • [AER-6170] - (XDR) Source node may crash when adding or removing namespaces in a destination cluster.
      • [AER-6172] - (XDR) Increasing datacenter context configuration item dc-connections dynamically may cause crash.

    Known Issues

  • 4.7.0.9
    Release Date: January 15, 2020
    • XDR, using ACL, in server versions between 4.1.0.1 and 4.3.0.6 cannot ship to this version. The simplest workaround is to avoid using those versions.
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise Only
      • [AER-6175] - (BALANCE) For strong-consistency namespaces, appeal subsystem leaks memory, and has rare races which may cause crash or deadlock.

    Known Issues

  • 4.7.0.8
    Release Date: January 6, 2020
    • XDR, using ACL, in server versions between 4.1.0.1 and 4.3.0.6 cannot ship to this version. The simplest workaround is to avoid using those versions.
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-6174] - (KVS) For namespaces with data-in-memory true, a delete record op applied to a record with more than one bin may cause a crash.

    Known Issues

  • 4.7.0.7
    Release Date: December 16, 2019
    • XDR, using ACL, in server versions between 4.1.0.1 and 4.3.0.6 cannot ship to this version. The simplest workaround is to avoid using those versions.
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise Only
      • [AER-6169] - (AUDIT) Reporting of login failures erroneously requires setting security log/syslog context configuration item report-authentication true.

    Known Issues

  • 4.7.0.6
    Release Date: December 6, 2019
    • XDR, using ACL, in server versions between 4.1.0.1 and 4.3.0.6 cannot ship to this version. The simplest workaround is to avoid using those versions.
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure.
      • [AER-6159] - (INFO) The thread-traces info command can cause a deadlock.
      • [AER-6165] - (CDT) by_value_list and by_key_list OPs do not accept non-storage tokens such as WILDCARD.
    • Enterprise Only
      • [AER-6163] - (STORAGE) When using compression, migrated, replicated, or duplicate-resolved records may be incorrectly rejected by destination node for being too big.

    Known Issues

  • 4.7.0.5
    Release Date: November 14, 2019
    • XDR, using ACL, in server versions between 4.1.0.1 and 4.3.0.6 cannot ship to this version. The simplest workaround is to avoid using those versions.
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-6146] - (KVS) With debug-allocations enabled, a memory accounting array will eventually overflow and cause a crash.
    • Enterprise Only
      • [AER-6152] - (KVS) With auto-pin numa, namespaces with index-type pmem will assert at startup.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections.

    Known Issues

  • 4.7.0.3
    Release Date: November 1, 2019
    • XDR, using ACL, in server versions between 4.1.0.1 and 4.3.0.6 cannot ship to this version. The simplest workaround is to avoid using those versions.
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-6140] - (CDT) Map context unwind causes crash for namespaces with data-in-memory true when original map had incomplete order index.
      • [AER-6132] - (CDT) Get or remove by key for map with element count 1 and result type index or rank returns a list instead of a scalar.
    • Enterprise Only
      • [AER-6143] - (BALANCE) For strong-consistency namespaces, if quiescing nodes with non-roster nodes in the cluster, the wrong nodes may quiesce.

    Known Issues

  • 4.7.0.2
    Release Date: September 30, 2019

    New Features

    • Enterprise & Community
      • [AER-6096] - (KVS) Added delete of entire record as an operation (e.g. to enable atomic read then delete).
      • [AER-6101] - (KVS) Added predicate filter support for batch, read, write, delete, and record UDF transactions.
      • [AER-6123] - (KVS) Added support for ADQ.
      • [AER-6109] - (SCAN) Added a new type of background scan and query that performs (write only) operations.
    • Enterprise Only
      • [AER-6124] - (XDR) Added LDAP login support for XDR.

    Improvements

    • Enterprise & Community
      • [AER-6112] - (KVS) Removed service context configuration items transaction-queues and transaction-threads-per-queue, and made service context configuration item service-threads dynamic.
      • [AER-6113] - (KVS) Increased maximum allowed value of storage context configuration item post-write-queue to 8192.
      • [AER-6100] - (SCAN) Scans now use their own thread(s) instead of sharing a thread pool, and are given a record-per-second limit instead of a priority.
      • [AER-6106] - (STATS) Added CPU usage in stats and log ticker.
    • Enterprise Only
      • [AER-6102] - (BALANCE) Changed default setting of namespace context configuration item prefer-uniform-balance to true.
      • [AER-6105] - (XDR) Certificate is presented to http destination when required for mutual authentication.

    Bug Fixes

    • Enterprise & Community
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate.
      • [AER-6128] - (BALANCE) For AP namespaces with prefer-uniform-balance true, non-optimal masters may be selected.

    Known Issues

  • 4.6.0.21
    Release Date: September 18, 2020
    • A digitally signed feature key file is now required. (Enterprise Only)
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • For Aerospike Server versions prior to 4.7 XDR does not support LDAP logins.
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-6289] - (KVS) Concurrently reading and writing a new bin or set name may access a pointer which crosses a cache line boundary, causing a crash.
    • Enterprise Only
      • [AER-6287] - (KVS) When writing over a tombstone with Time-To-Live (TTL) value -2 (i.e. do not update TTL), the write fails to apply the namespace default-ttl.

    Known Issues

  • 4.6.0.20
    Release Date: July 7, 2020
    • A digitally signed feature key file is now required. (Enterprise Only)
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • For Aerospike Server versions prior to 4.7 XDR does not support LDAP logins.
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise Only
      • [AER-6250] - (UDF) Race between a background UDF scan/query internal transaction and a durable delete may cause a deadlock.

    Known Issues

  • 4.6.0.19
    Release Date: June 18, 2020
    • A digitally signed feature key file is now required. (Enterprise Only)
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • XDR, using ACL, in server versions between 4.1.0.1 and 4.3.0.6 cannot ship to this version. The simplest workaround is to avoid using those versions.
    • For Aerospike Server versions prior to 4.7 XDR does not support LDAP logins.
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Improvements

    • Enterprise & Community
      • [AER-6238] - (SECURITY) Added service context configuration item disable-udf-execution as a mitigation option for Lua security vulnerabilities.

    Known Issues

  • 4.6.0.17
    Release Date: May 22, 2020
    • A digitally signed feature key file is now required. (Enterprise Only)
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • XDR, using ACL, in server versions between 4.1.0.1 and 4.3.0.6 cannot ship to this version. The simplest workaround is to avoid using those versions.
    • For Aerospike Server versions prior to 4.7 XDR does not support LDAP logins.
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated.

    Known Issues

  • 4.6.0.16
    Release Date: May 15, 2020
    • A digitally signed feature key file is now required. (Enterprise Only)
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • XDR, using ACL, in server versions between 4.1.0.1 and 4.3.0.6 cannot ship to this version. The simplest workaround is to avoid using those versions.
    • For Aerospike Server versions prior to 4.7 XDR does not support LDAP logins.
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise Only
      • [AER-6227] - (BALANCE) When applying uniform balance, a misused stack variable may cause an inaccurate balance and prevent migrations from completing.

    Known Issues

  • 4.6.0.15
    Release Date: April 17, 2020
    • A digitally signed feature key file is now required. (Enterprise Only)
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • XDR, using ACL, in server versions between 4.1.0.1 and 4.3.0.6 cannot ship to this version. The simplest workaround is to avoid using those versions.
    • For Aerospike Server versions prior to 4.7 XDR does not support LDAP logins.
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-6211] - (KVS) Dynamically increasing both the system file descriptor limit and service context configuration item proto-fd-max to a value larger than the system limit at startup may cause an assert.
    • Enterprise Only
      • [AER-6214] - (ACL) Specifying a whitelist with a maximum set of (32) networks causes a stack memory stomp.

    Known Issues

  • 4.6.0.14
    Release Date: March 19, 2020
    • A digitally signed feature key file is now required. (Enterprise Only)
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • XDR, using ACL, in server versions between 4.1.0.1 and 4.3.0.6 cannot ship to this version. The simplest workaround is to avoid using those versions.
    • For Aerospike Server versions prior to 4.7 XDR does not support LDAP logins.
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive.
      • [AER-6194] - (GEO) For namespaces with data-in-memory true, GeoJSON particles allocate up to 2KB more than the reported particle size.
    • Enterprise Only
      • [AER-6195] - (MIGRATION) Theoretical race condition may cause delta migration to complete without sending all records.

    Known Issues

  • 4.6.0.13
    Release Date: February 28, 2020
    • A digitally signed feature key file is now required. (Enterprise Only)
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • XDR, using ACL, in server versions between 4.1.0.1 and 4.3.0.6 cannot ship to this version. The simplest workaround is to avoid using those versions.
    • For Aerospike Server versions prior to 4.7 XDR does not support LDAP logins.
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-6189] - (UDF) List creation via UDF does not initialize list flags, which may inadvertently flag the list as ordered.
      • [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF.
    • Enterprise Only
      • [AER-6178] - (STORAGE) Setting storage context configuration item compression dynamically for storage-engine memory namespaces is not prevented and may cause a crash.

    Known Issues

  • 4.6.0.12
    Release Date: January 21, 2020
    • A digitally signed feature key file is now required. (Enterprise Only)
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • XDR, using ACL, in server versions between 4.1.0.1 and 4.3.0.6 cannot ship to this version. The simplest workaround is to avoid using those versions.
    • For Aerospike Server versions prior to 4.7 XDR does not support LDAP logins.
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-6179] - (KVS) When upgrading from version earlier than 4.5.1, pre-existing eviction depth is not used during startup.
    • Enterprise Only
      • [AER-6170] - (XDR) Source node may crash when adding or removing namespaces in a destination cluster.
      • [AER-6172] - (XDR) Increasing datacenter context configuration item dc-connections dynamically may cause crash.

    Known Issues

  • 4.6.0.11
    Release Date: January 15, 2020
    • A digitally signed feature key file is now required. (Enterprise Only)
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • XDR, using ACL, in server versions between 4.1.0.1 and 4.3.0.6 cannot ship to this version. The simplest workaround is to avoid using those versions.
    • For Aerospike Server versions prior to 4.7 XDR does not support LDAP logins.
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise Only
      • [AER-6175] - (BALANCE) For strong-consistency namespaces, appeal subsystem leaks memory, and has rare races which may cause crash or deadlock.

    Known Issues

  • 4.6.0.10
    Release Date: December 16, 2019
    • A digitally signed feature key file is now required. (Enterprise Only)
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • XDR, using ACL, in server versions between 4.1.0.1 and 4.3.0.6 cannot ship to this version. The simplest workaround is to avoid using those versions.
    • For Aerospike Server versions prior to 4.7 XDR does not support LDAP logins.
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise Only
      • [AER-6169] - (AUDIT) Reporting of login failures erroneously requires setting security log/syslog context configuration item report-authentication true.

    Known Issues

  • 4.6.0.9
    Release Date: December 6, 2019
    • A digitally signed feature key file is now required. (Enterprise Only)
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • XDR, using ACL, in server versions between 4.1.0.1 and 4.3.0.6 cannot ship to this version. The simplest workaround is to avoid using those versions.
    • For Aerospike Server versions prior to 4.7 XDR does not support LDAP logins.
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure.
      • [AER-6165] - (CDT) by_value_list and by_key_list OPs do not accept non-storage tokens such as WILDCARD.
    • Enterprise Only
      • [AER-6163] - (STORAGE) When using compression, migrated, replicated, or duplicate-resolved records may be incorrectly rejected by destination node for being too big.

    Known Issues

  • 4.6.0.8
    Release Date: November 14, 2019
    • A digitally signed feature key file is now required. (Enterprise Only)
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • XDR, using ACL, in server versions between 4.1.0.1 and 4.3.0.6 cannot ship to this version. The simplest workaround is to avoid using those versions.
    • For Aerospike Server versions prior to 4.7 XDR does not support LDAP logins.
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-6146] - (KVS) With debug-allocations enabled, a memory accounting array will eventually overflow and cause a crash.
    • Enterprise Only
      • [AER-6152] - (KVS) With auto-pin numa, namespaces with index-type pmem will assert at startup.
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections.

    Known Issues

  • 4.6.0.6
    Release Date: November 1, 2019
    • A digitally signed feature key file is now required. (Enterprise Only)
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • XDR, using ACL, in server versions between 4.1.0.1 and 4.3.0.6 cannot ship to this version. The simplest workaround is to avoid using those versions.
    • For Aerospike Server versions prior to 4.7 XDR does not support LDAP logins.
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-6140] - (CDT) Map context unwind causes crash for namespaces with data-in-memory true when original map had incomplete order index.
      • [AER-6132] - (CDT) Get or remove by key for map with element count 1 and result type index or rank returns a list instead of a scalar.

    Known Issues

  • 4.6.0.5
    Release Date: October 3, 2019
    • A digitally signed feature key file is now required. (Enterprise Only)
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • XDR, using ACL, in server versions between 4.1.0.1 and 4.3.0.6 cannot ship to this version. The simplest workaround is to avoid using those versions.
    • For Aerospike Server versions prior to 4.7 XDR does not support LDAP logins.
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate.
      • [AER-6128] - (BALANCE) For AP namespaces with prefer-uniform-balance true, non-optimal masters may be selected.

    Known Issues

  • 4.6.0.4
    Release Date: August 28, 2019
    • A digitally signed feature key file is now required. (Enterprise Only)
      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • XDR, using ACL, in server versions between 4.1.0.1 and 4.3.0.6 cannot ship to this version. The simplest workaround is to avoid using those versions.
    • For Aerospike Server versions prior to 4.7 XDR does not support LDAP logins.
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Improvements

    • Enterprise Only
      • [AER-6099] - (ACL) Allow security module to exchange SMD in a cluster where security is not enabled on all nodes.

    Bug Fixes

    • Enterprise & Community
      • [AER-6097] - (CDT) Improved msgpack comparison and sizing methods to reduce CPU usage.
    • Enterprise Only
      • [AER-6104] - (KVS) For index-type flash, index allocation errors may cause crash.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart.

    Known Issues

  • 4.6.0.2
    Release Date: August 9, 2019
    • In server release 4.6.0.2, we have noticed that certain CDT use cases consume more CPU than in previous releases. This has been fixed in 4.6.0.4.

    • A digitally signed feature key file is now required. (Enterprise Only)

      • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
    • XDR, using ACL, in server versions between 4.1.0.1 and 4.3.0.6 cannot ship to this version. The simplest workaround is to avoid using those versions.
    • For Aerospike Server versions prior to 4.7 XDR does not support LDAP logins.
    • We have added support for Debian 10.
    • We have deprecated support for Debian 7.
    • New API for nested CDT operations.
    • New API for bitwise operations on BLOB particles.
    • When upgrading the Aerospike Server, from a version prior to 4.6, with the security feature enabled, make sure all Aerospike Clients are running a compatible version. (Enterprise Only)
    • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    New Features

    • Enterprise & Community
      • [AER-6074] - (KVS) Added bitwise BLOB operations.
      • [AER-6092] - (CDT) Added APIs to operate on lists and maps nested within lists and maps.
    • Enterprise Only
      • [AER-6079] - (DEPLOYMENT) Enterprise Edition now requires a feature key.
      • [AER-6065] - (ACL) Added predefined 'write' (write only) permission for use in defining custom roles.
      • [AER-6066] - (ACL) Added support for specifying network whitelists on custom roles.

    Improvements

    • Enterprise & Community
      • [AER-6062] - (KVS) Added namespace context configuration item truncate-threads to specify the number of threads used by truncations.
      • [AER-6091] - (KVS) Added service context configuration item indent-allocations to enhance double-free detection when debugging the heap.
      • [AER-6061] - (DEPLOYMENT) Increased grace period to 10 minutes before clean shutdowns are aborted, and enhanced logging during shutdown.
      • [AER-6078] - (BALANCE) Working masters (also) report ownership of appropriate replicas in client partition map (e.g. to optimize rack-aware client reads in certain situations).
      • [AER-6085] - (STORAGE) Re-use freed write blocks in the order they were freed (e.g. will allow tomb raider to clear tombstones more effectively).
      • [AER-6058] - (LOGGING) Made improvements to secondary index ('sindex' context) log messages.
      • [AER-6070] - (LOGGING) Added thread count to log message at start of nsup expire and evict cycles.
    • Enterprise Only
      • [AER-6081] - (KVS) For index-type flash and index-type pmem, warn at startup if index devices are not mounted.
      • [AER-6084] - (INFO) Report true default values for storage context configuration item compression-level (if compression zstd is used) and TLS context configuration item protocols.
      • [AER-6080] - (LDAP) Do not allow logins by external (LDAP) users who have an internal password.

    Bug Fixes

    • Enterprise & Community
      • [AER-6093] - (CDT) Get or remove by rank map operation with return type key or value returning nil element will access uninitialized memory.
      • [AER-6094] - (CDT) Get or remove by key-list ordered map operation with return type index, where key-list elements are not in map returns incomplete response.

    Known Issues

    Updates

  • 4.5.3.22
    Release Date: July 7, 2020
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise Only
      • [AER-6250] - (UDF) Race between a background UDF scan/query internal transaction and a durable delete may cause a deadlock.

    Known Issues

  • 4.5.3.21
    Release Date: June 18, 2020
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Improvements

    • Enterprise & Community
      • [AER-6238] - (SECURITY) Added service context configuration item disable-udf-execution as a mitigation option for Lua security vulnerabilities.

    Known Issues

  • 4.5.3.19
    Release Date: May 22, 2020
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated.

    Known Issues

  • 4.5.3.18
    Release Date: May 15, 2020
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise Only
      • [AER-6227] - (BALANCE) When applying uniform balance, a misused stack variable may cause an inaccurate balance and prevent migrations from completing.

    Known Issues

  • 4.5.3.17
    Release Date: April 17, 2020
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-6211] - (KVS) Dynamically increasing both the system file descriptor limit and service context configuration item proto-fd-max to a value larger than the system limit at startup may cause an assert.

    Known Issues

  • 4.5.3.16
    Release Date: March 19, 2020
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive.
      • [AER-6194] - (GEO) For namespaces with data-in-memory true, GeoJSON particles allocate up to 2KB more than the reported particle size.
    • Enterprise Only
      • [AER-6195] - (MIGRATION) Theoretical race condition may cause delta migration to complete without sending all records.

    Known Issues

  • 4.5.3.15
    Release Date: February 28, 2020
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-6189] - (UDF) List creation via UDF does not initialize list flags, which may inadvertently flag the list as ordered.
    • Enterprise Only
      • [AER-6178] - (STORAGE) Setting storage context configuration item compression dynamically for storage-engine memory namespaces is not prevented and may cause a crash.

    Known Issues

  • 4.5.3.14
    Release Date: January 21, 2020
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-6179] - (KVS) When upgrading from version earlier than 4.5.1, pre-existing eviction depth is not used during startup.
    • Enterprise Only
      • [AER-6170] - (XDR) Source node may crash when adding or removing namespaces in a destination cluster.
      • [AER-6172] - (XDR) Increasing datacenter context configuration item dc-connections dynamically may cause crash.

    Known Issues

  • 4.5.3.13
    Release Date: January 15, 2020
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise Only
      • [AER-6175] - (BALANCE) For strong-consistency namespaces, appeal subsystem leaks memory, and has rare races which may cause crash or deadlock.

    Known Issues

  • 4.5.3.12
    Release Date: December 16, 2019
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise Only
      • [AER-6169] - (AUDIT) Reporting of login failures erroneously requires setting security log/syslog context configuration item report-authentication true.

    Known Issues

  • 4.5.3.11
    Release Date: December 6, 2019
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure.
    • Enterprise Only
      • [AER-6163] - (STORAGE) When using compression, migrated, replicated, or duplicate-resolved records may be incorrectly rejected by destination node for being too big.

    Known Issues

  • 4.5.3.10
    Release Date: November 14, 2019
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-6146] - (KVS) With debug-allocations enabled, a memory accounting array will eventually overflow and cause a crash.
    • Enterprise Only
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections.

    Known Issues

  • 4.5.3.8
    Release Date: November 1, 2019
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-6132] - (CDT) Get or remove by key for map with element count 1 and result type index or rank returns a list instead of a scalar.

    Known Issues

  • 4.5.3.7
    Release Date: October 3, 2019
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate.
      • [AER-6128] - (BALANCE) For AP namespaces with prefer-uniform-balance true, non-optimal masters may be selected.

    Known Issues

  • 4.5.3.6
    Release Date: August 28, 2019
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Improvements

    • Enterprise Only
      • [AER-6099] - (ACL) Allow security module to exchange SMD in a cluster where security is not enabled on all nodes.

    Bug Fixes

    • Enterprise & Community
      • [AER-6093] - (CDT) Get or remove by rank map operation with return type key or value returning nil element will access uninitialized memory.
      • [AER-6094] - (CDT) Get or remove by key-list ordered map operation with return type index, where key-list elements are not in map returns incomplete response.
    • Enterprise Only
      • [AER-6104] - (KVS) For index-type flash, index allocation errors may cause crash.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart.

    Known Issues

  • 4.5.3.5
    Release Date: July 31, 2019
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Improvements

    • Enterprise Only
      • [AER-6088] - (LDAP) Added support for LDAPS.

    Bug Fixes

    • Enterprise & Community
      • [AER-6086] - (CDT) Single result operations returning boolean are not translated correctly to integer.
      • [AER-6087] - (CDT) List operations by rank and with return type rank can crash when specifying out of range rank as input.
    • Enterprise Only
      • [AER-6090] - (AUDIT) Batch sub-transactions' digests are not logged in the report-data-op audit trail.
      • [AER-6089] - (XDR) Race condition across multiple connections in libcurl may cause crash.

    Known Issues

  • 4.5.3.4
    Release Date: June 28, 2019
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Improvements

    • Enterprise & Community
      • [AER-6073] - (KVS) Validate the set name (if sent) in read and delete messages.

    Bug Fixes

    • Enterprise & Community
      • [AER-6077] - (BATCH) For storage-engine memory namespaces, batch transactions unnecessarily return an error if record size exceeds 10MB.
    • Enterprise Only
      • [AER-6072] - (XDR) Crash using multi-handles in curl library when using change notification.
      • [AER-6075] - (XDR) Dynamically setting xdr context configuration items when configuration file has no xdr context causes crash.

    Known Issues

  • 4.5.3.3
    Release Date: May 31, 2019
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Improvements

    • Enterprise & Community
      • [AER-6057] - (STORAGE) Added storage context configuration item disable-odsync to prevent setting O_DSYNC flag on storage devices.

    Bug Fixes

    • Enterprise & Community
      • [AER-6068] - (LOGGING) Concurrent SIGHUPs to roll log files may race and double close a log sink file descriptor.
    • Enterprise Only
      • [AER-6069] - (LDAP) Minor memory leak during LDAP login process.

    Known Issues

  • 4.5.3.2
    Release Date: May 14, 2019
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Improvements

    • Enterprise & Community
      • [AER-6043] - (KVS) Support aliasing and bonding plus aliases for auto-pin configuration.
      • [AER-6056] - (KVS) For increased efficiency, especially when using compression, flat storage format now also used as wire format for replication, migration, and duplicate resolution.
      • [AER-6055] - (INFO) Added info command thread-traces to show the current call stack for all server threads.
    • Enterprise Only
      • [AER-6027] - (TLS) Removed support for SSLv3.

    Bug Fixes

    • Enterprise & Community
      • [AER-6040] - (DEPLOYMENT) Aerospike will not start under systemd as non-root when using index-type value 'flash' or auto-pin value 'numa'.
      • [AER-6053] - (SCAN) Dynamically decreasing service context configuration items scan-threads or sindex-builder-threads temporarily blocks all (other) dynamic configurations.

    Known Issues

    Updates

  • 4.5.2.18
    Release Date: May 15, 2020
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • Aerospike Tools version 3.18.1 dependencies
      • Aerospike Tools 3.18.1 now requires Python version 2.7.
      • Aerospike Tools 3.18.1 now requires Java version 1.8 or newer.

    Bug Fixes

    • Enterprise Only
      • [AER-6227] - (BALANCE) When applying uniform balance, a misused stack variable may cause an inaccurate balance and prevent migrations from completing.

    Known Issues

  • 4.5.2.17
    Release Date: April 17, 2020
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • Aerospike Tools version 3.18.1 dependencies
      • Aerospike Tools 3.18.1 now requires Python version 2.7.
      • Aerospike Tools 3.18.1 now requires Java version 1.8 or newer.

    Bug Fixes

    • Enterprise & Community
      • [AER-6211] - (KVS) Dynamically increasing both the system file descriptor limit and service context configuration item proto-fd-max to a value larger than the system limit at startup may cause an assert.

    Known Issues

  • 4.5.2.16
    Release Date: March 19, 2020
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • Aerospike Tools version 3.18.1 dependencies
      • Aerospike Tools 3.18.1 now requires Python version 2.7.
      • Aerospike Tools 3.18.1 now requires Java version 1.8 or newer.

    Bug Fixes

    • Enterprise & Community
      • [AER-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive.
      • [AER-6194] - (GEO) For namespaces with data-in-memory true, GeoJSON particles allocate up to 2KB more than the reported particle size.
    • Enterprise Only
      • [AER-6195] - (MIGRATION) Theoretical race condition may cause delta migration to complete without sending all records.

    Known Issues

  • 4.5.2.15
    Release Date: February 28, 2020
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • Aerospike Tools version 3.18.1 dependencies
      • Aerospike Tools 3.18.1 now requires Python version 2.7.
      • Aerospike Tools 3.18.1 now requires Java version 1.8 or newer.

    Bug Fixes

    • Enterprise & Community
      • [AER-6189] - (UDF) List creation via UDF does not initialize list flags, which may inadvertently flag the list as ordered.
    • Enterprise Only
      • [AER-6178] - (STORAGE) Setting storage context configuration item compression dynamically for storage-engine memory namespaces is not prevented and may cause a crash.

    Known Issues

  • 4.5.2.14
    Release Date: January 21, 2020
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • Aerospike Tools version 3.18.1 dependencies
      • Aerospike Tools 3.18.1 now requires Python version 2.7.
      • Aerospike Tools 3.18.1 now requires Java version 1.8 or newer.

    Bug Fixes

    • Enterprise & Community
      • [AER-6179] - (KVS) When upgrading from version earlier than 4.5.1, pre-existing eviction depth is not used during startup.

    Known Issues

  • 4.5.2.13
    Release Date: January 15, 2020
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • Aerospike Tools version 3.18.1 dependencies
      • Aerospike Tools 3.18.1 now requires Python version 2.7.
      • Aerospike Tools 3.18.1 now requires Java version 1.8 or newer.

    Bug Fixes

    • Enterprise Only
      • [AER-6175] - (BALANCE) For strong-consistency namespaces, appeal subsystem leaks memory, and has rare races which may cause crash or deadlock.

    Known Issues

  • 4.5.2.12
    Release Date: December 16, 2019
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • Aerospike Tools version 3.18.1 dependencies
      • Aerospike Tools 3.18.1 now requires Python version 2.7.
      • Aerospike Tools 3.18.1 now requires Java version 1.8 or newer.

    Bug Fixes

    • Enterprise Only
      • [AER-6169] - (AUDIT) Reporting of login failures erroneously requires setting security log/syslog context configuration item report-authentication true.

    Known Issues

  • 4.5.2.11
    Release Date: December 6, 2019
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • Aerospike Tools version 3.18.1 dependencies
      • Aerospike Tools 3.18.1 now requires Python version 2.7.
      • Aerospike Tools 3.18.1 now requires Java version 1.8 or newer.

    Bug Fixes

    • Enterprise & Community
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure.

    Known Issues

  • 4.5.2.10
    Release Date: November 14, 2019
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • Aerospike Tools version 3.18.1 dependencies
      • Aerospike Tools 3.18.1 now requires Python version 2.7.
      • Aerospike Tools 3.18.1 now requires Java version 1.8 or newer.

    Bug Fixes

    • Enterprise & Community
      • [AER-6146] - (KVS) With debug-allocations enabled, a memory accounting array will eventually overflow and cause a crash.
    • Enterprise Only
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections.

    Known Issues

  • 4.5.2.8
    Release Date: November 1, 2019
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • Aerospike Tools version 3.18.1 dependencies
      • Aerospike Tools 3.18.1 now requires Python version 2.7.
      • Aerospike Tools 3.18.1 now requires Java version 1.8 or newer.

    Bug Fixes

    • Enterprise & Community
      • [AER-6132] - (CDT) Get or remove by key for map with element count 1 and result type index or rank returns a list instead of a scalar.

    Known Issues

  • 4.5.2.7
    Release Date: October 3, 2019
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • Aerospike Tools version 3.18.1 dependencies
      • Aerospike Tools 3.18.1 now requires Python version 2.7.
      • Aerospike Tools 3.18.1 now requires Java version 1.8 or newer.

    Bug Fixes

    • Enterprise & Community
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate.

    Known Issues

  • 4.5.2.6
    Release Date: August 28, 2019
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • Aerospike Tools version 3.18.1 dependencies
      • Aerospike Tools 3.18.1 now requires Python version 2.7.
      • Aerospike Tools 3.18.1 now requires Java version 1.8 or newer.

    Improvements

    • Enterprise Only
      • [AER-6099] - (ACL) Allow security module to exchange SMD in a cluster where security is not enabled on all nodes.

    Bug Fixes

    • Enterprise & Community
      • [AER-6093] - (CDT) Get or remove by rank map operation with return type key or value returning nil element will access uninitialized memory.
      • [AER-6094] - (CDT) Get or remove by key-list ordered map operation with return type index, where key-list elements are not in map returns incomplete response.
    • Enterprise Only
      • [AER-6104] - (KVS) For index-type flash, index allocation errors may cause crash.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart.

    Known Issues

  • 4.5.2.5
    Release Date: July 31, 2019
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • Aerospike Tools version 3.18.1 dependencies
      • Aerospike Tools 3.18.1 now requires Python version 2.7.
      • Aerospike Tools 3.18.1 now requires Java version 1.8 or newer.

    Improvements

    • Enterprise Only
      • [AER-6088] - (LDAP) Added support for LDAPS.

    Bug Fixes

    • Enterprise & Community
      • [AER-6086] - (CDT) Single result operations returning boolean are not translated correctly to integer.
      • [AER-6087] - (CDT) List operations by rank and with return type rank can crash when specifying out of range rank as input.
    • Enterprise Only
      • [AER-6090] - (AUDIT) Batch sub-transactions' digests are not logged in the report-data-op audit trail.
      • [AER-6089] - (XDR) Race condition across multiple connections in libcurl may cause crash.

    Known Issues

  • 4.5.2.4
    Release Date: June 28, 2019
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • Aerospike Tools version 3.18.1 dependencies
      • Aerospike Tools 3.18.1 now requires Python version 2.7.
      • Aerospike Tools 3.18.1 now requires Java version 1.8 or newer.

    Improvements

    • Enterprise & Community
      • [AER-6073] - (KVS) Validate the set name (if sent) in read and delete messages.

    Bug Fixes

    • Enterprise & Community
      • [AER-6077] - (BATCH) For storage-engine memory namespaces, batch transactions unnecessarily return an error if record size exceeds 10MB.
    • Enterprise Only
      • [AER-6072] - (XDR) Crash using multi-handles in curl library when using change notification.
      • [AER-6075] - (XDR) Dynamically setting xdr context configuration items when configuration file has no xdr context causes crash.

    Known Issues

  • 4.5.2.3
    Release Date: May 31, 2019
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • Aerospike Tools version 3.18.1 dependencies
      • Aerospike Tools 3.18.1 now requires Python version 2.7.
      • Aerospike Tools 3.18.1 now requires Java version 1.8 or newer.

    Improvements

    • Enterprise & Community
      • [AER-6057] - (STORAGE) Added storage context configuration item disable-odsync to prevent setting O_DSYNC flag on storage devices.

    Bug Fixes

    • Enterprise & Community
      • [AER-6068] - (LOGGING) Concurrent SIGHUPs to roll log files may race and double close a log sink file descriptor.
    • Enterprise Only
      • [AER-6069] - (LDAP) Minor memory leak during LDAP login process.

    Known Issues

  • 4.5.2.2
    Release Date: April 26, 2019
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • Aerospike Tools version 3.18.1 dependencies
      • Aerospike Tools 3.18.1 now requires Python version 2.7.
      • Aerospike Tools 3.18.1 now requires Java version 1.8 or newer.

    Bug Fixes

    • Enterprise & Community
      • [AER-6050] - (CDT) Extremely large unsorted lists or maps that require sorting within an operation may overflow the stack.
    • Enterprise Only
      • [AER-6048] - (STORAGE) Namespaces that use compression and have different write-block-size values may overwrite memory.
      • [AER-6049] - (XDR) May unnecessarily assert when a fresh socket goes bad while shipping to http destinations.

    Known Issues

  • 4.5.2.1
    Release Date: April 1, 2019
    • Relaxed Strong Consistency Reads. (Enterprise Only)
    • Bin Shipping per Data Center dc-ship-bins. (Enterprise Only)
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • Aerospike Tools version 3.18.1 dependencies
      • Aerospike Tools 3.18.1 now requires Python version 2.7.
      • Aerospike Tools 3.18.1 now requires Java version 1.8 or newer.

    New Features

    • Enterprise Only
      • [AER-6037] - (KVS) Added relaxed read modes for strong-consistency namespaces.
      • [AER-6025] - (XDR) Added datacenter context configuration item dc-ship-bins to allow bin shipping per DC.

    Improvements

    • Enterprise & Community
      • [AER-6013] - (INFO) Added client address to log lines for scan starts, and to job monitor info where appropriate.
      • [AER-6024] - (INFO) Made service context configuration item info-threads dynamic.
      • [AER-6030] - (INFO) Added socket timeout to log lines for scan starts, and to job monitor info where appropriate.
      • [AER-6023] - (STORAGE) Optimized hot key writes when record updates do not change stored size.
    • Enterprise Only
      • [AER-6033] - (KVS) For strong-consistency namespaces, improved replica write retransmission in various rare situations.
      • [AER-6026] - (BALANCE) Removed info command 'protect-roster-set' - protection is now automatic.

    Bug Fixes

    • Enterprise Only
      • [AER-6035] - (BALANCE) For AP namespaces with prefer-uniform-balance true, there may be redundant migrations after shutting down a quiesced node.
      • [AER-6041] - (XDR) Honor compression threshold configuration for http destination.

    Known Issues

  • 4.5.1.21
    Release Date: March 19, 2020
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • Aerospike Tools version 3.18.1 dependencies
      • Aerospike Tools 3.18.1 now requires Python version 2.7.
      • Aerospike Tools 3.18.1 now requires Java version 1.8 or newer.

    Bug Fixes

    • Enterprise & Community
      • [AER-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive.
      • [AER-6194] - (GEO) For namespaces with data-in-memory true, GeoJSON particles allocate up to 2KB more than the reported particle size.
    • Enterprise Only
      • [AER-6195] - (MIGRATION) Theoretical race condition may cause delta migration to complete without sending all records.

    Known Issues

  • 4.5.1.20
    Release Date: February 28, 2020
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • Aerospike Tools version 3.18.1 dependencies
      • Aerospike Tools 3.18.1 now requires Python version 2.7.
      • Aerospike Tools 3.18.1 now requires Java version 1.8 or newer.

    Bug Fixes

    • Enterprise & Community
      • [AER-6189] - (UDF) List creation via UDF does not initialize list flags, which may inadvertently flag the list as ordered.
    • Enterprise Only
      • [AER-6178] - (STORAGE) Setting storage context configuration item compression dynamically for storage-engine memory namespaces is not prevented and may cause a crash.

    Known Issues

  • 4.5.1.19
    Release Date: January 21, 2020
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • Aerospike Tools version 3.18.1 dependencies
      • Aerospike Tools 3.18.1 now requires Python version 2.7.
      • Aerospike Tools 3.18.1 now requires Java version 1.8 or newer.

    Bug Fixes

    • Enterprise & Community
      • [AER-6179] - (KVS) When upgrading from version earlier than 4.5.1, pre-existing eviction depth is not used during startup.

    Known Issues

  • 4.5.1.18
    Release Date: January 15, 2020
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • Aerospike Tools version 3.18.1 dependencies
      • Aerospike Tools 3.18.1 now requires Python version 2.7.
      • Aerospike Tools 3.18.1 now requires Java version 1.8 or newer.

    Bug Fixes

    • Enterprise Only
      • [AER-6175] - (BALANCE) For strong-consistency namespaces, appeal subsystem leaks memory, and has rare races which may cause crash or deadlock.

    Known Issues

  • 4.5.1.17
    Release Date: December 16, 2019
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • Aerospike Tools version 3.18.1 dependencies
      • Aerospike Tools 3.18.1 now requires Python version 2.7.
      • Aerospike Tools 3.18.1 now requires Java version 1.8 or newer.

    Bug Fixes

    • Enterprise Only
      • [AER-6169] - (AUDIT) Reporting of login failures erroneously requires setting security log/syslog context configuration item report-authentication true.

    Known Issues

  • 4.5.1.16
    Release Date: December 6, 2019
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • Aerospike Tools version 3.18.1 dependencies
      • Aerospike Tools 3.18.1 now requires Python version 2.7.
      • Aerospike Tools 3.18.1 now requires Java version 1.8 or newer.

    Bug Fixes

    • Enterprise & Community
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure.

    Known Issues

  • 4.5.1.15
    Release Date: November 14, 2019
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • Aerospike Tools version 3.18.1 dependencies
      • Aerospike Tools 3.18.1 now requires Python version 2.7.
      • Aerospike Tools 3.18.1 now requires Java version 1.8 or newer.

    Bug Fixes

    • Enterprise & Community
      • [AER-6146] - (KVS) With debug-allocations enabled, a memory accounting array will eventually overflow and cause a crash.
    • Enterprise Only
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections.

    Known Issues

  • 4.5.1.13
    Release Date: November 1, 2019
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • Aerospike Tools version 3.18.1 dependencies
      • Aerospike Tools 3.18.1 now requires Python version 2.7.
      • Aerospike Tools 3.18.1 now requires Java version 1.8 or newer.

    Bug Fixes

    • Enterprise & Community
      • [AER-6132] - (CDT) Get or remove by key for map with element count 1 and result type index or rank returns a list instead of a scalar.

    Known Issues

  • 4.5.1.12
    Release Date: October 3, 2019
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • Aerospike Tools version 3.18.1 dependencies
      • Aerospike Tools 3.18.1 now requires Python version 2.7.
      • Aerospike Tools 3.18.1 now requires Java version 1.8 or newer.

    Bug Fixes

    • Enterprise & Community
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate.

    Known Issues

  • 4.5.1.11
    Release Date: August 28, 2019
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • Aerospike Tools version 3.18.1 dependencies
      • Aerospike Tools 3.18.1 now requires Python version 2.7.
      • Aerospike Tools 3.18.1 now requires Java version 1.8 or newer.

    Improvements

    • Enterprise Only
      • [AER-6099] - (ACL) Allow security module to exchange SMD in a cluster where security is not enabled on all nodes.

    Bug Fixes

    • Enterprise & Community
      • [AER-6093] - (CDT) Get or remove by rank map operation with return type key or value returning nil element will access uninitialized memory.
      • [AER-6094] - (CDT) Get or remove by key-list ordered map operation with return type index, where key-list elements are not in map returns incomplete response.
    • Enterprise Only
      • [AER-6104] - (KVS) For index-type flash, index allocation errors may cause crash.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart.

    Known Issues

  • 4.5.1.10
    Release Date: July 31, 2019
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • Aerospike Tools version 3.18.1 dependencies
      • Aerospike Tools 3.18.1 now requires Python version 2.7.
      • Aerospike Tools 3.18.1 now requires Java version 1.8 or newer.

    Improvements

    • Enterprise Only
      • [AER-6088] - (LDAP) Added support for LDAPS.

    Bug Fixes

    • Enterprise & Community
      • [AER-6086] - (CDT) Single result operations returning boolean are not translated correctly to integer.
      • [AER-6087] - (CDT) List operations by rank and with return type rank can crash when specifying out of range rank as input.
    • Enterprise Only
      • [AER-6090] - (AUDIT) Batch sub-transactions' digests are not logged in the report-data-op audit trail.
      • [AER-6089] - (XDR) Race condition across multiple connections in libcurl may cause crash.

    Known Issues

  • 4.5.1.9
    Release Date: June 28, 2019
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • Aerospike Tools version 3.18.1 dependencies
      • Aerospike Tools 3.18.1 now requires Python version 2.7.
      • Aerospike Tools 3.18.1 now requires Java version 1.8 or newer.

    Improvements

    • Enterprise & Community
      • [AER-6073] - (KVS) Validate the set name (if sent) in read and delete messages.

    Bug Fixes

    • Enterprise & Community
      • [AER-6077] - (BATCH) For storage-engine memory namespaces, batch transactions unnecessarily return an error if record size exceeds 10MB.
    • Enterprise Only
      • [AER-6072] - (XDR) Crash using multi-handles in curl library when using change notification.
      • [AER-6075] - (XDR) Dynamically setting xdr context configuration items when configuration file has no xdr context causes crash.

    Known Issues

  • 4.5.1.8
    Release Date: May 31, 2019
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • Aerospike Tools version 3.18.1 dependencies
      • Aerospike Tools 3.18.1 now requires Python version 2.7.
      • Aerospike Tools 3.18.1 now requires Java version 1.8 or newer.

    Improvements

    • Enterprise & Community
      • [AER-6057] - (STORAGE) Added storage context configuration item disable-odsync to prevent setting O_DSYNC flag on storage devices.

    Bug Fixes

    • Enterprise & Community
      • [AER-6068] - (LOGGING) Concurrent SIGHUPs to roll log files may race and double close a log sink file descriptor.
    • Enterprise Only
      • [AER-6069] - (LDAP) Minor memory leak during LDAP login process.

    Known Issues

  • 4.5.1.7
    Release Date: April 26, 2019
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • Aerospike Tools version 3.18.1 dependencies
      • Aerospike Tools 3.18.1 now requires Python version 2.7.
      • Aerospike Tools 3.18.1 now requires Java version 1.8 or newer.

    Bug Fixes

    • Enterprise & Community
      • [AER-6050] - (CDT) Extremely large unsorted lists or maps that require sorting within an operation may overflow the stack.
    • Enterprise Only
      • [AER-6048] - (STORAGE) Namespaces that use compression and have different write-block-size values may overwrite memory.
      • [AER-6049] - (XDR) May unnecessarily assert when a fresh socket goes bad while shipping to http destinations.

    Known Issues

  • 4.5.1.6
    Release Date: March 25, 2019
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • Aerospike Tools version 3.18.1 dependencies
      • Aerospike Tools 3.18.1 now requires Python version 2.7.
      • Aerospike Tools 3.18.1 now requires Java version 1.8 or newer.

    Improvements

    • Enterprise Only
      • [AER-6036] - (TLS) Do not block a TLS socket for a full second, for example when non-TLS connections are attempted.

    Bug Fixes

    • Enterprise & Community
      • [AER-6028] - (KVS) Proxied requests are failed by destination node before its first rebalance instead of returned to sender for retry.
      • [AER-6034] - (SCAN) Scans with a socket timeout of zero (meaning never time out) inadvertently time out.
      • [AER-6029] - (FABRIC) Load balance counter for send threads does not decrement correctly in certain rare circumstances.
    • Enterprise Only
      • [AER-6031] - (KVS) For strong-consistency namespaces, replications may unnecessarily assert when they are concurrent with non-durable deletes.

    Known Issues

  • 4.5.1.5
    Release Date: February 26, 2019
    • System Metadata (SMD) Protocol Change
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
    • Aerospike Tools version 3.18.1 dependencies
      • Aerospike Tools 3.18.1 now requires Python version 2.7.
      • Aerospike Tools 3.18.1 now requires Java version 1.8 or newer.

    Improvements

    • Enterprise & Community
      • [AER-6000] - (KVS) Redesigned namespace supervisor (nsup), featuring expiration and eviction without transactions, and per-namespace control.
      • [AER-6011] - (KVS) Deprecated namespace context configuration items 'max-ttl' and 'cold-start-evict-ttl'.
      • [AER-5999] - (SMD) Redesigned SMD layer to be more efficient and robust.
      • [AER-6008] - (LOGGING) Eliminated excessive error logging to /tmp/aerospike-console when rolling log file.
      • [AER-5980] - (STATS) Added detailed 'from_proxy' stats, for transactions proxied from another node.
    • Enterprise Only
      • [AER-6010] - (TLS) Changed three 'info' level logs that appeared with every new TLS connection to 'detail' level.
      • [AER-6004] - (MIGRATION) Support strong-consistency clusters with a mixture of storage-engine values ('memory' and 'device').

    Known Issues

    Updates

  • 4.5.0.24
    Release Date: March 19, 2020
    • The CentOS 7 RPM packages are built with OpenSSL 1.0.2, which is the current shipping package version. If you are running on an older version of CentOS 7 which uses OpenSSL 1.0.1, the installation will not succeed due to a dependency mismatch. Please resolve by either updating CentOS patches (security or whole release) to a point where OpenSSL 1.0.2 is used, or install OpenSSL 1.0.2 using "yum update openssl".
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash.
      • [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive.
      • [AER-6194] - (GEO) For namespaces with data-in-memory true, GeoJSON particles allocate up to 2KB more than the reported particle size.
    • Enterprise Only
      • [AER-6195] - (MIGRATION) Theoretical race condition may cause delta migration to complete without sending all records.

    Known Issues

  • 4.5.0.23
    Release Date: February 28, 2020
    • The CentOS 7 RPM packages are built with OpenSSL 1.0.2, which is the current shipping package version. If you are running on an older version of CentOS 7 which uses OpenSSL 1.0.1, the installation will not succeed due to a dependency mismatch. Please resolve by either updating CentOS patches (security or whole release) to a point where OpenSSL 1.0.2 is used, or install OpenSSL 1.0.2 using "yum update openssl".
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-6189] - (UDF) List creation via UDF does not initialize list flags, which may inadvertently flag the list as ordered.
    • Enterprise Only
      • [AER-6178] - (STORAGE) Setting storage context configuration item compression dynamically for storage-engine memory namespaces is not prevented and may cause a crash.

    Known Issues

  • 4.5.0.22
    Release Date: January 15, 2020
    • The CentOS 7 RPM packages are built with OpenSSL 1.0.2, which is the current shipping package version. If you are running on an older version of CentOS 7 which uses OpenSSL 1.0.1, the installation will not succeed due to a dependency mismatch. Please resolve by either updating CentOS patches (security or whole release) to a point where OpenSSL 1.0.2 is used, or install OpenSSL 1.0.2 using "yum update openssl".
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise Only
      • [AER-6175] - (BALANCE) For strong-consistency namespaces, appeal subsystem leaks memory, and has rare races which may cause crash or deadlock.

    Known Issues

  • 4.5.0.21
    Release Date: December 16, 2019
    • The CentOS 7 RPM packages are built with OpenSSL 1.0.2, which is the current shipping package version. If you are running on an older version of CentOS 7 which uses OpenSSL 1.0.1, the installation will not succeed due to a dependency mismatch. Please resolve by either updating CentOS patches (security or whole release) to a point where OpenSSL 1.0.2 is used, or install OpenSSL 1.0.2 using "yum update openssl".
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise Only
      • [AER-6169] - (AUDIT) Reporting of login failures erroneously requires setting security log/syslog context configuration item report-authentication true.

    Known Issues

  • 4.5.0.20
    Release Date: December 6, 2019
    • The CentOS 7 RPM packages are built with OpenSSL 1.0.2, which is the current shipping package version. If you are running on an older version of CentOS 7 which uses OpenSSL 1.0.1, the installation will not succeed due to a dependency mismatch. Please resolve by either updating CentOS patches (security or whole release) to a point where OpenSSL 1.0.2 is used, or install OpenSSL 1.0.2 using "yum update openssl".
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure.

    Known Issues

  • 4.5.0.19
    Release Date: November 14, 2019
    • The CentOS 7 RPM packages are built with OpenSSL 1.0.2, which is the current shipping package version. If you are running on an older version of CentOS 7 which uses OpenSSL 1.0.1, the installation will not succeed due to a dependency mismatch. Please resolve by either updating CentOS patches (security or whole release) to a point where OpenSSL 1.0.2 is used, or install OpenSSL 1.0.2 using "yum update openssl".
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-6146] - (KVS) With debug-allocations enabled, a memory accounting array will eventually overflow and cause a crash.
    • Enterprise Only
      • [AER-6133] - (TLS) Rotation not supported for elliptic curve private keys and certificates or for password-protected private keys.
      • [AER-6151] - (TLS) Updated certificates not promptly adopted for all intra-cluster connections.

    Known Issues

  • 4.5.0.17
    Release Date: November 1, 2019
    • The CentOS 7 RPM packages are built with OpenSSL 1.0.2, which is the current shipping package version. If you are running on an older version of CentOS 7 which uses OpenSSL 1.0.1, the installation will not succeed due to a dependency mismatch. Please resolve by either updating CentOS patches (security or whole release) to a point where OpenSSL 1.0.2 is used, or install OpenSSL 1.0.2 using "yum update openssl".
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-6132] - (CDT) Get or remove by key for map with element count 1 and result type index or rank returns a list instead of a scalar.

    Known Issues

  • 4.5.0.16
    Release Date: October 3, 2019
    • The CentOS 7 RPM packages are built with OpenSSL 1.0.2, which is the current shipping package version. If you are running on an older version of CentOS 7 which uses OpenSSL 1.0.1, the installation will not succeed due to a dependency mismatch. Please resolve by either updating CentOS patches (security or whole release) to a point where OpenSSL 1.0.2 is used, or install OpenSSL 1.0.2 using "yum update openssl".
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-6129] - (KVS) Predicate filter memory leak observed when using list/map iterate.

    Known Issues

  • 4.5.0.15
    Release Date: August 28, 2019
    • The CentOS 7 RPM packages are built with OpenSSL 1.0.2, which is the current shipping package version. If you are running on an older version of CentOS 7 which uses OpenSSL 1.0.1, the installation will not succeed due to a dependency mismatch. Please resolve by either updating CentOS patches (security or whole release) to a point where OpenSSL 1.0.2 is used, or install OpenSSL 1.0.2 using "yum update openssl".
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Improvements

    • Enterprise Only
      • [AER-6099] - (ACL) Allow security module to exchange SMD in a cluster where security is not enabled on all nodes.

    Bug Fixes

    • Enterprise & Community
      • [AER-6093] - (CDT) Get or remove by rank map operation with return type key or value returning nil element will access uninitialized memory.
      • [AER-6094] - (CDT) Get or remove by key-list ordered map operation with return type index, where key-list elements are not in map returns incomplete response.
    • Enterprise Only
      • [AER-6104] - (KVS) For index-type flash, index allocation errors may cause crash.
      • [AER-6098] - (XDR) XDR may ship older versions of records following a restart.

    Known Issues

  • 4.5.0.14
    Release Date: July 31, 2019
    • The CentOS 7 RPM packages are built with OpenSSL 1.0.2, which is the current shipping package version. If you are running on an older version of CentOS 7 which uses OpenSSL 1.0.1, the installation will not succeed due to a dependency mismatch. Please resolve by either updating CentOS patches (security or whole release) to a point where OpenSSL 1.0.2 is used, or install OpenSSL 1.0.2 using "yum update openssl".
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Improvements

    • Enterprise Only
      • [AER-6088] - (LDAP) Added support for LDAPS.

    Bug Fixes

    • Enterprise & Community
      • [AER-6086] - (CDT) Single result operations returning boolean are not translated correctly to integer.
      • [AER-6087] - (CDT) List operations by rank and with return type rank can crash when specifying out of range rank as input.
    • Enterprise Only
      • [AER-6090] - (AUDIT) Batch sub-transactions' digests are not logged in the report-data-op audit trail.
      • [AER-6089] - (XDR) Race condition across multiple connections in libcurl may cause crash.

    Known Issues

  • 4.5.0.13
    Release Date: June 28, 2019
    • The CentOS 7 RPM packages are built with OpenSSL 1.0.2, which is the current shipping package version. If you are running on an older version of CentOS 7 which uses OpenSSL 1.0.1, the installation will not succeed due to a dependency mismatch. Please resolve by either updating CentOS patches (security or whole release) to a point where OpenSSL 1.0.2 is used, or install OpenSSL 1.0.2 using "yum update openssl".
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Improvements

    • Enterprise & Community
      • [AER-6073] - (KVS) Validate the set name (if sent) in read and delete messages.

    Bug Fixes

    • Enterprise & Community
      • [AER-6077] - (BATCH) For storage-engine memory namespaces, batch transactions unnecessarily return an error if record size exceeds 10MB.
    • Enterprise Only
      • [AER-6072] - (XDR) Crash using multi-handles in curl library when using change notification.
      • [AER-6075] - (XDR) Dynamically setting xdr context configuration items when configuration file has no xdr context causes crash.

    Known Issues

  • 4.5.0.12
    Release Date: May 31, 2019
    • The CentOS 7 RPM packages are built with OpenSSL 1.0.2, which is the current shipping package version. If you are running on an older version of CentOS 7 which uses OpenSSL 1.0.1, the installation will not succeed due to a dependency mismatch. Please resolve by either updating CentOS patches (security or whole release) to a point where OpenSSL 1.0.2 is used, or install OpenSSL 1.0.2 using "yum update openssl".
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Improvements

    • Enterprise & Community
      • [AER-6057] - (STORAGE) Added storage context configuration item disable-odsync to prevent setting O_DSYNC flag on storage devices.
      • [AER-6008] - (LOGGING) Eliminated excessive error logging to /tmp/aerospike-console when rolling log file.

    Bug Fixes

    • Enterprise & Community
      • [AER-6068] - (LOGGING) Concurrent SIGHUPs to roll log files may race and double close a log sink file descriptor.
    • Enterprise Only
      • [AER-6069] - (LDAP) Minor memory leak during LDAP login process.

    Known Issues

  • 4.5.0.11
    Release Date: April 26, 2019
    • The CentOS 7 RPM packages are built with OpenSSL 1.0.2, which is the current shipping package version. If you are running on an older version of CentOS 7 which uses OpenSSL 1.0.1, the installation will not succeed due to a dependency mismatch. Please resolve by either updating CentOS patches (security or whole release) to a point where OpenSSL 1.0.2 is used, or install OpenSSL 1.0.2 using "yum update openssl".
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-6050] - (CDT) Extremely large unsorted lists or maps that require sorting within an operation may overflow the stack.
    • Enterprise Only
      • [AER-6048] - (STORAGE) Namespaces that use compression and have different write-block-size values may overwrite memory.
      • [AER-6049] - (XDR) May unnecessarily assert when a fresh socket goes bad while shipping to http destinations.

    Known Issues

  • 4.5.0.10
    Release Date: April 5, 2019
    • The CentOS 7 RPM packages are built with OpenSSL 1.0.2, which is the current shipping package version. If you are running on an older version of CentOS 7 which uses OpenSSL 1.0.1, the installation will not succeed due to a dependency mismatch. Please resolve by either updating CentOS patches (security or whole release) to a point where OpenSSL 1.0.2 is used, or install OpenSSL 1.0.2 using "yum update openssl".
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Improvements

    • Enterprise & Community
      • [AER-6042] - (KVS) When service context configuration item 'prole-extra-ttl' is set, delete all eligible expired non-master replicas during each nsup cycle.

    Known Issues

  • 4.5.0.9
    Release Date: March 25, 2019
    • The CentOS 7 RPM packages are built with OpenSSL 1.0.2, which is the current shipping package version. If you are running on an older version of CentOS 7 which uses OpenSSL 1.0.1, the installation will not succeed due to a dependency mismatch. Please resolve by either updating CentOS patches (security or whole release) to a point where OpenSSL 1.0.2 is used, or install OpenSSL 1.0.2 using "yum update openssl".
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Improvements

    • Enterprise Only
      • [AER-6036] - (TLS) Do not block a TLS socket for a full second, for example when non-TLS connections are attempted.

    Bug Fixes

    • Enterprise & Community
      • [AER-6028] - (KVS) Proxied requests are failed by destination node before its first rebalance instead of returned to sender for retry.
      • [AER-6034] - (SCAN) Scans with a socket timeout of zero (meaning never time out) inadvertently time out.
      • [AER-6029] - (FABRIC) Load balance counter for send threads does not decrement correctly in certain rare circumstances.
    • Enterprise Only
      • [AER-6031] - (KVS) For strong-consistency namespaces, replications may unnecessarily assert when they are concurrent with non-durable deletes.

    Known Issues

  • 4.5.0.8
    Release Date: February 26, 2019
    • The CentOS 7 RPM packages are built with OpenSSL 1.0.2, which is the current shipping package version. If you are running on an older version of CentOS 7 which uses OpenSSL 1.0.1, the installation will not succeed due to a dependency mismatch. Please resolve by either updating CentOS patches (security or whole release) to a point where OpenSSL 1.0.2 is used, or install OpenSSL 1.0.2 using "yum update openssl".
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise Only
      • [AER-6022] - (KVS) May unnecessarily assert when fast restarting after a shutdown that left a ref-counted record (for reduce, e.g. scan) that was deleted.

    Known Issues

  • 4.5.0.7
    Release Date: February 25, 2019
    • The CentOS 7 RPM packages are built with OpenSSL 1.0.2, which is the current shipping package version. If you are running on an older version of CentOS 7 which uses OpenSSL 1.0.1, the installation will not succeed due to a dependency mismatch. Please resolve by either updating CentOS patches (security or whole release) to a point where OpenSSL 1.0.2 is used, or install OpenSSL 1.0.2 using "yum update openssl".
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Improvements

    • Enterprise Only
      • [AER-6014] - (XDR) Ensure info commands that get XDR stats are non-blocking.

    Bug Fixes

    • Enterprise & Community
      • [AER-6020] - (NETWORK) The heartbeat context configuration item mesh-seed-address-port is limited to 64 characters when using DNS.
    • Enterprise Only
      • [AER-5746] - (XDR) Time lag value can be incorrect. Supplements fix done in 4.1.0.1.

    Known Issues

  • 4.5.0.6
    Release Date: February 20, 2019
    • The CentOS 7 RPM packages are built with OpenSSL 1.0.2, which is the current shipping package version. If you are running on an older version of CentOS 7 which uses OpenSSL 1.0.1, the installation will not succeed due to a dependency mismatch. Please resolve by either updating CentOS patches (security or whole release) to a point where OpenSSL 1.0.2 is used, or install OpenSSL 1.0.2 using "yum update openssl".
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Improvements

    Bug Fixes

    • Enterprise Only
      • [AER-6012] - (MIGRATION) For AP namespaces, there may be redundant migrations when quiescing multiple nodes at once and later shutting them down one by one.
      • [AER-6016] - (XDR) May miss records when a destination cluster is down, especially if there is only one destination.

    Known Issues

  • 4.5.0.5
    Release Date: January 25, 2019
    • The CentOS 7 RPM packages are built with OpenSSL 1.0.2, which is the current shipping package version. If you are running on an older version of CentOS 7 which uses OpenSSL 1.0.1, the installation will not succeed due to a dependency mismatch. Please resolve by either updating CentOS patches (security or whole release) to a point where OpenSSL 1.0.2 is used, or install OpenSSL 1.0.2 using "yum update openssl".
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-6007] - (CDT) Map operations that add items and use both the DO_PARTIAL and NO_FAIL error policies may overwrite memory.
    • Enterprise Only
      • [AER-6006] - (KVS) For strong-consistency namespaces, re-replications may unnecessarily assert in very rare situations.
      • [AER-6002] - (BALANCE) For strong-consistency namespaces with replication-factor 1, removing node(s) from roster may cause crash.
      • [AER-5984] - (TLS) Small memory leak when logging a new TLS connection.

    Known Issues

  • 4.5.0.4
    Release Date: January 10, 2019
    • The CentOS 7 RPM packages are built with OpenSSL 1.0.2, which is the current shipping package version. If you are running on an older version of CentOS 7 which uses OpenSSL 1.0.1, the installation will not succeed due to a dependency mismatch. Please resolve by either updating CentOS patches (security or whole release) to a point where OpenSSL 1.0.2 is used, or install OpenSSL 1.0.2 using "yum update openssl".
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-5996] - (KVS) Regression - service context configuration item auto-pin values cpu and numa do not pin service threads to CPUs.
      • [AER-5997] - (MIGRATION) Rare race condition causes migrate_signals_remaining stat to underflow.
    • Enterprise Only

    Known Issues

  • 4.5.0.3
    Release Date: December 17, 2018
    • The CentOS 7 RPM packages are built with OpenSSL 1.0.2, which is the current shipping package version. If you are running on an older version of CentOS 7 which uses OpenSSL 1.0.1, the installation will not succeed due to a dependency mismatch. Please resolve by either updating CentOS patches (security or whole release) to a point where OpenSSL 1.0.2 is used, or install OpenSSL 1.0.2 using "yum update openssl".
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-5985] - (STORAGE) Improper handling of dropped keys when replicating or migrating records.
    • Enterprise Only
      • [AER-5990] - (INFO) Service context configuration item migrate-fill-delay does not take time units when set dynamically.

    Known Issues

  • 4.5.0.2
    Release Date: December 13, 2018
    • The CentOS 7 RPM packages are built with OpenSSL 1.0.2, which is the current shipping package version. If you are running on an older version of CentOS 7 which uses OpenSSL 1.0.1, the installation will not succeed due to a dependency mismatch. Please resolve by either updating CentOS patches (security or whole release) to a point where OpenSSL 1.0.2 is used, or install OpenSSL 1.0.2 using "yum update openssl".
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise Only
      • [AER-5982] - (XDR) Some records may get stuck in flight to http server when the load stops.

    Known Issues

  • 4.5.0.1
    Release Date: December 12, 2018
    • The CentOS 7 RPM packages are built with OpenSSL 1.0.2, which is the current shipping package version. If you are running on an older version of CentOS 7 which uses OpenSSL 1.0.1, the installation will not succeed due to a dependency mismatch. Please resolve by either updating CentOS patches (security or whole release) to a point where OpenSSL 1.0.2 is used, or install OpenSSL 1.0.2 using "yum update openssl".
    • Index in Persistent Memory is an Enterprise Edition only feature requiring an additional license. Existing Aerospike Enterprise customers should contact their account representative for a trial license.
    • Support for Record Storage Compression (Enterprise Only).
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    New Features

    • Enterprise Only
      • [AER-5967] - (KVS) Added value pmem for namespace context configuration item index-type, to use persistent memory for primary index.
      • [AER-5968] - (STORAGE) Added storage context configuration items compression and compression-level, to enable data compression on storage devices.

    Improvements

    • Enterprise Only
      • [AER-5962] - (STORAGE) Added storage context configuration item encryption to specify the algorithm used by encryption at rest.

    Bug Fixes

    • Enterprise & Community
      • [AER-5966] - (CDT) Memory leak in non-recursive deeply nested list/map comparisons.
    • Enterprise Only
      • [AER-5971] - (XDR) The dc-security-config-file item is not shown in get-dc-config info.
      • [AER-5973] - (XDR) Dissociating a DC during active link down session does not abort link down thread.

    Known Issues

  • 4.4.0.15
    Release Date: April 26, 2019
    • The CentOS 7 RPM packages are built with OpenSSL 1.0.2, which is the current shipping package version. If you are running on an older version of CentOS 7 which uses OpenSSL 1.0.1, the installation will not succeed due to a dependency mismatch. Please resolve by either updating CentOS patches (security or whole release) to a point where OpenSSL 1.0.2 is used, or install OpenSSL 1.0.2 using "yum update openssl".
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-6050] - (CDT) Extremely large unsorted lists or maps that require sorting within an operation may overflow the stack.
    • Enterprise Only
      • [AER-6049] - (XDR) May unnecessarily assert when a fresh socket goes bad while shipping to http destinations.

    Known Issues

  • 4.4.0.14
    Release Date: March 25, 2019
    • The CentOS 7 RPM packages are built with OpenSSL 1.0.2, which is the current shipping package version. If you are running on an older version of CentOS 7 which uses OpenSSL 1.0.1, the installation will not succeed due to a dependency mismatch. Please resolve by either updating CentOS patches (security or whole release) to a point where OpenSSL 1.0.2 is used, or install OpenSSL 1.0.2 using "yum update openssl".
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Improvements

    • Enterprise Only
      • [AER-6036] - (TLS) Do not block a TLS socket for a full second, for example when non-TLS connections are attempted.

    Bug Fixes

    • Enterprise & Community
      • [AER-6028] - (KVS) Proxied requests are failed by destination node before its first rebalance instead of returned to sender for retry.
      • [AER-6034] - (SCAN) Scans with a socket timeout of zero (meaning never time out) inadvertently time out.
      • [AER-6029] - (FABRIC) Load balance counter for send threads does not decrement correctly in certain rare circumstances.
    • Enterprise Only
      • [AER-6031] - (KVS) For strong-consistency namespaces, replications may unnecessarily assert when they are concurrent with non-durable deletes.

    Known Issues

  • 4.4.0.13
    Release Date: February 26, 2019
    • The CentOS 7 RPM packages are built with OpenSSL 1.0.2, which is the current shipping package version. If you are running on an older version of CentOS 7 which uses OpenSSL 1.0.1, the installation will not succeed due to a dependency mismatch. Please resolve by either updating CentOS patches (security or whole release) to a point where OpenSSL 1.0.2 is used, or install OpenSSL 1.0.2 using "yum update openssl".
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Improvements

    • Enterprise Only
      • [AER-6014] - (XDR) Ensure info commands that get XDR stats are non-blocking.

    Bug Fixes

    • Enterprise & Community
      • [AER-6020] - (NETWORK) The heartbeat context configuration item mesh-seed-address-port is limited to 64 characters when using DNS.
    • Enterprise Only
      • [AER-6022] - (KVS) May unnecessarily assert when fast restarting after a shutdown that left a ref-counted record (for reduce, e.g. scan) that was deleted.
      • [AER-5746] - (XDR) Time lag value can be incorrect. Supplements fix done in 4.1.0.1.

    Known Issues

  • 4.4.0.11
    Release Date: February 20, 2019
    • The CentOS 7 RPM packages are built with OpenSSL 1.0.2, which is the current shipping package version. If you are running on an older version of CentOS 7 which uses OpenSSL 1.0.1, the installation will not succeed due to a dependency mismatch. Please resolve by either updating CentOS patches (security or whole release) to a point where OpenSSL 1.0.2 is used, or install OpenSSL 1.0.2 using "yum update openssl".
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Improvements

    Bug Fixes

    • Enterprise Only
      • [AER-6012] - (MIGRATION) For AP namespaces, there may be redundant migrations when quiescing multiple nodes at once and later shutting them down one by one.
      • [AER-6016] - (XDR) May miss records when a destination cluster is down, especially if there is only one destination.

    Known Issues

  • 4.4.0.10
    Release Date: January 25, 2019
    • The CentOS 7 RPM packages are built with OpenSSL 1.0.2, which is the current shipping package version. If you are running on an older version of CentOS 7 which uses OpenSSL 1.0.1, the installation will not succeed due to a dependency mismatch. Please resolve by either updating CentOS patches (security or whole release) to a point where OpenSSL 1.0.2 is used, or install OpenSSL 1.0.2 using "yum update openssl".
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-6007] - (CDT) Map operations that add items and use both the DO_PARTIAL and NO_FAIL error policies may overwrite memory.
    • Enterprise Only
      • [AER-6006] - (KVS) For strong-consistency namespaces, re-replications may unnecessarily assert in very rare situations.
      • [AER-6002] - (BALANCE) For strong-consistency namespaces with replication-factor 1, removing node(s) from roster may cause crash.
      • [AER-5984] - (TLS) Small memory leak when logging a new TLS connection.

    Known Issues

  • 4.4.0.9
    Release Date: January 10, 2019
    • The CentOS 7 RPM packages are built with OpenSSL 1.0.2, which is the current shipping package version. If you are running on an older version of CentOS 7 which uses OpenSSL 1.0.1, the installation will not succeed due to a dependency mismatch. Please resolve by either updating CentOS patches (security or whole release) to a point where OpenSSL 1.0.2 is used, or install OpenSSL 1.0.2 using "yum update openssl".
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-5996] - (KVS) Regression - service context configuration item auto-pin values cpu and numa do not pin service threads to CPUs.
      • [AER-5997] - (MIGRATION) Rare race condition causes migrate_signals_remaining stat to underflow.
    • Enterprise Only

    Known Issues

  • 4.4.0.8
    Release Date: December 17, 2018
    • The CentOS 7 RPM packages are built with OpenSSL 1.0.2, which is the current shipping package version. If you are running on an older version of CentOS 7 which uses OpenSSL 1.0.1, the installation will not succeed due to a dependency mismatch. Please resolve by either updating CentOS patches (security or whole release) to a point where OpenSSL 1.0.2 is used, or install OpenSSL 1.0.2 using "yum update openssl".
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-5985] - (STORAGE) Improper handling of dropped keys when replicating or migrating records.
    • Enterprise Only
      • [AER-5990] - (INFO) Service context configuration item migrate-fill-delay does not take time units when set dynamically.

    Known Issues

  • 4.4.0.7
    Release Date: December 13, 2018
    • The CentOS 7 RPM packages are built with OpenSSL 1.0.2, which is the current shipping package version. If you are running on an older version of CentOS 7 which uses OpenSSL 1.0.1, the installation will not succeed due to a dependency mismatch. Please resolve by either updating CentOS patches (security or whole release) to a point where OpenSSL 1.0.2 is used, or install OpenSSL 1.0.2 using "yum update openssl".
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise Only
      • [AER-5982] - (XDR) Some records may get stuck in flight to http server when the load stops.

    Known Issues

  • 4.4.0.6
    Release Date: December 5, 2018
    • The CentOS 7 RPM packages are built with OpenSSL 1.0.2, which is the current shipping package version. If you are running on an older version of CentOS 7 which uses OpenSSL 1.0.1, the installation will not succeed due to a dependency mismatch. Please resolve by either updating CentOS patches (security or whole release) to a point where OpenSSL 1.0.2 is used, or install OpenSSL 1.0.2 using "yum update openssl".
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise Only
      • [AER-5981] - (ACL) Login command failure (e.g. incorrect password) may eventually result in assertion or double free.

    Known Issues

  • 4.4.0.5
    Release Date: November 28, 2018
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Improvements

    • Enterprise & Community
      • [AER-5975] - (SMD) Ignore unknown JSON items within SMD items.

    Bug Fixes

    • Enterprise Only
      • [AER-5976] - (XDR) If using any HTTP version 2 option with 'change notification', bug in curl library can cause crash.
      • [AER-5974] - (BALANCE) For strong-consistency namespaces, rare cluster split scenario after expanding roster can trigger assertion.

    Known Issues

  • 4.4.0.4
    Release Date: November 19, 2018
    • change notification is an Enterprise Edition only feature requiring an additional license. Existing Aerospike Enterprise customers should contact their account representative for a trial license.
    • Qualified el6 package on Amazon Linux.
    • Qualified el7 package on Amazon Linux 2.
    • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    New Features

    • Enterprise Only
      • [AER-5960] - (XDR) Added xdr context configuration item enable-change-notification to export records to non-Aerospike destinations.

    Improvements

    • Enterprise & Community
      • [AER-5961] - (BATCH) Removed support for batch-direct mode.
      • [AER-5964] - (CLUSTERING) Resolve DNS asynchronously to avoid blocking heartbeat.
      • [AER-5955] - (INFO) Made truncate command safer against accidents when issuing the command via asinfo tool.
      • [AER-5963] - (INFO) Removed deprecated (client-only) 'replicas-prole' command.
      • [AER-5946] - (GEO) Raised geo2dsphere-within context configuration item max-cells limit to 256, and made min-level and max-level dynamic.
    • Enterprise Only
      • [AER-5957] - (INFO) Added (client-only) 'rebalance-generation' and 'rack-ids' commands.
      • [AER-5907] - (XDR) Added separate counter xdr_ship_destination_permanent_error for errors that are not relogged.

    Bug Fixes

    • Enterprise & Community
      • [AER-5867] - (GEO) Predicate expression list value iteration fails for geoJson variables.
      • [AER-5983] - (STATS) Transaction histograms for large requests (e.g., large writes and batches) may show inaccurate '...-start' time slice.
    • Enterprise Only
      • [AER-5965] - (CDT) For storage-engine device namespaces with data-in-memory true, ordered map with 2+ elements causes crash on restart.
      • [AER-5916] - (XDR) Reported time lag is inaccurate in digestlog overflow situations.
      • [AER-5948] - (XDR) Log warnings use incorrect names for several TLS context configuration items.

    Known Issues

    Updates

  • 4.3.1.14
    Release Date: April 26, 2019
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-6050] - (CDT) Extremely large unsorted lists or maps that require sorting within an operation may overflow the stack.

    Known Issues

  • 4.3.1.13
    Release Date: March 25, 2019
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Improvements

    • Enterprise Only
      • [AER-6036] - (TLS) Do not block a TLS socket for a full second, for example when non-TLS connections are attempted.

    Bug Fixes

    • Enterprise & Community
      • [AER-6028] - (KVS) Proxied requests are failed by destination node before its first rebalance instead of returned to sender for retry.
      • [AER-6034] - (SCAN) Scans with a socket timeout of zero (meaning never time out) inadvertently time out.
      • [AER-6029] - (FABRIC) Load balance counter for send threads does not decrement correctly in certain rare circumstances.
    • Enterprise Only
      • [AER-6031] - (KVS) For strong-consistency namespaces, replications may unnecessarily assert when they are concurrent with non-durable deletes.

    Known Issues

  • 4.3.1.12
    Release Date: February 26, 2019
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise Only
      • [AER-6022] - (KVS) May unnecessarily assert when fast restarting after a shutdown that left a ref-counted record (for reduce, e.g. scan) that was deleted.
      • [AER-5746] - (XDR) Time lag value can be incorrect. Supplements fix done in 4.1.0.1.

    Known Issues

  • 4.3.1.11
    Release Date: February 20, 2019
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Improvements

    Bug Fixes

    • Enterprise Only
      • [AER-6012] - (MIGRATION) For AP namespaces, there may be redundant migrations when quiescing multiple nodes at once and later shutting them down one by one.

    Known Issues

  • 4.3.1.10
    Release Date: January 25, 2019
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-6007] - (CDT) Map operations that add items and use both the DO_PARTIAL and NO_FAIL error policies may overwrite memory.
    • Enterprise Only
      • [AER-6006] - (KVS) For strong-consistency namespaces, re-replications may unnecessarily assert in very rare situations.
      • [AER-6002] - (BALANCE) For strong-consistency namespaces with replication-factor 1, removing node(s) from roster may cause crash.
      • [AER-5984] - (TLS) Small memory leak when logging a new TLS connection.

    Known Issues

  • 4.3.1.8
    Release Date: December 17, 2018
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-5985] - (STORAGE) Improper handling of dropped keys when replicating or migrating records.
    • Enterprise Only
      • [AER-5990] - (INFO) Service context configuration item migrate-fill-delay does not take time units when set dynamically.

    Known Issues

  • 4.3.1.7
    Release Date: December 5, 2018
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise Only
      • [AER-5981] - (ACL) Login command failure (e.g. incorrect password) may eventually result in assertion or double free.

    Known Issues

  • 4.3.1.6
    Release Date: November 27, 2018
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Improvements

    • Enterprise & Community
      • [AER-5975] - (SMD) Ignore unknown JSON items within SMD items.

    Bug Fixes

    • Enterprise Only
      • [AER-5974] - (BALANCE) For strong-consistency namespaces, rare cluster split scenario after expanding roster can trigger assertion.

    Known Issues

  • 4.3.1.5
    Release Date: November 6, 2018
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Improvements

    • Enterprise & Community
      • [AER-5950] - (STORAGE) When defrag load is extremely low, periodically flush defrag buffer in order to free source write blocks.

    Bug Fixes

    • Enterprise & Community
      • [AER-5956] - (INFO) cluster-stable command fails for 100 or more nodes, or with parameter 'ignore-migrations=false'.
    • Enterprise Only
      • [AER-5958] - (INFO) For strong-consistency namespaces, racks command will return incorrect values if all roster nodes are not present.

    Known Issues

  • 4.3.1.4
    Release Date: October 22, 2018
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Improvements

    • Enterprise Only
      • [AER-5951] - (BALANCE) Added info command protect-roster-set to make roster changes that remove nodes safer in various scenarios.
      • [AER-5952] - (BALANCE) For strong-consistency namespaces, improved availability in extremely rare cluster split scenario.

    Bug Fixes

    • Enterprise & Community
      • [AER-5953] - (GEO) Possible memory overwrite in extremely rare cases.

    Known Issues

  • 4.3.1.3
    Release Date: October 18, 2018

    New Features

    • Enterprise & Community
      • [AER-5944] - (STORAGE) Added storage context configuration item read-page-cache to disable O_DIRECT and O_DSYNC on selected read operations.
      • [AER-5945] - (CDT) Added INF and WILDCARD types for use in map and list comparators.
    • Enterprise Only
      • [AER-5292] - (BALANCE) Added info command quiesce to inform a node to prepare to be removed from the cluster.
      • [AER-5875] - (TLS) Added support for password-protected TLS keys.
      • [AER-5931] - (MIGRATION) Added service context configuration item migrate-fill-delay to optionally delay "fill" migrations to temporary replicas.

    Improvements

    • Enterprise & Community
      • [AER-5915] - (KVS) Moved configuration item transaction-pending-limit from service context to namespace context.
      • [AER-5938] - (SINDEX) Secondary indexes now use SMD union merge instead of majority merge.
      • [AER-5935] - (INFO) Added service context configuration item enable-health-check and info commands health-outliers and health-stats.
      • [AER-5921] - (NETWORK) Cap the listen() backlog at 512 instead of 128 connections.
      • [AER-5947] - (STORAGE) Replace storage context configuration item 'fsync-max-sec' with direct-files.
      • [AER-5920] - (UDF) System Lua code is now loaded directly from C strings.
      • [AER-5939] - (LOGGING) Use ticker warnings and detail messages to reduce log noise when failing to allocate index arena stages.

    Bug Fixes

    • Enterprise & Community
      • [AER-5933] - (CDT) Map/List get-by-value, get-by-value-list comparison may be incorrect for maps/lists of different lengths.
      • [AER-5930] - (CLUSTERING) Crash in service-list exchange when out of file descriptors.
      • [AER-5943] - (GENERIC) JEMalloc may leak memory when threads exit their run functions.
    • Enterprise Only
      • [AER-5932] - (INFO) Some TLS configuration items returned by get-config contain underscores instead of hyphens.
      • [AER-5925] - (TLS) The TLS context configuration item protocols is parsed incorrectly when multiple values are specified.

    Known Issues

    Updates

  • 4.3.0.10
    Release Date: October 3, 2018
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise Only
      • [AER-5941] - (BALANCE) AP cluster with namespace not on all nodes with prefer-uniform-balance true may access invalid memory.
      • [AER-5942] - (BALANCE) Using prefer-uniform-balance true in a cluster whose node count is a power of two will access uninitialized memory.

    Known Issues

  • 4.3.0.9
    Release Date: October 1, 2018
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-5940] - (INFO) Crash when meminfo file reports zero physical memory.

    Known Issues

  • 4.3.0.7
    Release Date: August 30, 2018
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-5928] - (KVS) In non data-in-memory namespaces, read operation mixed with 'replace' write causes write to update instead.
    • Enterprise Only
      • [AER-5929] - (XDR) XDR (sometimes silently) drops bins with name length of 15 characters.

    Known Issues

  • 4.3.0.6
    Release Date: August 24, 2018
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise Only
      • [AER-5924] - (BALANCE) May assert rebalancing to cluster containing non-roster node with unique rack-id.

    Known Issues

  • 4.3.0.4
    Release Date: August 17, 2018
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-5917] - (KVS) In non data-in-memory namespaces, cannot add a stored key to an existing record.
    • Enterprise Only
      • [AER-5919] - (KVS) Fast restart may assert if previous shutdown occurred during a rebalance.

    Known Issues

  • 4.3.0.3
    Release Date: August 13, 2018
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise Only
      • [AER-5913] - (KVS) Re-replication during clock-skew stop-writes leaves record stuck in 're-replicating' state, blocking migrations.

    Known Issues

  • 4.3.0.2
    Release Date: August 1, 2018
    • All Flash (Enterprise only, requires new feature key).
    • Ability to choose uniform partition balance over minimal migrations during cluster changes (Enterprise only).
    • Relative range operations for CDTs, and NO_FAIL and DO_PARTIAL CDT error policies.
    • When upgrading the Aerospike Server, from a version prior to 4.3 with replication-factor 2 or greater along with the use of the rack-aware feature in AP namespaces, refer to the special considerations knowledge base article for details. (Enterprise Only)
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    New Features

    • Enterprise & Community
      • [AER-5891] - (CDT) Added CDT relative range operations.
      • [AER-5892] - (CDT) Added NO_FAIL and DO_PARTIAL CDT error policies.
    • Enterprise Only
      • [AER-5901] - (KVS) Added namespace context configuration item index-type with value 'flash' to use block storage devices for primary index.
      • [AER-5900],[AER-4714] - (BALANCE) Added namespace context configuration item prefer-uniform-balance to choose uniform partition balance over minimal migrations.

    Improvements

    • Enterprise & Community
      • [AER-5881] - (KVS) Setting service context configuration item nsup-period to zero deactivates runtime expiration/eviction.
      • [AER-5882] - (KVS) Setting service context configuration item object-size-hist-period to zero deactivates object size histogram population.
      • [AER-5885] - (KVS) Replaced service context configuration item nsup-startup-evict with namespace context item disable-cold-start-eviction.
      • [AER-5886] - (KVS) Added namespace context configuration item disable-nsup to disable runtime expiration/eviction for the namespace.
      • [AER-5906] - (KVS) Removed default value of namespace context configuration item memory-size.
      • [AER-5909] - (KVS) Improved efficiency of pushing to head of queue.
      • [AER-5883] - (SINDEX) Setting service context configuration item sindex-gc-period to zero deactivates secondary index garbage collection.
      • [AER-5897] - (INFO) Added 'size' parameter and 'ignore-migrations' option to cluster-stable info command, and made 'namespace' parameter optional.
      • [AER-4969] - (INFO) Expose various device-specific metrics through the info protocol.
      • [AER-5893] - (NETWORK) Increased the character limit on heartbeat context configuration item mesh-seed-address-port from 64 to 255.
      • [AER-5902] - (STORAGE) Allow storage files to have shadow files.
      • [AER-5905] - (STORAGE) Removed default value of storage context configuration item filesize.
    • Enterprise Only
      • [AER-5541] - (KVS) Added storage context configuration item serialize-tomb-raider to allow serialization of different namespaces' tomb raids.
      • [AER-5884] - (KVS) Setting namespace context configuration item tomb-raider-period to zero deactivates tomb raider.

    Bug Fixes

    • Enterprise & Community
      • [AER-5904] - (CLUSTERING) Clock skew may be falsely reported briefly when a node joins a cluster where the logical clock is ahead of the physical clock.
      • [AER-5911] - (FABRIC) Race condition caused by recycling duplicate resolution fabric message for replica write/ping.
      • [AER-5894] - (STORAGE) IO on shadow device fails if its minimum IO size exceeds that of its primary device.
    • Enterprise Only
      • [AER-5912] - (CLUSTERING) Slow drives may prevent initial cluster formation under strong consistency when roster is missing.
      • [AER-5888] - (BALANCE) Changing rack IDs with replication factor 3 or more may result in suboptimal master selection.
      • [AER-5880] - (XDR) Dynamic changes to datacenter context configuration items dc-connections and dc-connections-idle-ms are applied to all DCs.

    Known Issues

    Updates

  • 4.2.0.10
    Release Date: August 10, 2018
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Improvements

    • Enterprise & Community
      • [AER-5909] - (KVS) Improved efficiency of pushing to head of queue.

    Bug Fixes

    • Enterprise & Community
      • [AER-5911] - (FABRIC) Race condition caused by recycling duplicate resolution fabric message for replica write/ping.
    • Enterprise Only
      • [AER-5913] - (KVS) Re-replication during clock-skew stop-writes leaves record stuck in 're-replicating' state, blocking migrations.
      • [AER-5912] - (CLUSTERING) Slow drives may prevent initial cluster formation under strong consistency when roster is missing.

    Known Issues

  • 4.2.0.7
    Release Date: July 27, 2018
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-5908] - (UDF) Memory leak running UDFs in single-bin namespaces. Introduced in 3.15.0.1.
    • Enterprise Only
      • [AER-5903] - (STORAGE) Zero padding at end of write blocks may decrypt to accidentally yield good record magic.

    Known Issues

  • 4.2.0.5
    Release Date: July 18, 2018
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-5898] - (CLUSTERING) A node may still rebalance after abandoning a clustering attempt.
    • Enterprise Only
      • [AER-5899] - (KVS) Fast restart may unnecessarily assert on finding deleted but not yet freed records.
      • [AER-5844] - (XDR) In a single DC scenario, some records may not be shipped if link goes down while processing failed node. Introduced in 3.10.1.
      • [AER-5890] - (XDR) Window shipper can get stuck if the link to all DCs goes down. Introduced in 3.10.0.2.

    Known Issues

  • 4.2.0.4
    Release Date: June 25, 2018
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-5889] - (KVS) Memory leak replicating or migrating records bigger than 1 MB, or ordered maps/lists near that size, in non data-in-memory namespaces.

    Known Issues

  • 4.2.0.3
    Release Date: June 8, 2018
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.

    Bug Fixes

    • Enterprise & Community
      • [AER-5879] - (FABRIC) Records a few bytes less than 1M, or bigger than 1M, will cause a crash in fabric.

    Known Issues

  • 4.2.0.2
    Release Date: May 31, 2018

    New Features

    • Enterprise & Community
      • New Distro - Ubuntu 18.04

    Improvements

    • Enterprise & Community
      • [AER-5862] - (KVS) Namespace context configuration item partition-tree-sprigs minimum and default values increased to 256.
      • [AER-5863] - (KVS) Deprecated namespace context configuration item partition-tree-locks.
      • [AER-5850] - (STORAGE) Maximum write-block-size increased to 8MB.
      • [AER-5858] - (STORAGE) Increased maximum devices per namespace to 128.
      • [AER-5859] - (STORAGE) Significantly reduced record storage overhead.
      • [AER-5878] - (FABRIC) Removed message pool lock contention.
      • [AER-5864] - (LOGGING) Improved signal context dumped in log on assertions and crashes.
      • [AER-5866] - (STATS) Improved object size histograms, deprecated namespace context configuration item obj-size-hist-max, added service context configuration item object-size-hist-period.
    • Enterprise Only
      • [AER-5860] - (KVS) Much faster fast restart.
      • [AER-5861] - (STORAGE) Made device configuration order independent across fast restart.

    Bug Fixes

    • Enterprise & Community
      • [AER-5756] - (KVS) auto-pin unnecessarily fails assertion on servers with 72 TX network queues and i40e driver.
      • [AER-5869] - (INFO) Info reports duplicate heartbeat.mesh-seed-address-port.
      • [AER-5876] - (STATS) When 'read' and 'batch-sub', or 'udf' and 'udf-sub' histograms are both enabled, the histograms are incorrect.

    Known Issues

    Updates

  • 4.1.0.6
    Release Date: September 6, 2018
    • When upgrading the Aerospike server, from a version prior to 3.14, please follow the upgrade and protocol-switching PREREQUISITES for 3.13.0.11 documentation for Upgrade to 3.13.

    Bug Fixes

    • Enterprise & Community
      • [AER-5934] - (CLUSTERING) When upgrading directly from 3.13 to 4.0 or 4.1, device header artifact is mistakenly interpreted as a strong consistency regime.
    • Enterprise Only
      • [AER-5913] - (KVS) Re-replication during clock-skew stop-writes leaves record stuck in 're-replicating' state, blocking migrations.

    Known Issues

  • 4.1.0.5
    Release Date: August 6, 2018
    • DO NOT UPGRADE from 3.13 (or earlier) directly to this release. Instead, upgrade to 4.1.0.6, 4.2 or 4.3.
    • If you have already upgraded directly from 3.13 to this version, upgrade to 4.1.0.6 prior to any further upgrade.
    • After the upgrade to 4.1.0.6 depending on the client’s versions being utilized it may be necessary to restart them (including XDR).

    Improvements

    • Enterprise & Community
      • [AER-5909] - (KVS) Improved efficiency of pushing to head of queue.

    Bug Fixes

    • Enterprise & Community
      • [AER-5911] - (FABRIC) Race condition caused by recycling duplicate resolution fabric message for replica write/ping.

    Known Issues

  • 4.1.0.4
    Release Date: July 27, 2018
    • DO NOT UPGRADE from 3.13 (or earlier) directly to this release. Instead, upgrade to 4.1.0.6, 4.2 or 4.3.
    • If you have already upgraded directly from 3.13 to this version, upgrade to 4.1.0.6 prior to any further upgrade.
    • After the upgrade to 4.1.0.6 depending on the client’s versions being utilized it may be necessary to restart them (including XDR).

    Bug Fixes

    • Enterprise & Community
      • [AER-5908] - (UDF) Memory leak running UDFs in single-bin namespaces.
    • Enterprise Only
      • [AER-5903] - (STORAGE) Zero padding at end of write blocks may decrypt to accidentally yield good record magic.

    Known Issues

  • 4.1.0.2
    Release Date: June 8, 2018
    • DO NOT UPGRADE from 3.13 (or earlier) directly to this release. Instead, upgrade to 4.1.0.6, 4.2 or 4.3.
    • If you have already upgraded directly from 3.13 to this version, upgrade to 4.1.0.6 prior to any further upgrade.
    • After the upgrade to 4.1.0.6 depending on the client’s versions being utilized it may be necessary to restart them (including XDR).

    Bug Fixes

    • Enterprise & Community
      • [AER-5879] - (FABRIC) Records a few bytes less than 1M, or bigger than 1M, will cause a crash in fabric.

    Known Issues

  • 4.1.0.1
    Release Date: May 10, 2018
    • DO NOT UPGRADE from 3.13 (or earlier) directly to this release. Instead, upgrade to 4.1.0.6, 4.2 or 4.3.
    • If you have already upgraded directly from 3.13 to this version, upgrade to 4.1.0.6 prior to any further upgrade.
    • After the upgrade to 4.1.0.6 depending on the client’s versions being utilized it may be necessary to restart them (including XDR).
    • Introduction of LDAP support
      • LDAP is an Enterprise Edition only feature requiring an additional license. Existing Aerospike Enterprise customers should contact their account representative for a trial license.
      • Configuring LDAP
    • Encryption at rest is an Enterprise Edition only feature now requiring an additional license. Existing Aerospike Enterprise customers should contact their account representative for a trial license. Customers who have previously implemented encryption at rest should contact their account representative or Aerospike Support prior to starting an upgrade.
    • Strong Consistency is an Enterprise Edition only feature requiring an additional license. Existing Aerospike Enterprise customers should contact their account representative for a trial license.

    New Features

    • Enterprise & Community
      • New Distro - Debian 9
    • Enterprise Only
      • [AER-5848] - (LDAP) Added support for external authentication via LDAP.
      • [AER-5483] - (XDR) Added a command to force an XDR destination cluster into window shipping.

    Improvements

    • Enterprise & Community
      • [AER-5837] - (FABRIC) Do not retransmit fabric message which is still in fabric's message queue.
      • [AER-5857] - (FABRIC) Reduced memory consumption and number of system calls in fabric layer.
      • [AER-5845] - (BATCH) Batch-index responses are now non-blocking.
      • [AER-5841] - (LOGGING) Include client IP address in log line for failed info responses.
    • Enterprise Only
      • [AER-5856] - (BALANCE) For strong consistency, reduced pessimism in certain cases when regime is skipped.

    Bug Fixes

    • Enterprise & Community
      • [AER-5853] - (CDT) Add_items with replace policy on unordered maps fails unless all items are replaced.
      • [AER-5855] - (CDT) Some single-result operations on ordered CDTs return an error code instead of an empty result.
    • Enterprise Only
      • [AER-5746] - (XDR) Time lag value can be incorrect.
      • [AER-5839] - (XDR) Node without XDR section configured crashes when other nodes in the cluster are configured.

    Known Issues

    Updates

  • 4.0.0.6
    Release Date: September 6, 2018
    • Strong Consistency an Enterprise Edition only feature requiring an additional license. Existing Aerospike Enterprise customers should contact their account representative for a trial license.
    • When upgrading the Aerospike server, from a version prior to 3.14, please follow the upgrade and protocol-switching PREREQUISITES for 3.13.0.11 documentation for Upgrade to 3.13.

    Improvements

    • Enterprise & Community
      • [AER-5909] - (KVS) Improved efficiency of pushing to head of queue.

    Bug Fixes

    • Enterprise & Community
      • [AER-5934] - (CLUSTERING) When upgrading directly from 3.13 to 4.0 or 4.1, device header artifact is mistakenly interpreted as a strong consistency regime.
      • [AER-5911] - (FABRIC) Race condition caused by recycling duplicate resolution fabric message for replica write/ping.
    • Enterprise Only
      • [AER-5913] - (KVS) Re-replication during clock-skew stop-writes leaves record stuck in 're-replicating' state, blocking migrations.

    Known Issues

  • 4.0.0.5
    Release Date: April 20, 2018
    • DO NOT UPGRADE from 3.13 (or earlier) directly to this release. Instead, upgrade to 4.0.0.6, 4.1.0.6, 4.2 or 4.3.
    • If you have already upgraded directly from 3.13 to this version, upgrade to 4.0.0.6 prior to any further upgrade.
    • After the upgrade to 4.0.0.6 depending on the client’s versions being utilized it may be necessary to restart them (including XDR).
    • Strong Consistency an Enterprise Edition only feature requiring an additional license. Existing Aerospike Enterprise customers should contact their account representative for a trial license.

    Bug Fixes

    • Enterprise & Community
      • [AER-5838] - (KVS) Omitting a closing brace ( } ) in a namespace context configuration eventually causes a crash.
    • Enterprise Only
      • [AER-5847] - (STORAGE) Ensure decrypt caller fails magic check if decrypt fails magic check. Introduced in 3.15.1.3

    Known Issues

  • 4.0.0.4
    Release Date: March 21, 2018
    • DO NOT UPGRADE from 3.13 (or earlier) directly to this release. Instead, upgrade to 4.0.0.6, 4.1.0.6, 4.2 or 4.3.
    • If you have already upgraded directly from 3.13 to this version, upgrade to 4.0.0.6 prior to any further upgrade.
    • After the upgrade to 4.0.0.6 depending on the client’s versions being utilized it may be necessary to restart them (including XDR).
    • Strong Consistency an Enterprise Edition only feature requiring an additional license. Existing Aerospike Enterprise customers should contact their account representative for a trial license.

    Improvements

    • Enterprise & Community
      • [AER-5823] - (STORAGE) Prevent duplicate 'file' or 'device' storage-engine context configuration items.
      • [AER-5825] - (STATS) Renamed 'cluster_clock_skew' statistic to cluster_clock_skew_ms.

    Bug Fixes

    • Enterprise & Community
      • [AER-5831] - (KVS) Proxied transactions that time out shortly after insertion into hash may double free fabric message.
      • [AER-5829] - (CDT) List-by-value-list operation on ordered list may crash with certain value parameters. Introduced in 3.16.0.1
      • [AER-5830] - (CDT) By-list-value-list, by-map-key-list, by-map-value-list operations may crash if parameter lists contain duplicate elements. Introduced in 3.16.0.1
    • Enterprise Only
      • [AER-5828] - (KVS) Memory leak in fabric when sending replication confirmation message (in strong-consistency mode).
      • [AER-5822] - (STORAGE) At startup, if device is encrypted, check of device header's strong consistency flag is bypassed.
      • [AER-5835] - (STORAGE) Post-write queue is not thread-safe in commit-to-device mode.
      • [AER-5824] - (XDR) Crash when bin shipping is enabled and a record contains only zero-length blobs and/or strings.

    Known Issues

  • 4.0.0.1
    Release Date: March 7, 2018
    • DO NOT UPGRADE from 3.13 (or earlier) directly to this release. Instead, upgrade to 4.0.0.6, 4.1.0.6, 4.2 or 4.3.
    • If you have already upgraded directly from 3.13 to this version, upgrade to 4.0.0.6 prior to any further upgrade.
    • After the upgrade to 4.0.0.6 depending on the client’s versions being utilized it may be necessary to restart them (including XDR).
    • Introduction of Strong Consistency

    New Features

    • Enterprise Only
      • [AER-5816] - (KVS) Introduced strong consistency, enabled by namespace context configuration item strong-consistency.
      • [AER-5815] - (DEPLOYMENT) Introduced feature keys for select enterprise features.
      • [AER-5818] - (CLUSTERING) Rack-aware is now an enterprise feature.
    • Community Only
      • [AER-5817] - (DEPLOYMENT) Introduced maximum cluster size of 8, introduced maximum of 2 namespaces.

    Known Issues

    Updates