Aerospike Server EE Release Notes

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

    Bug Fixes

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

    Known Issues

    • If you use equality secondary index queries that return a small number of records, you may see a latency increase in server releases 6.0-6.2. The inline-short-queries configuration option provides a partial fix in server 6.3, and a more advanced fix is scheduled for server 6.4.
    • If your secondary index query only returns 0 records or 1 record, meaning that it is acting as a unique index, you should consider converting such a query to a get/exists operation by creating a self-managed reverse index (lookup table).
    • Spark Connector version 3.5 starts using batch writes when possible, a feature which was introduced in Aerospike server version 6.0. Consult the Spark Connector rate limiting documentation before you upgrade the server. Pay attention to throttling write throughput, and use Spark Connector 3.5.5 or later, which fixes throttling behavior to conform to the aerospike.transaction.rate.
    • Known Issues: Server

    Updates

  • 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

  • 3.16.0.6
    Release Date: March 2, 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.
    • The deprecated Large Data Types (LDT) feature has been removed.
      • LDT usage continues to be supported through server versions up to 3.14.1.10.
      • If you are still using LDTs, refer to this article prior to upgrading.

    Bug Fixes

    • Enterprise & Community
      • [AER-5812] - (CDT) Incorrect result returned for unordered list operations with 'add-unique' policy (similar to AER-5808).
      • [AER-5819] - (CDT) Adding element to partially indexed ordered list can result in element being out of order. Refer to Aerospike CDT Validation Tool.
    • Enterprise Only
      • [AER-5813] - (KVS) Incorrect error handling when durable delete fails storage write operation.

    Known Issues

  • 3.16.0.4
    Release Date: February 28, 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.
    • The deprecated Large Data Types (LDT) feature has been removed.
      • LDT usage continues to be supported through server versions up to 3.14.1.10.
      • If you are still using LDTs, refer to this article prior to upgrading.

    Bug Fixes

    • Enterprise & Community
      • [AER-5807] - (CDT) Ordered list with duplicate elements can return incorrect element list for certain operations.
      • [AER-5808] - (CDT) Incorrect result returned for list operations with 'add-unique' policy.
      • [AER-5809] - (CDT) Operation to get list of values from ordered list by specifying list of values may crash.
      • [AER-5811] - (CDT) List operation using 'inverted' flag may access un-indexed element.
      • [AER-5810] - (STATS) Log ticker over-reports free system memory.

    Known Issues

  • 3.16.0.1
    Release Date: February 21, 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.
    • The deprecated Large Data Types (LDT) feature has been removed.
      • LDT usage continues to be supported through server versions up to 3.14.1.10.
      • If you are still using LDTs, refer to this article prior to upgrading.

    New Features

    • Enterprise & Community
      • [AER-5798] - (CDT) Added 'ordered list' CDT.
      • [AER-5799] - (CDT) Introduced 'inverted' flag for map and list operations.

    Improvements

    • Enterprise & Community
      • [AER-5782] - (KVS) Set evict_ttl to zero if there was no threshold breach during the last nsup cycle.
      • [AER-5785] - (KVS) With write-commit-level 'master', or for nsup deletes, do not wait for replica write ack.
      • [AER-5802] - (KVS) Increased maximum allowed value of post-write-queue from 2048 to 4096.
      • [AER-5672] - (CLUSTERING) Added service context configuration item node-id to optionally specify a node's ID.
      • [AER-5789] - (CLUSTERING) Improved cluster convergence times.
      • [AER-5795] - (SCAN) Increased scan-threads limit from 32 to 128.
      • [AER-5797] - (MIGRATION) Increased maximum allowed value for migrate-max-num-incoming to 256.
      • [AER-5776] - (STORAGE) Don't free a defragmented write block before all data evacuated from it has been flushed.
      • [AER-5803] - (CDT) Changed error behavior for remove-element operations on non-existent bins.
      • [AER-5775] - (STATS) Added a log ticker line for XDR write & delete stats, a line for special errors, and contexts for a few special logs.
    • Enterprise Only
      • [AER-5787] - (XDR) Added xdr context configuration item xdr-min-digestlog-free-pct to stop regular writes when the XDR digest log is too full.

    Bug Fixes

    • Enterprise & Community
      • [AER-5792] - (CLUSTERING) Potential deadlock when handling racks info command, introduced in 3.15.0.1.
      • [AER-5806] - (CDT) Adding an empty map to an empty bin may crash the server.

    Known Issues

    Updates

  • 3.15.1.4
    Release Date: January 3, 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.
    • The deprecated Large Data Types(LDT) feature has been removed.
      • LDT usage continues to be supported through server versions up to 3.14.1.10.
      • If you are still using LDTs, refer to this article prior to upgrading.

    Bug Fixes

    • Enterprise & Community
      • [AER-5778] - (CLUSTERING) Heartbeat events can be delivered out of order.
    • Enterprise Only
      • [AER-5774] - (XDR) Dynamically reducing xdr-read-threads may crash asd.
      • [AER-5777] - (XDR) Very large digest log files are not reclaimed if full.

    Known Issues

  • 3.15.1.3
    Release Date: December 18, 2017
    • 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.
    • The deprecated Large Data Types(LDT) feature has been removed.
      • LDT usage continues to be supported through server versions up to 3.14.1.10.
      • If you are still using LDTs, refer to this article prior to upgrading.

    New Features

    • Enterprise Only
      • [AER-5768] - (STORAGE) Encryption at rest.

    Improvements

    • Enterprise & Community
      • [AER-5760] - (KVS) Reintroduce disable-write-dup-res at namespace level. Introduced in version 3.15.0.1
      • [AER-5759] - (KVS) During cold start, read in write-block-size chunks -- speeds up cold start for SSDs.
      • [AER-5758] - (KVS) Don't retry proxies - rely on client retries.
      • [AER-4911] - (KVS) Complete sanity check of client messages.
      • [AER-5731] - (CLUSTERING) Added 'fresh-partitions' count to the rebalanced log line.
      • [AER-5738] - (INFO) Rename repl-factor to replication-factor in namespace get-config output, add effective_replication_factor to namespace info output.
      • [AER-5747] - (SCAN) Include client address in warnings about errors sending scan responses.
    • Enterprise Only
      • [AER-5743] - (KVS) Make use of persisted index on restarting data-in-memory namespaces.
      • [AER-5771] - (XDR) Include digest in XDR debug log for temporary write errors.

    Bug Fixes

    • Enterprise Only
      • [AER-5763] - (XDR) Unsafe to configure more than 32 datacenters.
      • [AER-5772] - (XDR) Remote datacenter cannot be seeded dynamically using ipv6 address. Introduced in version 3.11.0

    Known Issues

    Updates

  • 3.15.0.2
    Release Date: November 6, 2017
    • 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.
    • The deprecated Large Data Types(LDT) feature has been removed.
      • LDT usage continues to be supported through server versions up to 3.14.1.10.
      • If you are still using LDTs, refer to this article prior to upgrading.
    • Introduced Intra-cluster Transport Layer Security(TLS) and changes to the TLS configuration structure, in the Enterprise Edition only,

    Improvements

    • Enterprise & Community
      • [AER-5755] - (UDF) Allow Lua cache to freely increase to its limit as needed.

    Bug Fixes

    • Enterprise & Community
      • [AER-5734] - (KVS) Possible race when reading and writing vmap hash concurrently.

    Known Issues

  • 3.15.0.1
    Release Date: October 3, 2017
    • 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.
    • The deprecated Large Data Types(LDT) feature has been removed.
      • LDT usage continues to be supported through server versions up to 3.14.1.10.
      • If you are still using LDTs, refer to this article prior to upgrading.
    • Introduced Intra-cluster Transport Layer Security(TLS) and changes to the TLS configuration structure, in the Enterprise Edition only,

    New Features

    • Enterprise & Community
      • [AER-5149] - (CDT) Added new list operation to increment a list element's value.
      • [AER-5702] - (QUERY) Support returning keys/digests without bins in query.
    • Enterprise Only
      • [AER-5704] - (TLS) Intra-cluster TLS support for heartbeat and fabric connections.

    Improvements

    • Enterprise & Community
      • [AER-5555] - (LDT) LDT code removal.
      • [AER-5717] - (KVS) Deprecated 'write-duplicate-resolution-disable', 'respond-client-on-master-completion', and 'transaction-repeatable-read' service context configuration items.
      • [AER-5160] - (KVS) Check stop-writes threshold independently of nsup cycle.
      • [AER-2381] - (INFO) Tip and tip-clear acknowledge success or failure.
      • [AER-5729] - (SCAN) Include client address in the warning about receiving a scan message with an unrecognized set.
      • [AER-5711] - (NETWORK) Increased the limit on the number of interfaces to 500.
      • [AER-5724] - (NETWORK) get-config returns mesh-seed-address-port exactly as configured.
      • [AER-5716] - (MIGRATION) Retry emigrations after waiting a second, instead of immediately, when rejected by remote node.
    • Enterprise Only
      • [AER-5644] - (TLS) Check the tls-name against the certificate on server start-up.
      • [AER-5712] - (TLS) Server dynamically reloads certificates.
      • [AER-5722] - (NETWORK) Do not use IPv6 if enabled in kernel but disabled via sysctl.

    Bug Fixes

    • Enterprise & Community
      • [AER-5728] - (SMD) Some SMD module initializations do not ensure all existing SMD data is restored.
      • [AER-5703] - (MIGRATION) Race condition where migrations can complete successfully when they should not.
      • [AER-5419] - (UDF) UDFs in single-bin namespaces have various problems.

    Known Issues

    Updates

  • 3.14.1.10
    Release Date: April 26, 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.
    • This is the last release that will include the deprecated LDT feature.

    Improvements

    • Enterprise & Community
      • [AER-5711] - (NETWORK) Increased the limit on the number of interfaces to 500.

    Known Issues

  • 3.14.1.9
    Release Date: March 15, 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.

    Improvements

    • Enterprise Only
      • [AER-5826] - (CLUSTERING) Support rolling upgrades to later versions in which fabric TLS is enabled.

    Bug Fixes

    • Enterprise & Community
      • [AER-5831] - (KVS) Proxied transactions that time out shortly after insertion into hash may double free fabric message.
    • Enterprise Only
      • [AER-5813] - (KVS) Incorrect error handling when durable delete fails storage write operation.

    Known Issues

  • 3.14.1.8
    Release Date: February 13, 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-5804] - (LDT) With LDTs disabled, LDT records from other nodes, and during warm restart, are not handled properly.

    Known Issues

  • 3.14.1.7
    Release Date: January 3, 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-5778] - (CLUSTERING) Heartbeat events can be delivered out of order.
    • Enterprise Only
      • [AER-5774] - (XDR) Dynamically reducing xdr-read-threads may crash asd.
      • [AER-5777] - (XDR) Very large digest log files are not reclaimed if full.

    Known Issues

  • 3.14.1.5
    Release Date: November 6, 2017
    • 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-5755] - (UDF) Allow Lua cache to freely increase to its limit as needed.

    Bug Fixes

    • Enterprise & Community
      • [AER-5728] - (SMD) Some SMD module initializations do not ensure all existing SMD data is restored.
      • [AER-5734] - (KVS) Possible race when reading and writing vmap hash concurrently.

    Known Issues

  • 3.14.1.4
    Release Date: September 18, 2017
    • 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-5725] - (CLUSTERING) For replication-factor 16 or more, version family array might overflow and crash.
      • [AER-5726] - (SMD) Parsing a msgpack list of buffers with missing entries will fail.
      • [AER-5727] - (CLUSTERING) Rare race may skip rebalance.

    Known Issues

  • 3.14.1.3
    Release Date: September 1, 2017
    • 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-5720] - (KVS) debug-allocations modes 'persistent' and 'all' do not allow for free cache mixing namespace arenas.
      • [AER-5721] - (CDT) Particle destructor sometimes relies on unused bins' particles being null.
    • Enterprise Only
      • [AER-5718] - (XDR) Race between destination disconnect and client put can cause crash.
      • [AER-5719] - (XDR) XDR not compatible when shipping to clusters running version 3.9 or below.

    Known Issues

  • 3.14.1.2
    Release Date: July 31, 2017
    • 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-5707] - (KVS) Memory leak during cold-start eviction.
      • [AER-5710] - (LDT) Assert fires when proxy return-to-sender handler is invoked for an LDT "ship-op".
      • [AER-5706] - (CDT) Some map ops may find unfilled index and assert after prole becomes master.
    • Enterprise Only
      • [AER-5705] - (BATCH) Batch security does not allow permissions based on set names.

    Known Issues

  • 3.14.1.1
    Release Date: July 6, 2017
    • 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.

    New Features

    • Enterprise & Community
      • [AER-5683] - (KVS) New memory subsystem with configurable allocation debugging.
      • [AER-5682] - (CLUSTERING) New info command to trigger a recluster.

    Improvements

    • Enterprise & Community
      • [AER-5699] - (SINDEX) Less aggressive secondary index garbage collection configuration default.
      • [AER-5701] - (CLUSTERING) Fewer fabric messages used to exchange services info when a node joins a cluster.
    • Enterprise Only
      • [AER-5697] - (KVS) Improved fast restart time when index arena contains lots of free elements.
      • [AER-5515] - (XDR) Made dc-use-alternate-services a dynamically configurable parameter.
      • [AER-5616] - (XDR) Non-blocking client-server TLS connections (particularly helpful for XDR using TLS).
      • [AER-5655] - (XDR) Improved XDR in low throughput situations.
      • [AER-5686] - (XDR) Made XDR set-config logging consistent with other set-config contexts.
      • [AER-5680] - (XDR) Changed names of configuration items (dc-name, nodes) returned via info command get-dc-config to be consistent.

    Bug Fixes

    • Enterprise & Community
      • [AER-3173] - (KVS) Issues setting max-write-cache config item.
      • [AER-5695] - (KVS) Misleading master-object count returned from node before initial rebalance.
      • [AER-5664] - (SINDEX) Recreating a secondary index too soon after deleting it can fail.
      • [AER-5690] - (CLUSTERING) Server may return non-empty partition ownership map to client before initial rebalance, resulting in transactions getting 'unavailable' error.
    • Enterprise Only
      • [AER-5346] - (XDR) XDR doesn't connect to configured DC when turned on.
      • [AER-5617] - (XDR) XDR does not broadcast last ship info if all DCs are INACTIVE.
      • [AER-5684] - (XDR) Failure handling in XDR can miss records when it starts with all reclaimed state.
      • [AER-5700] - (XDR) Failed node shipping may miss some records when throttled.

    Known Issues

  • 3.14.0.2
    Release Date: June 26, 2017
    • 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-5698] - (SINDEX) Records created via migrations are not added to secondary index.

    Known Issues

  • 3.14.0.1
    Release Date: June 8, 2017

    Please use release 3.14.0.2 in lieu of this version (see Known Issues).

    • 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 Only
      • [AER-5668] - (XDR) Dynamically adding/removing seed nodes from cluster in an inactive state will cause a crash.
      • [AER-5657] - (XDR) 'xdr-command:skip-outstanding' now always generates correct outstanding objects statistic.

    Known Issues

  • 3.14.0
    Release Date: June 6, 2017

    Please use release 3.14.0.2 in lieu of this version (see Known Issues).

    • 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-5658] - (KVS) Deprecated set-delete and associated functionality.
      • [AER-5593] - (SINDEX) Simplified garbage collection configuration.
      • [AER-5603] - (CLUSTERING) Disallowed setting heartbeat protocol to v2, deprecated paxos-max-cluster-size.
      • [AER-5652] - (CLUSTERING) Server now runs only paxos-protocol v5, deprecated paxos-protocol.

    Known Issues

  • 3.13.0.11
    Release Date: April 26, 2018

    3.13 is a jump-version.

    • Once on 3.13 all deployments should schedule a convenient time to dynamically switch clustering protocol.
    • The 3.13 upgrade and protocol-switching are PREREQUISITES for any future version upgrade.
    • For XDR-enabled clusters: In the unlikely case of downgrade, the XDR digest log must be deleted to avoid a crash.

    Improvements

    • Enterprise & Community
      • [AER-5711] - (NETWORK) Increased the limit on the number of interfaces to 500.

    Known Issues

  • 3.13.0.10
    Release Date: March 16, 2018

    3.13 is a jump-version.

    • Once on 3.13 all deployments should schedule a convenient time to dynamically switch clustering protocol.
    • The 3.13 upgrade and protocol-switching are PREREQUISITES for any future version upgrade.
    • For XDR-enabled clusters: In the unlikely case of downgrade, the XDR digest log must be deleted to avoid a crash.

    Improvements

    • Enterprise Only
      • [AER-5826] - (CLUSTERING) Support rolling upgrades to later versions in which fabric TLS is enabled.

    Bug Fixes

    • Enterprise & Community
      • [AER-5831] - (KVS) Proxied transactions that time out shortly after insertion into hash may double free fabric message.
    • Enterprise Only
      • [AER-5813] - (KVS) Incorrect error handling when durable delete fails storage write operation.

    Known Issues

  • 3.13.0.9
    Release Date: January 3, 2018

    3.13 is a jump-version.

    • Once on 3.13 all deployments should schedule a convenient time to dynamically switch clustering protocol.
    • The 3.13 upgrade and protocol-switching are PREREQUISITES for any future version upgrade.
    • For XDR-enabled clusters: In the unlikely case of downgrade, the XDR digest log must be deleted to avoid a crash.

    Bug Fixes

    • Enterprise & Community
      • [AER-5778] - (CLUSTERING) Heartbeat events can be delivered out of order.
    • Enterprise Only
      • [AER-5774] - (XDR) Dynamically reducing xdr-read-threads may crash asd.
      • [AER-5777] - (XDR) Very large digest log files are not reclaimed if full.

    Known Issues

  • 3.13.0.8
    Release Date: November 6, 2017

    3.13 is a jump-version.

    • Once on 3.13 all deployments should schedule a convenient time to dynamically switch clustering protocol.
    • The 3.13 upgrade and protocol-switching are PREREQUISITES for any future version upgrade.
    • For XDR-enabled clusters: In the unlikely case of downgrade, the XDR digest log must be deleted to avoid a crash.

    Improvements

    • Enterprise & Community
      • [AER-5755] - (UDF) Allow Lua cache to freely increase to its limit as needed.

    Bug Fixes

    • Enterprise & Community
      • [AER-5728] - (SMD) Some SMD module initializations do not ensure all existing SMD data is restored.
      • [AER-5734] - (KVS) Possible race when reading and writing vmap hash concurrently.

    Known Issues

  • 3.13.0.7
    Release Date: September 18, 2017

    3.13 is a jump-version.

    • Once on 3.13 all deployments should schedule a convenient time to dynamically switch clustering protocol.
    • The 3.13 upgrade and protocol-switching are PREREQUISITES for any future version upgrade.
    • For XDR-enabled clusters: In the unlikely case of downgrade, the XDR digest log must be deleted to avoid a crash.

    Bug Fixes

    • Enterprise & Community
      • [AER-5725] - (CLUSTERING) For replication-factor 16 or more, version family array might overflow and crash.
      • [AER-5726] - (SMD) Parsing a msgpack list of buffers with missing entries will fail.
      • [AER-5727] - (CLUSTERING) Rare race may skip rebalance.

    Known Issues

  • 3.13.0.6
    Release Date: September 1, 2017

    3.13 is a jump-version.

    • Once on 3.13 all deployments should schedule a convenient time to dynamically switch clustering protocol.
    • The 3.13 upgrade and protocol-switching are PREREQUISITES for any future version upgrade.
    • For XDR-enabled clusters: In the unlikely case of downgrade, the XDR digest log must be deleted to avoid a crash.

    Bug Fixes

    • Enterprise & Community
      • [AER-5721] - (CDT) Particle destructor sometimes relies on unused bins' particles being null.
    • Enterprise Only
      • [AER-5718] - (XDR) Race between destination disconnect and client put can cause crash.
      • [AER-5719] - (XDR) XDR not compatible when shipping to clusters running version 3.9 or below.

    Known Issues

  • 3.13.0.4
    Release Date: July 31, 2017

    3.13 is a jump-version.

    • Once on 3.13 all deployments should schedule a convenient time to dynamically switch clustering protocol.
    • The 3.13 upgrade and protocol-switching are PREREQUISITES for any future version upgrade.
    • For XDR-enabled clusters: In the unlikely case of downgrade, the XDR digest log must be deleted to avoid a crash.

    Improvements

    • Enterprise & Community
      • [AER-5701] - (CLUSTERING) Fewer fabric messages used to exchange services info when a node joins a cluster.

    Bug Fixes

    • Enterprise & Community
      • [AER-5707] - (KVS) Memory leak during cold-start eviction.
      • [AER-5710] - (LDT) Assert fires when proxy return-to-sender handler is invoked for an LDT "ship-op".
      • [AER-5706] - (CDT) Some map ops may find unfilled index and assert after prole becomes master.
    • Enterprise Only
      • [AER-5705] - (BATCH) Batch security does not allow permissions based on set names.

    Known Issues

  • 3.13.0.3
    Release Date: June 26, 2017

    3.13 is a jump-version.

    • Once on 3.13 all deployments should schedule a convenient time to dynamically switch clustering protocol.
    • The 3.13 upgrade and protocol-switching are PREREQUISITES for any future version upgrade.
    • For XDR-enabled clusters: In the unlikely case of downgrade, the XDR digest log must be deleted to avoid a crash.

    Bug Fixes

    • Enterprise & Community
      • [AER-5698] - (SINDEX) Records created via migrations are not added to secondary index.

    Known Issues

  • 3.13.0.2
    Release Date: June 7, 2017

    Please use release 3.13.0.3 in lieu of this version (see Known Issues).

    3.13 is a jump-version.

    • Once on 3.13 all deployments should schedule a convenient time to dynamically switch clustering protocol.
    • The 3.13 upgrade and protocol-switching are PREREQUISITES for any future version upgrade.
    • For XDR-enabled clusters: In the unlikely case of downgrade, the XDR digest log must be deleted to avoid a crash.

    Bug Fixes

    • Available before the clustering protocol switch
      • [AER-5668] - (XDR) Dynamically adding/removing seed nodes from cluster in an inactive state will cause a crash.
      • [AER-5657] - (XDR) 'xdr-command:skip-outstanding' now always generates correct outstanding objects statistic.

    Known Issues

  • 3.13.0.1
    Release Date: May 30, 2017

    Please use release 3.13.0.3 in lieu of this version (see Known Issues).

    3.13 is a jump-version.

    • Once on 3.13 all deployments should schedule a convenient time to dynamically switch clustering protocol.
    • The 3.13 upgrade and protocol-switching are PREREQUISITES for any future version upgrade.
    • For XDR-enabled clusters: In the unlikely case of downgrade, the XDR digest log must be deleted to avoid a crash.

    New Features

    • Enterprise & Community
      • [AER-3485] - (KVS) With paxos-protocol v5 enabled, support adding/removing namespaces with rolling restart.
      • [AER-4678] - (CLUSTERING) With paxos-protocol v5 enabled, enhanced clustering algorithm.

    Improvements

    • Enterprise & Community
      • [AER-5103] - (KVS) Deprecated paxos-recovery-policy.
      • [AER-5584] - (KVS) Use non-temporal pre-fetch hint for index access.
      • [AER-5590] - (KVS) Object statistics - new non-replica object; prole object more accurate during migration.
      • [AER-5597] - (KVS) Remove unnecessary in-line batch request transaction copying.
      • [AER-5636] - (KVS) Log contexts named "cf:xxx" are now renamed "xxx".
      • [AER-2750] - (SINDEX) Dropping secondary index no longer locks up write and query transactions for records in dropped sindex.
      • [AER-5571] - (SINDEX) Deprecate unused sindex statistics and command.
      • [AER-5572] - (SINDEX) Remove redundant metadata translation layer.
      • [AER-5479] - (CLUSTERING) Periodically log heartbeat clustering failures.
      • [AER-5604] - (CLUSTERING) Speed up peer list convergence when new nodes are added.
      • [AER-5480] - (FABRIC) Remove fabric backdoor which may erroneously keep cluster connected.
      • [AER-5503] - (NETWORK) No longer too many log messages if fabric/HB host is unavailable.
      • [AER-5632] - (MIGRATION) Limit migrate-max-num-incoming to 64.
      • [AER-5569] - (SMD) With paxos-protocol v5 enabled, different key & value formats and Improve consensus merge for sindex.
      • [AER-5595] - (FABRIC) With paxos-protocol v5 enabled, more compact fabric messages.
      • [AER-4831] - (CLUSTERING) With paxos-protocol v5 enabled, replicas no longer immediately dropped when adding new nodes to a cluster.
      • [AER-4875] - (CLUSTERING) With paxos-protocol v5 enabled, maintain partition versions for partially filled partitions when restarting nodes.
      • [AER-5615] - (CLUSTERING) With paxos-protocol v5 enabled, rackaware configured on a per namespace level.
    • Enterprise Only
      • [AER-5607] - (ACL) Truncate command requires data-admin privilege.
      • [AER-5473] - (XDR) Remove the backdoor to stop and resume XDR.
      • [AER-5504] - (XDR) Digest log is order independent of namespace definition in configuration file.
      • [AER-5538] - (XDR) Enhance log to include node_id on "Connection error when writing to cluster".
      • [AER-5661] - (XDR) Make the buffering delay configurable for the dlogwriter/dlogreader.

    Bug Fixes

    • Enterprise & Community
      • [AER-5618] - (KVS) Fix log line migrate-threads -> migrate-threads.
      • [AER-5624] - (KVS) Retry replica writes that failed due to cluster-key mismatch.
      • [AER-5499] - (SINDEX) Remove mem-usage value from statistics since not tallied.
      • [AER-5562] - (SINDEX) Fix unprotected access to si->state field in secondary index code.
      • [AER-5567] - (SMD) With paxos-protocol v5 enabled, fixed rare crash caused by thread unsafe access of succession list.
    • Enterprise Only
      • [AER-5514] - (XDR) xdr_timelag shows lag of an inactive DC.
      • [AER-5551] - (XDR) Incorrect cluster-up state after reseeding a DC.
      • [AER-5581] - (XDR) CPU utilization increases after xdr enabled for a namespace.
      • [AER-5648] - (XDR) XDR slow shipping can cause XDR info calls locked up.

    Known Issues

    Updates

  • 3.12.1.3
    Release Date: July 31, 2017

    Bug Fixes

    • Enterprise & Community
      • [AER-5707] - (KVS) Memory leak during cold-start eviction.
      • [AER-5708] - (BATCH) Batch request containing particular mixture of items with and without set name may crash.
      • [AER-5710] - (LDT) Assert fires when proxy return-to-sender handler is invoked for an LDT "ship-op".
      • [AER-5706] - (CDT) Some map ops may find unfilled index and assert after prole becomes master.

    Known Issues

  • 3.12.1.2
    Release Date: June 26, 2017

    Improvements

    • Enterprise Only
      • [AER-5661] - (XDR) Make the buffering delay configurable for the dlogwriter/dlogreader.

    Bug Fixes

    • Enterprise & Community
      • [AER-5698] - (SINDEX) Records created via migrations are not added to secondary index.

    Known Issues

  • 3.12.1.1
    Release Date: May 11, 2017

    Please use release 3.12.1.2 in lieu of this version (see Known Issues).

    Bug Fixes

    • Enterprise & Community
      • [AER-5591] - (KVS) Rare crash on new bin-name insertion caused by incorrect extra bytes copied.
      • [AER-5627] - (KVS) last-update-time erroneously not used while conflict-resolving records with > 1 duplicate copies.
      • [AER-5641] - (KVS) Cold start of records with different versions across different devices can load wrong version.
      • [AER-5639] - (SINDEX) Minor memory leak when attempting to create secondary index that already exists.
      • [AER-5630] - (SMD) Rare crash caused by retransmitted SMD message to self.
      • [AER-5628] - (CLUSTERING) Rack-aware loop can cause possible memory overwrite.
      • [AER-5629] - (FABRIC) Departure of an node with idle channel traffic can cause crash.
      • [AER-5642] - (FABRIC) Incorrect overflow number in bulk fabric-bytes-per-second.
      • [AER-5429] - (MIGRATION) Reuse of emigrate_id on node restart can cause stuck migrations.
      • [AER-5651] - (MIGRATION) Made emigration insert-id a per emigration counter.
    • Enterprise Only
      • [AER-5637] - (XDR) Adding DC to namespace can cause race condition leading to locked transactions.
      • [AER-5609] - (ACL) ACL checks on sockets of failed batch transactions can crash.

    Known Issues

  • 3.12.1
    Release Date: April 4, 2017

    Please use release 3.12.1.2 in lieu of this version (see Known Issues).

    Improvements

    • Enterprise & Community
      • [AER-5381] - (KVS) Increase max number of devices per namespace per node to 64.
      • [AER-5553] - (KVS) Support auto-pin on bonded devices.
      • [AER-5410] - (KVS) Improve device usage distribution in a namespace.
      • [AER-5556] - (KVS) Log when rebalance finds fresh partitions.
      • [AER-5552] - (SINDEX) Eliminate per-sindex lock.
      • [AER-5554] - (SINDEX) Better filtering for secondary index existence.
      • [AER-5540] - (SINDEX) Actively remove truncated records from sindex.
      • [AER-5545] - (SCAN & SINDEX) Support digest_modulo predicate filter.
      • [AER-5510] - (SCAN) Write idle-time-out now configurable from client.
      • [AER-5561] - (SMD) Skip sending unneeded SMD data on ack messages.
    • Enterprise Only
      • [AER-5549] - (XDR) Log free digest space periodically.

    Bug Fixes

    • Enterprise & Community
      • [AER-5563] - (KVS) Changing batch thread counts can crash server.
      • [AER-5570] - (KVS) Enable jemalloc with valgrind.
      • [AER-5543] - (SMD) Node-restart atomically updates local file once.
      • [AER-5537] - (CLUSTERING) Clustering crash caused by gcc 4.9 optimization.
    • Enterprise Only
      • [AER-5544] - (KVS) Auto-pin - move shared memory on warm start of numa-pin.

    Known Issues

    Updates

  • 3.12.0
    Release Date: March 15, 2017

    New Features

    • Enterprise & Community
    • Enterprise Only
      • [AER-4890] - (KVS) Make truncate set/namespace durable on cold-start.

    Improvements

    • Enterprise & Community
      • [AER-5396] - (KVS) Use CPU count info where appropriate.
    • Enterprise Only
      • [AER-4522] - (KVS) Increase per namespace per node record capacity to 32 billion records (2TB memory).
      • [AER-5516] - (XDR) Allow dynamically disabling of XDR security credentials.

    Bug Fixes

    • Enterprise & Community
      • [AER-5497] - (KVS) Negative and out-of-bound high-water-disk/memory configuration values are erroneously accepted.
      • [AER-5512] - (SINDEX) Query transaction on a network socket erroneously marks socket not reapable.
      • [AER-5522] - (SINDEX) Secondary index drop during udf-update causes deadlock.
      • [AER-5523] - (SINDEX) Rare race condition during secondary index removal can cause crash.
      • [AER-5526] - (SMD) Memory leak on principal during merge.
      • [AER-5527] - (SMD) Rare concurrent SMD fabric message in flight can cause incorrect SMD message to be picked by principal.
      • [AER-5531] - (SMD) Fix incorrect reference count which can cause crash.
    • Enterprise Only
      • [AER-5485] - (KVS) Only announce TLS in peers protocol when TLS is configured.

    Known Issues

    Updates

  • 3.11.1.1
    Release Date: February 15, 2017

    Improvements

    • Enterprise & Community
      • [AER-5138] - (KVS) Display queue-too-deep warning message only periodically.
      • [AER-5447] - (KVS) Standardize replica-writes to also use bin-less record to delete replicas.
      • [AER-5478] - (KVS) Consolidate configuration setter lock.
      • [AER-5362, AER-749, AER-3467] - (FABRIC) Channel-based fabric system, separating out delivery of different message types, such as control, transaction and migration. Various fabric bug fixes.
      • [AER-5348] - (FABRIC) Per-channel throughput log-line and statistics.
    • Enterprise Only
      • [AER-5448] - (KVS) For TLS connection, server picks the cipher preference.
      • [AER-5462] - (XDR) Enhance dc related statistics in log.
      • [AER-5484] - (XDR) Log digest of records that permanently fail shipping.

    Bug Fixes

    • Enterprise & Community
      • [AER-4839] - (KVS) Deleting a non-existent set unexpectedly creates the set metadata.
      • [AER-5420] - (KVS) Rare network interface discovery during network interface starting up causing crash.
      • [AER-5458] - (KVS) Internally generated deletes such as set-delete do not progress when allow-nonxdr-writes=false.
      • [AER-5475] - (KVS) Record updates with new bins and record size exceeding write-block-size cause memory leaks in data-in-memory configuration.
      • [AER-5505] - (KVS) multicast-group missing from config-get info calls.
      • [AER-5507] - (KVS) Records with TTL > 10 years are not correctly capped by post 3.8.3 release and newer.
      • [AER-5436] - (SECURITY) TALOS-2016-0263/CVE-2016-9049 Corrupted fabric message with large message length will cause crash.
      • [AER-5437] - (SECURITY) TALOS-2016-0265/CVE-2016-9051 Receiving corrupt batch message with missing batch bound check will cause crash.
      • [AER-5439] - (SECURITY) TALOS-2016-0267/CVE-2016-9053 Corrupted fabric msg can cause crash due to unknown particle type.
      • [AER-5310] - (FABRIC) MTU computation should ignore network interfaces that are DOWN or IPv6-only.
      • [AER-5443] - (NETWORK) Heartbeat connections do not reap immediately when node departs.
    • Enterprise Only
      • [AER-5441] - (XDR) Reuse of idle TLS connection causes shipping record relogged instead of immediately shipped.
      • [AER-5267] - (XDR) Obsoleted xdr_uptime statistics.
    • Community Only
      • [AER-5506] - (TELEMETRY) Missing multicast-group stops telemetry agent.

    Known Issues

    Updates

  • 3.11.0.2
    Release Date: January 13, 2017

    Bug Fixes

    • Enterprise & Community
      • [AER-5450] - (SINDEX) Uninitialized variable cause Sindex builder job's load_pct to be inaccurate.
      • [AER-5451] - (CLUSTERING) Incorrect node-id generated in rack-aware dynamic mode, and node-id-interface is ignored.
      • [AER-5456] - (CLUSTERING) Network interface without valid ip addresses can be used to generate node_id names.

    Known Issues

  • 3.11.0.1
    Release Date: January 9, 2017

    Bug Fixes

    • Enterprise & Community
      • [AER-5445] - (KVS) Rare crash caused by duplicate resolution response and retransmit race.
      • [AER-5416] - (MIGRATION) Rare crash caused by 'Insert' hander acting on immigration which isn't started.
      • [AER-5322] - (MIGRATION) Migration reference count error can cause unexpected crash when reaching index arena limit.

    Known Issues

  • 3.11.0
    Release Date: January 5, 2017
    • Note: Upgrade will force Cold-start. Please see cold-start to manage cold-start.

    New Features

    • Enterprise & Community
    • Enterprise Only
      • [AER-5126] - (NETWORK) Support TLS 1.2. More details on TLS configuration and network changes See TLS.

    Improvements

    • Enterprise & Community
      • [AER-5072] - (KVS) OpenSSL is now dynamically linked.
      • [AER-5393] - (KVS) Obsolete use-queue-per-device.
      • [AER-5395] - (KVS) Improved rchash implementation.
      • [AER-5407] - (KVS) Deprecate allow-inline-transactions.
      • [AER-5417] - (KVS) Handle /tmp folder permission denied at startup more gracefully.
      • [AER-5442] - (CLUSTERING) Allow unsetting of cluster-name via info call.
      • [AER-5369] - (SINDEX) Deprecated sindex-data-max-memory.
      • [AER-5403] - (NETWORK) Idle heart-beat connections are reaped based on hb.interval.
      • [AER-5404] - (NETWORK) Do not allow heartbeat timeout to be lower than 3.
      • [AER-5388] - (MIGRATION) Emigrates should requeue migrates that are not accepted.
      • [AER-5392] - (MIGRATION) Partition rebalance refactoring - extract balance_namespace().
      • [AER-5397] - (MIGRATION) Do not initialize partition_sz array with unused qnode information.
    • Enterprise Only
      • [AER-5391] - (KVS) Shared memory restructuring.

    Bug Fixes

    • Enterprise & Community
      • [AER-2604] - (KVS) Community version should not start with security stanza defined.
      • [AER-5390] - (KVS) Add migrate-retransmit-ms to info get/set.
      • [AER-5409] - (KVS) Protect non-LDT enabled nodes from migrations and replica-writes from LDT-enabled nodes. Ignore LDT records on cold-start on non-LDT-enabled nodes.
      • [AER-3344] - (SINDEX) Do not update SMD files on SMD shutdown to avoid race condition of corruption.
      • [AER-5246] - (SINDEX) Sindex memory usage accounting is incorrect when sindex change from array to tree.
      • [AER-5398] - (SINDEX) Server crash caused by index name longer than 255.
      • [AER-5438] - (SECURITY) TALOS-2016-0266/CVE-2016-9052 & TALOS-2016-0268/CVE-2016-9054 Invalid sindex message field can crash server.
      • [AER-5341] - (CLUSTERING) Setting hb version via info call can unexpectedly timeout and effect is delayed.
      • [AER-5383] - (PACKAGING) kernel.shmmax returns values larger than Bash's max int.

    Known Issues

    Updates

  • 3.10.1.5
    Release Date: January 13, 2017

    Bug Fixes

    • Enterprise & Community
      • [AER-5450] - (SINDEX) Uninitialized variable cause Sindex builder job's load_pct to be inaccurate.
      • [AER-5451] - (CLUSTERING) Incorrect node-id generated in rack-aware dynamic mode, and node-id-interface is ignored.
      • [AER-5456] - (CLUSTERING) Network interface without valid ip addresses can be used to generate node_id names.

    Known Issues

  • 3.10.1.3
    Release Date: January 7, 2017

    Bug Fixes

    • Enterprise & Community
      • [AER-5445] - (KVS) Rare crash caused by duplicate resolution response and retransmit race.
      • [AER-5416] - (MIGRATION) Rare crash caused by 'Insert' handler acting on immigration which is not started.
      • [AER-5426] - (MIGRATION) Rare crash caused by 'Done' handler acting on immigration not yet started. Fix race for migrate_rx_partitions_active counter. Deprecated migrate-rx-lifetime-ms.

    Known Issues

  • 3.10.1.2
    Release Date: January 3, 2017

    Bug Fixes

    • Enterprise & Community
      • [AER-5394] - (KVS) Adjust conflict resolution to allow keeping 'older' record after split brain.
      • [AER-5418] - (KVS) Log level critical cannot be used as a logging context.
      • [AER-5434] - (KVS) Rack-aware with > 23 nodes on rack can crash.
      • [AER-5440] - (CLUSTERING) HB-V3 incorrectly always send "null" as a cluster-name, causing clustering issue with future releases.
    • Enterprise Only
      • [AER-5425] - (XDR) Wrongly declare all DC's down and XDR throughput becomes zero.
      • [AER-5343] - (XDR) Rare race condition in digest-log wrap-around scenario cause outstanding records to become 0.

    Known Issues

  • 3.10.1.1
    Release Date: December 8, 2016

    Bug Fixes

    • Enterprise & Community
      • [AER-5406] - (KVS) evict-tenths-pct calculation overflow/incorrect when namespace objects > ~800m.
      • [AER-5415] - (MIGRATION) Change migrate-threads down dynamically crashes daemon.

    Known Issues

  • 3.10.1
    Release Date: November 17, 2016

    New Features

    • Enterprise & Community
      • [AER-3261] - (KVS) Special TTL value of '-2' now means record's TTL is unchanged when record is updated.

    Improvements

    • Enterprise & Community
      • [AER-5038] - (KVS) Upgrade to jemalloc version 4. Improve long term memory allocation to improve fragmentation. New statistics to monitor jemalloc heap efficiency.
      • [AER-5161] - (KVS) Improve log when server assert occurs.
      • [AER-5273] - (KVS) Read duplicate resolution should only be done when repeatable read is turned on.
      • [AER-5332] - (KVS) Better logging when no active network interfaces are available.
      • [AER-5335] - (KVS) Transactions now try to return error code TIMEOUT instead of closing socket.
      • [AER-5356] - (KVS) Add transaction retry statistics.
      • [AER-5370] - (KVS) Remove unnecessary request-hash processing when cluster state changes.
      • [AER-5363] - (MIGRATION) Default for migrate-max-num-incoming is now 4.
      • [AER-5364] - (MIGRATION) Reduce likelihood of multiple migrations to same node.
      • [AER-5365] - (MIGRATION) Retransmit tuning and tracking - migrate-retransmit-ms now on namespace level, default of 5 second.
      • [AER-5295] - (STORAGE) Improved storage name detection to set device scheduler "noop".
    • Enterprise Only
      • [AER-5333] - (KVS) Refactor fast restart to be namespace order-independent on config.
      • [AER-5297] - (XDR) Disconnect from a DC if no source namespace replicates to it.
      • [AER-5300] - (XDR) Remove RBUFFER_FLAG_TRACE mechanism which is adding layers to the logging.

    Bug Fixes

    • Enterprise & Community
      • [AER-4578] - (KVS) single-bin namespace can cause SEGV while reading beyond allocated memory.
      • [AER-5327] - (KVS) Access-address no longer support loop-back 127.0.0.1
      • [AER-5354] - (KVS) In mixed version cluster, 3.10's peers-list will now also include peer-nodes which are on previous releases.
      • [AER-5379] - (KVS) obj-size-hist-max not returned when querying namespace config.
      • [AER-5304] - (CLUSTERING) Incorrect fabric network address used when changing heartbeat protocol version from v3 back to v2.
      • [AER-5309] - (CLUSTERING) Rare cluster integrity caused by incorrectly rejecting new principal node's paxos message.
      • [AER-5340] - (CLUSTERING) In mesh network, split cluster may not re-form due to incorrectly losing "isSeed" info.
      • [AER-5315] - (UDF) Memory stomp caused by UDF creating list with null elements.
      • [AER-5312] - (AGGREGRATION) Memory leak of records caused by aggregation, if records are later deleted.
    • Enterprise Only
      • [AER-5377] - (ACL) Query user or query role can cause server termination due to incorrect file handle reference counting.
      • [AER-5385] - (UDF) Failed bin create cause leak and xdr crash.
      • [AER-5174] - (XDR) Global xdr-min-lastshipinfo does not move forward, due to rogue node info in system.
      • [AER-5193] - (XDR) DC marked as CLUSTER_UP even though it is down.
      • [AER-5249] - (XDR) Reconnect inactive cluster with valid seed nodes.
      • [AER-5293] - (XDR) No longer detect remote cluster state changes, if detection fails on source cluster startup.
      • [AER-5350] - (XDR) Shipping from single-bin namespace with unexpected null bin data can cause crash.
      • [AER-5358] - (XDR) Startup race condition cause limited connections (64) to pre 3.7.0.1 releases.
      • [AER-5360] - (XDR) Enhance log for outgoing/incoming re-logged digests.
    • Community Only
      • [AER-5353] - (TELEMETRY) On rpm systems, telemetry daemon not stopped if server not running.

    Known Issues

  • 3.10.0.3
    Release Date: October 21, 2016
    • When upgrading, please follow Network Upgrade for 3.10 to make required aerospike.conf configuration changes.
    • This server version may require an upgrade to your existing client to the latest version. For more information on client compatibility, click here.
    • SortedMap Operations is now GA.
    • Customers currently on Enterprise Edition 3.10.0 or 3.10.0.1, please contact Aerospike support for instructions to upgrade to 3.10.0.3.
    • This release introduces in the Enterprise Edition only an index converter for clearing bits for tombstone. A downgrade from this release will force a cold start.

    New Features

    • Enterprise & Community
      • [AER-5190] - (CLUSTERING) Heartbeat V3 new supported features.
      • [AER-5231] - (CLUSTERING) Support cluster-name.
    • Enterprise Only

    Improvements

    • Enterprise & Community
      • [AER-5092] - (KVS) Add Read / Write histograms per record size on storage benchmark.
      • [AER-5256] - (KVS) Partition drops now done by background thread.
      • [AER-5257] - (KVS) Obsolete replicas-read/replicas-write.
      • [AER-5270] - (KVS) Remove unneeded record reference count.
      • [AER-5271] - (KVS) Separate partition drop on its own queue thread.
      • [AER-5291] - (KVS) Partition rebalance refactoring.
      • (KVS) Bin delete on a non-existing record now returns NOTFOUND (error code 2).
      • [AER-5096] - (MIGRATION) Empty migrate no longer spawn unused threads for migration.
      • [AER-4728] - (CLUSTERING) Support heartbeat version change when using mesh.
      • [AER-5062] - (FABRIC) Inbound/outbound fabric buffer now default with 1M stack memory.
      • [AER-5200] - (FABRIC) Guard against network packets that may contain garbage.
      • [AER-5275] - (FABRIC) Fabric benchmark instrumentation.
      • [AER-5264] - (SINDEX) Use client replica bitmap to check if partition is queryable.
      • [AER-5087] - (UDF) Scan aggregation - Improved map allocation performance.
      • [AER-5137], [AER-5047], [AER-3804] - (SCAN) Set scan's socket send() timeout to be 10 seconds, to accommodate slow or improperly disconnected client.
      • [AER-5222] - (NETWORK) Deprecate reuse-address in network section.
      • [AER-5274] - (NETWORK) Deprecated mcast-ttl and replace with multicast-ttl.
      • [AER-5282] - (NETWORK) Deprecate network.heartbeat.interface-address.
      • [AER-5035] - (NETWORK) Honor address field in network.fabric and network.info section.
      • [AER-5269] - (NETWORK) Change network.service.network-interface-name to service.node-id-interface.
      • [AER-5283] - (NETWORK) Multicast heartbeat must provide multicast-group as the group address.
      • [AER-5147] - (NETWORK) New peers list for node discovery.
    • Enterprise Only
      • [AER-5181] - (XDR) Log global last ship time.
      • [AER-5243] - (XDR) xdr-ship-bins should do replace when 80% of the data has changed rather than 80% of the bins.
      • [AER-5245] - (XDR) Fixes XDR log inconsistency.

    Bug Fixes

    • Enterprise & Community
      • [AER-5272] - (KVS) JEMalloc stats randomly truncated under systemd.
      • [AER-5299] - (KVS) Incorrect comparison for large void-times on cold start. Removed max_void_time stat.
      • [AER-5241] - (CLUSTERING) tip-clear:all will clear both seed nodes and adjacency nodes.
      • [AER-5278] - (CLUSTERING) Principal node may illegally re-enter partition_rebalance if subordinate retransmits PARTITION_SYNC_REQUEST_ACK.
      • [AER-5307] - (CLUSTERING) Node crash on receiving non-conforming mesh heartbeat messages.
      • [AER-4273] - (UDF) Avoid unneeded re-parse of UDF parameters in scan/aggregate/query.
      • [AER-5258] - (UDF) Invalid memory access during UDF loading on startup.
      • [AER-3895] - (SINDEX) Querying for empty string does not return data, even though they are indexed.
      • [AER-4930] - (SINDEX) Replica-creates not updating sindex entry, cause missing records in query.
      • [AER-5238] - (SINDEX) Potential query crash on bins with List/Map while filtering query result.
      • [AER-4947] - (STORAGE) Discrepancy in device details of 'dump_wb_summary' command.
      • [AER-5198] - (NETWORK) Infiniband network interface does not generate meaningful node_id.
      • [AER-5279] - (NETWORK) Do not advertise network interface when it is in ifdown state.
      • [AER-5234] - (CDT) Server crashes when sending unimplemented list/map operation commands.
      • [AER-5239],[AER-5303] - (CDT) Calling map.replace_items incorrectly returns success.
      • [AER-5285] - (CDT) Clear null map flags when persisted.
    • Enterprise Only
      • [AER-5122] - (MIGRATION) Migration can be stuck with an empty node joining.
      • [AER-5191] - (MIGRATION) Removed unneeded warning - "merge meta ack: could not find immigration".
      • [AER-5216] - (XDR) Do not allow same dc to be multiply added in the namespace.
      • [AER-5224] - (XDR) Records missing in remote DC while doing linkdown processing, if number of records logged < 100.
      • [AER-5237] - (XDR) Shipping does not progress with mismatched rbuffer version.
      • [AER-5164] - (XDR) Digest-log overflow issues leading to non-reclamation or loss of valid digest log records.
      • [AER-5177] - (XDR) Log warning when digest-log is full, and increment dlog_overwritten_error counter.
      • [AER-5188] - (XDR) TPS limit based throttling too aggressive.
      • [AER-5260] - (XDR) Changing XDR read threads locks server and kills XDR throughput.
      • [AER-5261] - (XDR) Dynamically changing xdr-read-threads crashes server.

    Known Issues

    Updates

  • 3.9.1.1
    Release Date: September 2, 2016

    Bug Fixes

    • Enterprise & Community
      • [AER-5253] - (KVS) For network interface with label, interface are not correctly enumerated.
      • [AER-5255] - (KVS) Heartbeat publishes incorrect address to be used by fabric.

    Known Issues

  • 3.9.1
    Release Date: August 12, 2016

    Improvements

    • Enterprise & Community
      • [AER-4454] - (CLUSTERING) Enhanced heartbeat subsystem. Obsoleted operational commands such as "snub/dun".
      • [AER-5146] - (KVS) Socket API refactoring.
      • [AER-5172] - (KVS) Add new error codes for map_add() operations - ELEMENT_NOT_FOUND & ELEMENT_EXISTS.
      • [AER-5187] - (KVS) Add deleted_last_bin stat for record deleted via last bin deleted.
      • [AER-5060] - (KVS) Log when set-delete reverts to false.
      • [AER-4669] - (KVS) Obsolete "mesh-address" configuration.
      • [AER-5289] - (KVS) Set-config syntax for heartbeat parameters are more consistent.
      • [AER-5128] - (FABRIC) Obsolete migrate_progress_send/recv.
      • [AER-4587] - (CLUSTERING) Allow seed node to accept hostnames - via tip and via config.
    • Community Only
      • [AER-5082] - (CLUSTERING) Community cluster size limit of 32. For more information click here.

    Bug Fixes

    • Enterprise & Community
      • [AER-5127] - (KVS) Full bin data incorrectly returned when querying for a non-existent map key - Respond_all_ops reads now consistent.
      • [AER-5143] - (KVS) Return cluster config also in "config-get:" call.
      • [AER-5166] - (KVS) cf_fault_event_nostack() should respect log-local-time.
      • [AER-5199] - (KVS) Generation & TTL in client response incorrect (zero) for writes that duplicate resolve and replicate.
      • [AER-5213] - (KVS) Crash or garbage returned on list/map read-only operations that has empty results.
      • [AER-5202][AER-5150] - (KVS) Migrated/Replicated map bins builds wrong map-index. Thus map operations on promoted master crashes server.
      • [AER-5290] - (KVS) Disallow bin writes of map with NULL data.
      • [AER-5140] - (UDF) Correctly adjust storage stats when record is deleted via no-more bins in UDF.
      • [AER-5178] - (UDF) Log entries generated from Lua should display the Lua file name and line number.
      • [AER-5113] - (SCAN) Partial scans can cause memory/stack corruption.
      • [AER-5145] - (FABRIC) Race conditions and object reference fixes for fb and fne.
      • [AER-4822] - (CLUSTERING) Server crash paxos-max-cluster-size set differently on different nodes.
      • [AER-5136] - (CLUSTERING) Unstable cluster formation if the cluster size reaches paxos-max-cluster-size.
    • Enterprise Only
      • [AER-5184] - (KVS) Unexpected binless records created by Rapid Rebalance.
      • [AER-5108] - (XDR) Bin-level shipping not handling deleted bins.
      • [AER-5124] - (XDR) Failed node processing to other DCs is aborted if a link is down.
      • [AER-5131] - (XDR) xdr-info-timeout dynamic config change is not reflected properly.

    Known Issues

    Updates

  • 3.9.0.3
    Release Date: July 31, 2016

    Bug Fixes

    • Enterprise & Community
      • [AER-5180] - File descriptor leak cause by transactions requiring duplicate resolution.
      • [AER-5168] - LDT duplicate resolution phase (shipop) cause crash due to null msgp pointer.

    Known Issues

  • 3.9.0.2
    Release Date: July 26, 2016

    Bug Fixes

    • Enterprise & Community
      • [AER-5159] - Hot key transactions with some timeout can cause transaction to fail, manifesting as "non-null 'from'" assert and abort server.

    Known Issues

  • 3.9.0.1
    Release Date: July 22, 2016

    Bug Fixes

    • Enterprise & Community
      • [AER-5141] - (KVS) Nodes with expiration/eviction may crash while freeing stale message. Fixes regression for [AER-4868].
      • [AER-4930] - (SINDEX) Replica-creates not updating sindex entry, cause missing records in query.
      • [AER-5142] - (LDT) Timed-out of LDT transactions during migration are not properly handled.

    Known Issues

  • 3.9.0
    Release Date: July 11, 2016
    • Segmentation fault on 3.9.0. Fixed in version 3.9.0.1
    • Statistic/Benchmark/Logging Revamp. Please review details to investigate necessary changes for your monitoring systems.

    New Features

    • Enterprise & Community
      • [AER-4233] - (KVS) Provide statistics for single record transaction at namespace level.
      • [AER-4723] - (KVS) Benchmark at namespace level.
      • Aerospike Server now available on Ubuntu 16.04

    Improvements

    • Enterprise & Community
      • [AER-4735] - (KVS) Single-record transaction code refactoring.
      • [AER-4868] - (KVS) Expire-/evict-deletes no longer do duplicate resolution.
      • [AER-4873] - (KVS) Reads no longer inserted in rw-request hash unless duplicate resolution is necessary.
      • [AER-5021] - (KVS) Obsolete replica-fire-and-forget.
    • Enterprise Only
      • [AER-5081] - (XDR) Sorted Map to Retain Sorting via XDR shipping.
      • [AER-5079] - (XDR) Improve latency caused by shipping list/map with high nesting/elements.
      • [AER-5091] - (XDR) Adjust XDR timeout during cluster tending.

    Bug Fixes

    • Enterprise & Community
      • [AER-4549] - (KVS) SSD read failure on a write crashes server.
      • [AER-5031] - (KVS) Deleted but still-referenced index elements are now flagged, fixing various race conditions such as reading binless records.
      • [AER-5115] - (KVS) Fix memory leak for record deletes resulting from last bin removed.
      • [AER-5117] - (KVS) Scan with bin selection option, may return unexpected result code.
      • [AER-5116] - (FABRIC) Strict check on extra fabric message release.
      • [AER-4891] - (MIGRATION) Record delete are applied immediately during migration - no more delete journaling.
      • [AER-5083] - (KVS) Miscellaneous SortedMap edge condition bugs, resulting either crash or invalid results.
      • [AER-4373] - (LDT) Subrecord ref not accounted in warm start.
    • Enterprise Only
      • [AER-5118] - (XDR) Throttling does not work properly if round trip time of any link is <1ms.

    Known Issues

    Updates

  • 3.8.4
    Release Date: June 17, 2016

    New Features

    • Enterprise & Community Sorted Map Operations (Developer Preview). For more information click here. Sorted Maps is not transmitted via XDR.

    Improvements

    • Enterprise & Community
      • [AER-5064] - (KVS) Improve non-evictable bucket message.
      • [AER-5069] - (KVS) Improve scan progress % display's granularity.
      • [AER-5059] - (CLUSTERING) Multicast heartbeats will now only listen on specified multicast address.
    • Enterprise Only
      • [AER-5067] - (XDR) Added stat_dlog_overwritten stat for lost records when digestlog is full.

    Bug Fixes

    • Enterprise & Community
      • [AER-5071] - (FABRIC) Conflict resolution was not properly using last-update-time.
      • [AER-4997] - (CDT) List insert operation was not checking bad parameters.
    • Enterprise Only
      • [AER-5001] - (XDR) IP mapping for seed nodes defined in dc-int-ext-ipmap was not used.
      • [AER-5039] - (XDR) Throughput is now smoother during very highly volatile latency scenarios.
      • [AER-5075] - (XDR) Handle non-existent namespaces in failednode/linkdown processing.

    Known Issues

  • 3.8.3
    Release Date: June 2, 2016
    • ATTENTION: This release introduces a new timestamp in the index for record's last updated time. A downgrade from this release will force a cold start.

    New Features

    • Enterprise Only
      • [AER-4550] - (CLUSTERING) Major migration performance improvement through Rapid Rebalance.
      • [AER-4967] - (XDR) New configuration to allow bin level shipping (to minimize bandwidth usage).
      • [AER-4983] - (XDR) Ability to ignore pending digestlog records in XDR (no resume).
      • [AER-4993] - (XDR) Enable dc-security-config-file to be dynamically configurable.

    Improvements

    • Enterprise & Community
      • [AER-4958] - (KVS) Add record's last updated time on the server.
      • (KVS) Cold start resolves different record versions based on last-update-time instead of generation.
      • (KVS) Replace conflict-resolution-policy=ttl with conflict-resolution-policy=last-update-time.
      • (KVS) Namespace's max-ttl is capped to 10 years.
      • [AER-4448] - (KVS) Improve cold start eviction when there is no records to evict.
      • [AER-4773] - (KVS) Cold start will continue to load past HWM breach, until stop_writes.
      • [AER-4956] - (KVS) Improve client's querying of partition ownership by caching map on server.
      • [AER-5024], [AER-4978], [AER-4842] - (KVS) Minor logging improvements.
      • [AER-5030] - (MIGRATION) New migration statistics at namespace level.
      • [AER-5042] - (SINDEX) Change secondary index stat from "objects" to entries.
      • [AER-5009] - (UDF) Refactor of UDF callback so no as_transaction container is needed.
    • Enterprise Only
      • [AER-4810] - (KVS) Obsolete warm restart converter V2 (v2 -> V4). Any customers upgrading from versions before 3.1.3 Enterprise will need to cold start.
      • [AER-4964] - (XDR) Add stat for successfully shipped records (stat_recs_shipped_success).
      • [AER-4991] - (XDR) Stats cleanup and renaming (renamed noship_recs_hotkey_timeout to hotkeys_fetched and remove duplicate/deprecated stats).

    Bug Fixes

    • Enterprise & Community
      • [AER-4955] - (KVS) Do not include on service list any 127.0.0.* when address=any.
      • [AER-4990] - (KVS) Restart on CentOS did not wait long enough to complete flushing to storage.
      • [AER-4998] - (KVS) Allow for records to expire when no evictions are possible.
      • [AER-5026] - (KVS) A timed out duplicate resolution transaction incorrectly asserts on NULL fd.
      • [AER-5027] - (TELEMETRY) Send build number in telemetry.
      • [AER-4877] - (CLUSTERING Restarting paxos principal node rapidly can result in a malformed cluster.
      • [AER-4971] - (MIGRATION) Fix migration for replication factor 3 introduced in 3.7.5.
      • [AER-4975],[AER-4988] - (MIGRATION) Rare case of un-terminated migrations can cause write blocks to not get defragmented.
    • Enterprise Only
      • [AER-4974] - (XDR) XDR read requests not counted in stat_read_success anymore.
      • [AER-5015] - (XDR) Fix outstanding stat value after digestlog wrap around.
      • [AER-5016] - (XDR) Fix for corrupted (really high) free_dlog_pct value post no-resume restart.
      • [AER-5032] - (XDR) Potential crash for incorrectly closing rogue fd used by xdr authentication connections.
      • [AER-5036] - (XDR) Fix for potential crash when fetching XDR stats after XDR has been stopped.
      • [AER-5050] - (XDR) Fix for failed node processing getting stuck when dynamically changing xdr-hotkey-time-ms during failed node processing.
      • [AER-5056] - (XDR) XDR shipping to extra namespaces during CLUSTER_WINDOW_SHIP state.
      • [AER-5058] - (XDR) Use a globally unique dedupulication key digest for keeping track of hotkeys.

    Known Issues

    Updates

  • 3.8.2.4
    Release Date: May 16, 2016

    Bug Fixes

    • Enterprise Only
      • AER-5011 - (XDR) Deletes of pending hot-keys are not counted as shipped, causing Failed Node Processing to not finish.
      • AER-5012 - (XDR) Digest log version error after wrap-around incorrectly stops shipping on node restart.

    Known Issues

  • 3.8.2.3
    Release Date: May 10, 2016

    Bug Fixes

    • Enterprise & Community
      • [AER-4994] - (KVS) Namespace requiring evicting on cold-start crashes.
    • Enterprise Only
      • [AER-4995] - (XDR) Crash after 2^31 non-hotkey writes in SSD configuration.
      • [AER-5000] - (XDR) Failed-node processing race condition may cause processing being stuck and hot-keys not shipped.

    Known Issues

  • 3.8.2.2
    Release Date: May 5, 2016

    Improvements

    • Enterprise & Community
      • [AER-4929] - (FABRIC) Remove unnecessary memory allocation and copying of fabric messages.
      • [AER-4792] - (UDF) Implement record.numbins().

    Bug Fixes

    • Enterprise & Community
      • [AER-2423] - (KVS) Tip command on a multicast system crashes server.
      • [AER-4602] - (KVS) SEGV during startup with misconfigured multicast setting.
      • [AER-4808] - (KVS) Various fixes to log lines with incorrect format strings.
      • [AER-4979] - (KVS) Incorrect bytes_emigrating counter causing migrations stuck.
      • [AER-4889] - (FABRIC) Epoll race condition on fabric causing fabric threads not used.
      • [AER-4920] - (MIGRATION) Make retransmits to be asynchronous to minimize missing Migrate Acks.
      • [AER-4970] - (SCAN) Cannot delete a lower priority job when higher priority jobs exist.
      • [AER-4919] - (UDF) Check minimum disk space available before committing record updates.
      • [AER-4826] - (SINDEX) Unable to add query tuning settings to aerospike.conf.
      • [AER-4966] - (PACKAGING) Redhat7 server installation does not create default log path.
    • Enterprise Only
      • [AER-4945] - (XDR) Under load, flushing digests to disk on shutdown doesn't finish.
      • [AER-4972] - (XDR) SEGV when passing using info "dc/NAME" when enable-xdr false.
      • [AER-4934] - (XDR) Improve detection of pipeline ability on destination.
      • [AER-4935] - (XDR) Use microsecond resolution for xdr-max-ship-throughput limit calculation.

    Known Issues

    Updates

  • 3.8.1.2
    Release Date: April 21, 2016
    • Datacenter related info calls (includes collectinfo) against a cluster that has a disabled xdr configuration with a specified datacenter may crash (AER-4972). Fixed in 3.8.2.2. See further details here.
    • For XDR enabled clusters, please refer to Upgrading XDR to version 3.8 to review necessary XDR configuration changes.

    Bug Fixes

    • Enterprise Only
      • [AER-4951] - (XDR) Fix potential crash during xdr failed node handling with hotkeys.
      • [AER-4950] - (XDR) xdr-delete-shipping-enabled not settable in config file anymore.

    Known Issues

  • 3.8.1.1
    Release Date: April 18, 2016
    • Datacenter related info calls (includes collectinfo) against a cluster that has a disabled xdr configuration with a specified datacenter may crash (AER-4972). Fixed in 3.8.2.2. See further details here.
    • For XDR enabled clusters, please refer to Upgrading XDR to version 3.8 to review necessary XDR configuration changes.

    Bug Fixes

    • Enterprise Only
      • [AER-4942] - (XDR) Setname is not propagated correctly on an upgrade situation.
      • [AER-4941] - (XDR) Increase MAX_IN_FLIGHT_LEGACY.
      • [AER-4944] - (XDR) Localized fix for draining records on shutting down shipper threads.

    Known Issues

  • 3.8.1
    Release Date: April 15, 2016
    • Datacenter related info calls (includes collectinfo) against a cluster that has a disabled xdr configuration with a specified datacenter may crash (AER-4972). Fixed in 3.8.2.2. See further details here.
    • For XDR enabled clusters, please refer to Upgrading XDR to version 3.8 to review necessary XDR configuration changes.

    New Features

    • Enterprise & Community
      • Secondary Index on List and Map. For more information see list-index and map-index
      • Geospatial is now GA.
      • New Platforms - CentOS7, Debian8 with systemd compatibility.
    • Enterprise Only
      • In-Process XDR. For more information click here
    • Community Only
      • Telemetry. For more information click here

    Improvements

    • Enterprise & Community
      • [AER-4496] - (KVS) Transaction data structure trimmed for better cache-alignment, boosting performance.
      • [AER-4874] - (KVS) Info transaction data structure trimmed for performance.
      • [AER-4655] - (KVS) Granular eviction histogram to give predictable eviction. No more random record evictions within a histogram bucket. Introduce evict-hist-buckets configuration.
      • [AER-4896] - (KVS) Move all sample config files into a sub directory
      • [AER-4912] - (KVS) Make aerospike compilable on ppc.
      • [AER-4845] - (FABRIC) Replica and migration writes should also use namespace jemalloc arenas, to minimize fragmentation in data-in-memory configuration.

    Bug Fixes

    • Enterprise & Community
      • [AER-4888] - (KVS) Epoll race condition could leave some demarshal threads unused.
      • [AER-4698] - (FABRIC) Node missing services list after quick restart.
      • [AER-4907] - (UDF) Writes bypassed stop_write check, resulting in storage full.

    Known Issues

    Updates

  • 3.7.5.1
    Release Date: March 31, 2016

    Bug Fixes

    • Enterprise & Community
      • [AER-4886] - (KVS) Batch request are incorrectly handled during duplicate resolution and timeout.
    • Enterprise Only
      • [AER-4887] - (XDR) Replication fail due to server's strict message format checking.

    Known Issues

  • 3.7.5
    Release Date: March 23, 2016

    New Features

    • Enterprise & Community
      • Aerospike Server now available on Ubuntu 14.04.
      • [AER-4869] - (FABRIC) Namespace level migration prioritization.

    Improvements

    • Enterprise & Community
      • [AER-4754] - (KVS) Consolidate default-timeout assignment code path. More strict protocol sanity checking.
      • [AER-4800] - (KVS) Improve primary index tree structure and traversal.
      • [AER-4824] - (KVS) Vmap implementation used for set and bin info goes lockless.
      • [AER-4667] - (FABRIC) Decrease migration memory footprint.
      • [AER-4743] - (FABRIC) Namespace level migration tuning. Migration configuration tuning highly recommended.
      • [AER-4846] - (UDF) Background UDF now protected against creating new records.
      • [AER-4828] - (GEO) Improve error responses for invalid regions passed in for geo index.
      • [AER-4687] - (GEO) Preliminary support for indexing GeoJSON elements in lists or maps.

    Bug Fixes

    • Enterprise & Community
      • [AER-4849] - (KVS) Fix crash when heartbeat protocol is set to "none".
      • [AER-4858] - (KVS) Fix rare memory leak on scan aggregations.
      • [AER-4785] - (FABRIC) Remove unneeded migration cancellation logic.
      • [AER-4867] - (FABRIC) Erroneous warnings due to duplicate migration start messages.
      • [AER-4848] - (SINDEX) Incorrectly sleeping when query results = 0.

    Known Issues

    Updates

  • 3.7.4.1
    Release Date: March 8, 2016

    Bug Fixes

    • Enterprise & Community
      • [AER-4832] - (UDF) When fetching from the bin cache, return a bin's value even if it's a nil.
      • [AER-4812] - (UDF) Update does not correctly account for stats.
    • Enterprise Only
      • [AER-4830] - (XDR) Does not ship set-name.

    Known Issues

  • 3.7.4
    Release Date: February 22, 2016
    • Regression - XDR erroneously insert new records without a setname on upgrade. Fixed in version 3.7.4.1.

    Improvements

    • Enterprise & Community
      • [AER-4747] - (KVS) Logging functions now lazily evaluate arguments.
      • [AER-4775] - (KVS) Remove redundant clock calls in microbenchmark.
      • [AER-4779] - (KVS) In read_local(), build response message under record lock, then send it to client later, outside record lock.
      • [AER-4749] - (FABRIC) Remove unused multi-target migration code.

    Bug Fixes

    • Enterprise & Community
      • [AER-4772] - (KVS) Rare proxy request ping-ponged for requests received by random, non-replica node.
      • [AER-4289] - (KVS) Race condition causing crash on merging of sindex meta data.
      • [AER-4766] - (KVS) List_insert fails when inserting into a list > 512 elements.
      • [AER-4786] - (KVS) When 'nsup-startup-evict' is false, cold-start erroneously early terminates.

    Known Issues

  • 3.7.3
    Release Date: February 4, 2016

    Improvements

    • Enterprise & Community
      • [AER-4542] - (KVS) Write latency issue during migration with write duplicate resolution.
      • [AER-2272] - (KVS) Deprecated write_to_device flag, introduced as_storage_record_write().

    Bug Fixes

    • Enterprise & Community
      • [AER-4730] - (KVS) Put() with no multi-ops is incorrectly counted as delete transaction.
      • [AER-4741] - (KVS) Crash accessing geojson data type via list operations.
      • [AER-4750] - (KVS) Minimize time of rejected transactions during initial partition rebalance.
      • [AER-4737] - (FABRIC) Potential (to drop) dropped packets when coalescing fabric messages.
      • [AER-4717] - (SINDEX) Invalid sindex gives garbage info.
      • [AER-4753] - (SINDEX) Sending multiple predicates crashes server.

    Known Issues

    Updates

  • 3.7.2
    Release Date: January 22, 2016

    Improvements

    • Enterprise & Community
      • [AER-4656] - (KVS) ClusterKey mismatch on proxyee should be allowed to proceed.
      • [AER-4703] - (KVS) Improve invalid message handling - proxyee now report invalid messages to proxyer.

    Bug Fixes

    • Enterprise & Community
      • [AER-4501] - (KVS) Allow replica transactions on cluster key mismatch to continue.
      • [AER-4691] - (KVS) Incorrectly accessing freed memory on writes - namespaces with sindex and non-integer data type.
      • [AER-4705] - (KVS) Rare race condition on batch-index, incorrectly releasing a retransmitted read duplicate resolution.
      • [AER-4721] - (KVS) Replace not working properly on namespaces configured as storage engine device and have a secondary index.
      • [AER-4722] - (Clustering/Migrations) Migrations may never complete in some cases (due to missing ack when receiving records with no bins).
      • [AER-3296] - (Clustering/Migrations) Migrate_num_incoming not resetting on cluster-reset, potentially causing subsequent migrations to be rejected.

    Known Issues

    Updates

    • Enterprise & Community

  • 3.7.1
    Release Date: January 4, 2016

    Maintenance release for Clustering/Migration.

    Improvements

    • Enterprise & Community
      • [AER-1859] - (KVS) Modify Rack-Aware code to work for any replication factor.
      • [AER-4558] - (KVS) Dump major statistics at regular interval in log file.
      • [AER-4643], [AER-3984] - (KVS) Improve prole delete handling.
      • [AER-4666] - (Clustering/Migration) Do not unnecessarily construct migration records when cluster key mismatches.
      • [AER-4636] - (Clustering/Migration) Reduced number of rebalance rounds.
      • [AER-4196] - (SINDEX) When deleting a set, also remove all entries from sindexes.
    • Enterprise Only
      • [AER-4676] - (AUDIT) Remove redundant warning "Allow op failed - no book".

    Bug Fixes

    • Enterprise & Community
      • [AER-4594] - (KVS) Do not queue requests on slow queue for cluster key mismatch.
      • [AER-4646] - (KVS) Asd crash when using systemctl restart command.
      • [AER-4668] - (KVS) Honor not evictable sets on cold startup.
      • [AER-4645] - (Clustering/Migration) Race condition caused by cluster key changing before disallow_migrations is set.
      • [AER-4679] - (Clustering/Migration) Fixed possible double-free of fabric message when one destination node is congested.
      • [AER-4487],[AER-4690] - (Clustering/Migration) Race condition causing incorrect heartbeat fd saved and later not removable.
      • [AER-4647] - (SINDEX) Asd crash on empty list indexing.
      • [AER-4675] - (PACKAGING) Asd starts up under aerospike user despite root / root configured in systemd aerospike.service file.

    Known Issues

    Updates

  • 3.7.0.2
    Release Date: December 16, 2015

    Improvements

    • Enterprise & Community
      • [AER-4637] - (KVS) List Pop/Remove operations now support variable argument count.

    Bug Fixes

    • Enterprise & Community
      • (KVS) Fix list operations on strings size 0-16.
      • (KVS) Handle edge case where append/insert no-op operations on not-in-use bins result in empty list bin.
      • (KVS) Add support for CDT list no-op so the bin won't get freed incorrectly.
      • (KVS) Handle possible overflows if user give huge numbers for index or count in list operations.

    Known Issues

  • 3.7.0.1
    Release Date: December 10, 2015

    New Features

    • Enterprise & Community
      • [AER-4424] - Geospatial Indexes (Experimental Release). For more information click here.
      • [AER-4544] - Operations on list. For more information click here.
      • [AER-4568] - (KVS) Add stop-writes threshold on a per set basis.
      • [AER-3789] - (SCAN) Add option to include LDT data in scans.
      • [AER-3639] - (MIGRATION) Added new migration stats to accurately reflect migration progress.
      • [AER-3439] - (CLUSTERING) Support dynamically changing the heartbeat mesh seed list.
      • [AER-3053] - (INFO) Add option to use local timestamps in server log.
    • Enterprise Only
      • [AER-2850] - (KVS) Publish alternative-services, used by XDR source cluster to connect remote cluster.
      • [AER-4274] - (ACL) Allow creating a secure user w/o a role.
      • [AER-4486] - (AUDIT) Include the client IP/port in security audit trail messages.

    Improvements

    • Enterprise & Community
      • [AER-4512],[AER-4563],[AER-4570]- Migration Improvements - Fix condition where redundant/incorrect migration requests are initiated. Remove incorrect migration state (pending-write) which causes "pending writes never drain" assertion or incorrect object counts.
      • [AER-4540] - (MIGRATION) Remove partition.reject_writes which has outlived its usefulness.
      • [AER-4310] - (KVS) Switched to using abstract UNIX domain sockets from being bound to a path in /tmp.
      • [AER-4452] - (KVS) Improve caller of msgpacks throughout (scan/udf) to use new msgpack API.
      • [AER-4449] - (KVS) Allow unread data in socket after a complete transaction is read.
      • [AER-4508] - (SCAN) Enhance scan's migration detection.
      • [AER-4450] - (UDF) as_val re-org for UDF.
      • [AER-4493] - (UDF) Aggregation code refactoring.
      • [AER-4318] - (SINDEX) Use master nodes instead of qnodes for queries.
      • [AER-4500] - (CLUSTERING) New cluster recovery policy paxos-recovery-policy=auto-reset-master.
    • Enterprise Only
      • [AER-4269] - (XDR) A deleted bin on an XDR source is not updated on the XDR target. Ability to replace a record instead of merge.
      • [AER-4580] - (XDR) Always allow asd to listen on 127.0.0.1.

    Bug Fixes

    • Enterprise & Community
      • [AER-4553] - (KVS) Server crash when printing strings containing %s.
      • [AER-5204] - (KVS) Services list intermittently add semicolon at start.
      • [AER-4612] - (UDF) Check for > 512 bins is missing when data-in-memory.
      • [AER-4112] - (MIGRATION) Correct erroneous warning "source node [node_id] not found in migration rx state".
      • [AER-4494] - (SINDEX) Memory corruption of stack variable causing undetermined result for list/map indexing.
      • [AER-4103] - (SINDEX) Server is crashing while creating index with index name more than 256 size.
      • [AER-3601] - (PACKAGING) "python" dependency for tools package is too strict and will not install if "python 2.7" installed.

    Known Issues

    Updates

    • aerospike-tools 3.7.0
    • Find out more about the new features and supporting clients released in this version, visit Client Matrix.

  • 3.6.4
    Release Date: November 10, 2015

    Batch related node crash has been fixed.

    Bug Fixes

    • Enterprise & Community
      • [AER-4552],[AER-4564] - (KVS) Fix batch-index memory corruption.
      • (KVS) Fix rare memory leak on batch-index errors.
      • (KVS) Use separate jemalloc arenas for batch-index buffers.

    Known Issues

  • 3.6.3
    Release Date: October 16, 2015
    • Regression - outstanding batch issue. Fixed in version 3.6.4.

    Bug Fixes

    • Enterprise & Community
      • [AER-4521] - (KVS) Batch crash caused by incorrectly setting member after batch data structure is freed.
      • [AER-4433] - (KVS) Improve assert caused by spurious prole delete - correctly upstream assert to master.
      • [AER-4480] - (PACKAGING) Install correct tools dependency on RedHat-ish machines with Python 2.7.

    Known Issues

    Updates

  • 3.6.2
    Release Date: October 9, 2015
    • Regression - outstanding batch issue. Fixed in version 3.6.4.

    New Features

    • Enterprise & Community
      • [AER-2757] - (CLUSTERING) Introduce a "service-alumni-reset" command to reset services-alumni to services.
      • [AER-3657] - (CLUSTERING) Add support for mesh clustering with each Aerospike node isolated behind their own NAT.

    Improvements

    • Enterprise & Community
      • [AER-4451] - (KVS) Deletes no longer counted as writes in stats.
      • [AER-4468] - (KVS) Ensure generation and void-time are returned to the client for write requests in multi-node clusters.
      • [AER-4447] - (PACKAGING) Various improvements to Debian init script.

    Bug Fixes

    • Enterprise & Community
      • [AER-4433] - (KVS) Spurious prole delete causes failed assertion.
      • [AER-4443] - (KVS) Records without a TTL incorrectly get default TTL after cold start.
      • [AER-4446] - (KVS) Crash in rare situation - multiple operations on bins containing non integer values (storage-engine device).
      • [AER-4455] - (KVS) Batch read race condition during cluster migration causes crash.
      • [AER-4457] - (KVS) Honor zero void-time during conflict resolution when generations are the same.
      • [AER-4458] - (SINDEX) Crash occurred while performing list and map queries that return list or map bins.
      • [AER-4453] - (LDT) On prole writes, the updated subrecords should share same version as parent.
      • [AER-4472] - (LDT) The llist.filter method in ldt/lib_llist doesn't call the filter function anymore.
    • Enterprise Only
      • [AER-4466] - (XDR) UDF deletes not shipped through XDR.
      • [AER-4489] - (XDR) Deletes generation not correctly passed through.

    Known Issues

    Updates

  • 3.6.1
    Release Date: September 24, 2015
    • Regression - outstanding batch issue. Fixed in version 3.6.4.

    New Features

    • Enterprise & Community
      • [AER-2806] - (KVS) Provide set-scoped "objsz" histograms (storage-engine device), TTL histograms (formerly not always available) & real-time memory usage (data-in-memory).
      • [AER-3518] - (KVS) Increase write buffer cache efficiency - separate client write from defrag re-write.
      • [AER-3792] - (PACKAGING) Added support for run levels in RPM packaging.
    • Enterprise Only
      • [AER-4422] - (XDR) Skip windowshipping mode if only single destination.

    Improvements

    • Enterprise & Community
      • [AER-4298] - (KVS) Removed unused vinfo data structure and deprecated 'allow-versions'.
      • [AER-4434] - (KVS) Remove unnecessary warning in single-bin configuration for "sizing unused bin".
      • [AER-4435] - (KVS) Added "disable-eviction" option to disable evictions for specific sets.
      • [AER-4436] - (KVS) Deprecated count-based set-eviction.
      • [AER-4437] - (KVS) Deprecated writes-reply histogram.
      • [AER-4407] - (UDF) Add log entries when UDF modules are registered or removed.
      • [AER-4415] - (SINDEX) Remove redundant warning line for "Number of sbins found for 1 sindex is not 1".
      • [AER-4438] - (AQL) Added "explain" for primary key functions.
      • [AER-4439] - (AQL) Describe-index info call specify index type as NUMERIC/STRING (instead of TEXT and SIGNED INT).
      • [AER-4440] - (Backup/Restore) Ability to save system meta data - sindex and udf meta data.
      • [AER-4441] - (Backup/Restore) Ability to backup/restore binary data w/o b64.
    • Enterprise Only
      • [AER-4357] - (XDR) Added ability to dynamically add dc-int-ext-ipmap.

    Bug Fixes

    • Enterprise & Community
      • [AER-4378] - (KVS) Correctly fail transaction when invalid data type is sent for operations.
      • [AER-4381] - (KVS) Fix scan crash when LDT objects of size 2-4meg are in system.
      • [AER-4251] - (UDF) Stream UDF not returning bytes values.
      • [AER-4288] - (LDT) Improve subrec digest picking randomization.
      • [AER-4426] - (LDT) Github issue #93 - Fix incorrect prole delete originated from LDT.
      • [AER-4442] - (SINDEX) Closing potential sindex ref count mismatch which cause index to be in "D" state.
      • [AER-4406] - (AQL) Fixed output so it is consistent with the client API.
      • [AER-4404] - (PACKAGING) Fix default permission on CentOS 7 server install.
    • Enterprise Only
      • [AER-4423] - (XDR) Fixed the termination condition of walking the window list.

    Known Issues

  • 3.6.0
    Release Date: August 31, 2015
    • Regression - batch related crash during node rebalancing. Fixed in 3.6.2.
    • Regression - extra sizing unused bin log line printed in single-bin config. Fixed in 3.6.1.
    • [AER-2903] - (KVS) Batch-read improvement.
      • Batch-read requests are now proxied during cluster changes.
      • Handle mixed namespace/bin selections in one batch call.
      • Performance improvement.
    • [AER-2986] - (KVS) Scan improvement.
      • Concurrent scan jobs are interlaced, allowing progress on all scans.
      • Add ability to promote a scan to high-priority so it can be processed immediately.
      • Add ability to change number of scan threads during scans.
      • Performance improvement.
    • [PROD-265] - (KVS) Support for Double data-type.
      • Roll-back not supported once Double data inserted.
      • Roll-back require cold restart if no Double data inserted.

    New Features

    • Enterprise & Community
      • [AER-2903] - (KVS) Batch-read improvement.
      • [AER-2986] - (KVS) Scan improvement.
      • [PROD-265] - (KVS) Support for Double data-type.
      • (ASADM) Introduce asadmin 0.0.1, alternative to asmonitor.
    • Enterprise Only
      • [AER-3808] - (XDR) Added a new get-dc-config info command.

    Bug Fixes

    • Enterprise & Community
      • (KVS) Refactoring of write code path for operations and error handling.
      • [AER-3720] - (KVS) Github #71 Create info threads as detached.
      • [AER-3832] - (KVS) Fail transaction that tries to store key with single-bin data-in-memory configuration.
      • [AER-4026] - (KVS) Fix incorrect processing of interface name resulting in bogus node-id generated.
      • [AER-3968] - (KVS) Fix negative heartbeat accounting.
      • [AER-3946] - (KVS) Fix crash when non-virtual external address does not match interface ip.
      • [AER-3993],[AER-3897] - (KVS) Fix crash caused by invalid message operations.
      • [AER-3810] - (KVS) Allow reads and low consistency writes during cluster integrity situations.
      • [AER-4237] - (KVS) Fix for err_sync_copy_null_node.
      • [AER-3716] - (KVS) Add transaction timeout error statistics.
      • (KVS) Return void-time to client on write and UDF transactions.
      • (KVS) Fix 'operate' transactions so read-operations are executed in-sequence.
      • [AER-4151] - (SINDEX) Fix leak of file descriptors when query run against a non-existent set.
      • [AER-3924],[AER-3806] - (SINDEX) Stat & configuration improvement - adding query-thread, query-batch-size, query-priority, query-threshold, query-untracked-time, to be settable from configuration file.
      • [AER-3725],[AER-4062] - (SINDEX) Use query transaction structure from a pool.
      • [AER-4473] - (LDT) Perform bound check before pre-allocate list to store result in LLIST range.
      • [AER-3785] - (UDF) Fix incorrect record access via UDF when record is already expired but not removed yet by background thread.
      • [AER-3042],[AER-4182] - (UDF) Increase the bin limit for UDFs to 512. Fail out if a UDF attempts to access a record with more than 512 bins.
      • [AER-3716] - (UDF) Correctly clean up failed UDF transactions. Improper cleanup can cause query/scan UDF to hang.
      • (UDF) Fix crash caused by lua error() calls with non-string argument type.
      • [AER-3051],[AER-3052],[AER-3752],[AER-4162] - (PACKAGING) Fix build on amazon OS & debian8 build. Create 'aerospike' user on rpm distro's.
      • [AER-3483] - (KVS) Add meta data print to json format.
      • (AQL) Add option of REPLICA_ANY.
      • [AER-3556] - (AQL) Fix SET RECORD_TTL override namespace default ttl.
      • [AER-3807] - (AQL) Handle quote around bin name on an equality query.
      • [AER-3734] - (AQL) Fix double quote escape: Changed json output to use libjansson so all other escapes should be correct too.
      • [AER-3794] - (AQL) Fix setting of LuaPath.
      • [AER-3830] - (BACKUP) Honor '-s' option for keys.
    • Enterprise Only
      • [AER-3808] - (XDR) XDR config and stats clean up. Include name-pipe information on get-config call.
      • [AER-3664],[AER-4058] - (XDR) Fix crash when accepting connections if we run out of OS file descriptor limit, uninitialized namespace, uninitialized async queue.
      • [AER-4171] - (XDR) Fix thread usage in single get mode.

    Known Issues

  • 3.5.15
    Release Date: July 15, 2015

    Maintenance Release

    Bug Fixes

    • Enterprise & Community
      • [AER-3988] - (LDT) Fixed race conditions during migration and replication of LDT records.
      • [AER-3780] - (SCAN) Fixed regression of scan aggregations introduced in 3.5.8
      • [AER-4062] - (SINDEX) Fixed regression of query performance due to 'pre-reserve-qnodes' setting, introduced in 3.5.8.
      • [AER-3882] - (SINDEX) Fixed incorrect statistics for secondary indexes.
    • Enterprise Only
      • [AER-4058] - (XDR) Check initialization of async queue.

    Known Issues

  • 3.5.14
    Release Date: June 18, 2015

    Maintenance Release

    Bug Fixes

    • Enterprise & Community
      • [AER-3724] - (KVS) Clean up cluster visibility logging.
      • [AER-3684] - (KVS) Add checks to decompressed packet.
      • (KVS) Fixed shadow device log statement.
      • [AER-3725] - (SINDEX) Performance improvement - remove unnecessary memsets in qctx.
      • [AER-3709] - (SINDEX) Fixing mem leak in query engine with list/map.
      • [AER-3704] - (LDT) Deletes should be propagated to the prole on update properly; fix journalling delete for subRecords.
      • [AER-3705] - (LDT) Fix log line for subrec open failure.

    Known Issues

  • 3.5.12
    Release Date: May 28, 2015
    • Better Protection against unexpected protocol messages.
    • Improve Cloud Environment Support for using network devices and adapting firewall rules.
    • LDT backup support.
    • Improve XDR operational ease-of-use.

    Improvements

    • Enterprise & Community
      • [AER-3541] - (KVS) Add option for sending of keep-alive packets on all inter-node sockets, for deployments with firewall rules which actively reap idle connections.
      • [AER-3557] - (KVS) Add device shadowing functionality, for persistence on network devices in addition to ephemeral storage.
      • [AER-1801] - (SCAN) Added scan-abort-all.
      • [AER-3609] - (LDT) Support for LDT backup.
      • (AQL) Add EDIGEST and DIGEST as option of performing operation based on encoded and non-encoded digest string.
    • Enterprise Only
      • [AER-3603] - (XDR) Added namespace-level config option to disallow xdr/none-xdr writes.
      • [AER-3405] - (ACL) Added data-admin pre-defined role, for registering UDF and creating secondary index.

    Bug Fixes

    • Enterprise & Community
      • [AER-3633],[AER-3616],[AER-3688],[AER-3538] - (KVS) Improve unexpected as_msg - compressed as_msg; namespace too long, extra data than specified.
      • [AER-3662] - (KVS) Improve unexpected as_info - protect against info command with ':' and not terminated with '\n'.
      • [AER-3683] - (KVS) Fail on configuration with replication-factor 0.
      • [AER-3598] - (KVS) Enforce maximum device size for both files and raw devices (2TB). Minor SSD clean up.
      • [AER-3615] - (KVS) Logging fix - Fix cf_*_binary() to be safe against > 1kb. Refactor rw_cleanup(). Refactor as_transaction_error().
      • [AER-3437] - (SINDEX) Fix potential duplicate results returned on query by range due to entries not garbage collectible.
      • [AER-3573] - (SINDEX) Fix query failure when clients send setname=NULL (instead of no setname).
      • [AER-3609] - (SCAN) Support LDT elements. Improve message buffer growing scheme.
      • (SCAN) Set the client socket file descriptor to blocking during a scan, to avoid CPU-intensive retry loops.
      • (UDF) Do not send replica message on UDF failures on not-found files.
      • [AER-3594] - (LDT) Fix failed element delete caused by double-split leaf no longer connected.
      • (LDT) Add some more parameter check for the LLIST functions. Print parent record on open failure.
      • (LDT) Return proper error code if empty string is sent and binName or the key Type mismatch across multiple operations. Fix error code conversion.
      • [AER-3620] - (AQL) Fix for authentication fail error message logging during cluster connect for security enabled server.
    • Enterprise Only
      • (XDR) Setting of xdr-namedpipe-path is now dynamic. This avoids the need to restart ASD for XDR config changes.
      • [AER-3624] - (XDR) Disallow digest log file size change.

    Known Issues

  • 3.5.9
    Release Date: April 21, 2015
    • Fixed Regression introduced in 3.5.4, where queries do not respond to the client when aggregations fail.

    Improvements

    • Enterprise & Community
      • [AER-3529] - (KVS) added info protocol 'replicas-all' to fetch client map for all replicas simultaneously. This allows clients to read from prole replicas with any replication factor.

    Bug Fixes

    • Enterprise & Community
      • [AER-3532] - (KVS) Increase efficiency of tracking master/prole object counts.
      • [AER-3533] - (SINDEX) Regression from 3.5.4 - Fix the bug where query system does not respond back to the client when aggregation functions aren't found.
      • [AER-3515] - (SINDEX) 1. Instrumentation around sindex reservation. 2. Zombie sindex should be shown in 'show sindexes'
      • [AER-3514] - (SINDEX) Allow sindex deletion if index name starts with a white space.
      • [AER-3451] - (SCAN) Improve scan job kill - when a scan job is killed, abort processing immediately instead of waiting for partition.
      • (LDT) Fix LDT exception when invalid data type passed in for LLIST.range() calls.
      • (LDT) Fix error caused when LDT record not initialized via an 'update' call.
      • (LDT) Fix subrecord count on fast restart.
      • [AER-3550] - (PACKAGING) Properly install and remove the 2.x Aerospike Python client Library on all supported platforms
      • [AER-3484] - (ASCLI) Fixed - modified how bins are being iterated over.
    • Enterprise Only
      • (AQL) Generate error if password keyword missing in create user command.

    Known Issues

  • 3.5.8
    Release Date: April 7, 2015
    • Performance enhancements:
      • Clustering - Migration performance improved by modifying initial partition balancing scheme for nodes joining a cluster.
      • Scans - Scanning of large data-sets improved by buffering and sending chunks of records, rather than buffering entire partition.
      • Queries - Query results will no longer busy-wait while waiting to send results to the client, if the client is not consuming the records.
      • LDT - Paging objects based on page size (bytes), rather than object count. Default page size is 8 KB. New find_first/last/range API.
    • Tooling and Instrumentation:
      • JEMalloc Analyzer - Scripts that allow you to analyze JEMalloc related stats from Aerospike.
      • ASMalloc double-free detector - An ASMalloc enabled Aerospike server will log when a double-free is detected.

    Improvements

    • Enterprise & Community
      • (KVS) Migration Performance Enhancement - Changed the initial partition balancing scheme so that absent partitions remain absent until a node joins a cluster or is contacted by a client.
      • (SINDEX) Query management for slow clients . Introduce thread-pools to handle send w/ EAGAIN. Pause a query if there is more than X number of network packets outstanding.
      • [AER-3377] - (SCAN) Break scan results into reasonably sized proto blocks.
      • (LDT) Leaf node (data node) split based on configurable pageSize (bytes) rather than number of entries, default at 8k.
      • (LDT) Add new function find_first/last/range, with filtering capability.

    Bug Fixes

    • Enterprise & Community
      • [AER-3453] - (KVS) Changed default nsup-delete-sleep from 0 to 100 microseconds to avoid large number of objects in set-delete.
      • (KVS) Changed size of write request hash from 16K to 32K.
      • [AER-3297] - (KVS) Mesh - Increase the interval between re-trying heartbeat connections.
      • [AER-3465] - (KVS) Release JEMalloc Developer Tools.
      • (KVS) Cleanup - removed unused dupl_pvinfo array from partition structure. (Recovers 12Mb of RAM per namespace).
      • [AER-3125] - (KVS) Run-time recovering option for out-of-storage situation. On increasing defrag-lwm-pct, queue all newly eligible wblocks for defrag. Also, allow defrag to use reserve wblocks when other writer threads can't.
      • (KVS) as_malloc based double-free detector
      • [AER-3412] - (KVS) Added diagnostic code to check for non-master records after emptying set(s).
      • (LDT) Fix the corner case of child node being inserted at the first position.
      • (LDT) Fix version setting code in prole write code path. Fix proxy code to clean up write request.
      • (SCAN) Make sure asinfo properly reports the result of a scan-abort command.
      • [AER-3446] - (SINDEX) Fix crash caused by not checking the bound on selected bin name size.
      • [AER-3413] - (SINDEX) Sindex creation ticker to represent actual namespace %.
      • (SINDEX) Adding query-short-queue-size and query-long-queue-size.
      • (SINDEX) Query management for slow clients . Introduce thread-pools to handle send w/ EAGAIN. Pause a query if there is more than X number of network packets outstanding.
      • (SINDEX) Qnode hole closing.
      • [AER-3321] - (AGGREGATION) Change scan aggregation to use normal index reduce.
      • (PACKAGING) Enable building on Fedora.
    • Enterprise Only
      • (AQL) Fix clobbering of user name on set password when FOR clause omitted.

    Known Issues

  • 3.5.4
    Release Date: March 10, 2015
    • NOTICE A regression was introduced in 3.5.4 that caused queries to not respond to the client when aggregations fail. A fix was made in 3.5.9.

    Bug Fixes

    • Enterprise & Community
      • [AER-3393] - (KVS) Fix potential crash caused by divide-by-zero in expiration thread stat calculation.
      • (KVS) Add a signal handler for SIGILL. Gracefully handle unexpected return value of signal registration.
      • [AER-3395] - (KVS) Only apply delete generation check if delete is direct from client.
      • [AER-3378] - (KVS) Improve Socket-Related Error Handling.
      • [AER-3355] - (TOOLS) Fix digest operations in CLI.
      • (UDF) Support Lua list/map 'create', which will be portable to all platforms. The previous 'new' was not easily portable to Java/C#.
      • [AER-3314] - (UDF) Improve usage of the Lua debug hook used for timing record UDFs.

    Known Issues

  • 3.5.3
    Release Date: February 23, 2015
    • Maintenance release.

    Bug Fixes

    • Enterprise & Community
      • [AER-3343] - (KVS) Fix batch bin-filtering: return empty record when record exist and bin does not.
      • [AER-3332] - (KVS) Change permissions of log file to 644.
      • [AER-1376] - (KVS) Add generation enforcement option for record deletion.
      • [AER-3259] - (KVS) Heartbeat tip: correctly error out when a name is supplied instead of an ip address.
      • [FORUM-963] - (KVS) Fix g_service_str initialization race condition.
      • (LDT) Fix as_rec reference memory leak.
      • [AER-3307] - (UDF) Server statistics fix.
    • Enterprise Only
      • (AUDIT) Fix bug in assembling data transaction log filter scopes.
      • (ACL) Fix a couple of improperly sized allocations in role permission management.

    Known Issues

  • 3.5.2
    Release Date: February 13, 2015
    • Security enhancements; consolidation of Large Data Types (LDTs).

    New Features

    • Enterprise & Community
      • (TOOLS) Backup/restore/aql using new C client.
    • Enterprise Only
      • (ACL) Support namespace/set level security. Support user defined roles. Support access log at namespace/set level.

    Bug Fixes

    • Enterprise & Community
      • [AER-3250] - (KVS) Improved latencies during nsup - use dual tree locks so reads and overwrites are not blocked while reducing a partition tree.
      • [AER-3290] - (KVS) Increase the priority of migrate xmit thread kill messages. Allow migrate-max-num-incoming to be dynamically set to 0.
      • (KVS) Added sample configuration files.
      • [AER-3191] - (KVS) Added proto error code AS_PROTO_RESULT_FAIL_FORBIDDEN, currently for failing writes during set-delete.
      • (KVS) Increasing thread count for cold start eviction to fully exploit 24-core machines.
      • [AER-3172],[AER-3091] - (KVS) Minor stats fixes. Added stats 'nsup-cycle-duration' and 'nsup-cycle-sleep-pct'.
      • (KVS) Fix Scan/Query/Batch to not return empty record when the record does not contain the requested bin.
      • [AER-3111] - (KVS) Fix to allow core dump - modified signal handling exit by re-raising signals with default handlers for signals that crash.
      • (KVS) Do not return storage object size histogram (hist=objsz) in non-persisted namespace.
      • (LDT) Large Data Type (LDT) functionality consolidation: LMAP, LSTACK and LSET data types are planned for deprecation. Developers using any of these three types are urged to use LLIST instead. The LLIST API will remain as is.
      • (LDT) Lua module cleanup and enhancements 1. Removed unnecessary field in the property map 2. Cleaned up configuration module to only have relevant fields 3. Removed all the misc. tests and packages.
      • (LDT) Do not expire sub-record at boot time.
      • (TOOLS) Backup/restore/aql using new C client.
      • (TOOLS) AQL - Fix to handle queries with no results.
      • (SINDEX) Fix rare crash on sindex destroy due to incorrectly reserving the sindex.
      • [AER-3192] - (UDF) Record-UDF all bin deletes in a record are not updated in prole.
      • (UDF) Fix leak in hashmap entry removal.
    • Enterprise Only
      • [AER-3219] - (XDR) Enable-xdr is not honored after sets subsection. Fix lastshiptime issue. Stats fixes & enhancements.
      • [AER-3222] - (XDR) Fixed wrong data center lag values.

    Known Issues

  • 3.4.1
    Release Date: January 12, 2015
    • Enhancements/Stabilization for Large Data Types; Support for Scan Aggregation.

    New Features

    • Enterprise & Community
      • (KVS) Support for aggregation on scan.
      • (LDT) Enhancement for migration. AER-2655 Disallow any LDT operation when 'ldt-enabled' configuration is not on.
      • [AER-3073] - (UDF) Add an info call to clear the Lua cache on the node. ['asinfo -v udf-clear-cache:'].

    Bug Fixes

    • Enterprise & Community
      • [AER-3048] - (KVS) Paxos - Ensure the Paxos proposal from the node with the highest node ID will always be accepted.
      • [AER-3068] - (KVS) Eliminate rare small memory leak and also symptom message 'Illegal state in read request (second call)' (overwrite of tr->msgp).
      • [AER-3080] - (KVS) Increase MAX service-threads to 256 and transaction-queues to 128. Increase MAX_FABRIC_WORKERS from 64 to 128.
      • [AER-3100] - (KVS) Namespace too long for 31 char namespace.
      • [AER-3113] - (KVS) Remove unnecessary assert on 4095 select bin read.
      • (KVS) as_hashmap reallocation bug fix.
      • [AER-3109] - (AGGREGATION) Add record access function record.setname(), record.digest() and record.key() in streamUDF.
      • (SINDEX) Fix crash when system has > 127 sindexes.
      • [AER-3115] - (TOOLS) To avoid conflict, moved daemon.py into citrusleaf_graphite.py.
      • (AQL) Enable ability to perform get and delete based on digest.
      • (ASADMIN) Version 0.0.7. added 'info sindex'.

    Known Issues

  • 3.4.0
    Release Date: December 8, 2014
    • Since going open source earlier this year with Aerospike version 3.3.5, we’ve added a myriad of features and fixes. Though this version only includes one feature (enhancing defragmentation) and a handful of fixes, we wanted to end 2014 with a fresh new version: Aerospike 3.4.0.

    New Features

    • Enterprise & Community
      • [AER-3067] - (KVS) Defrag enhancement - added defrag-queue-min configuration parameter to specify delay in processing defrag-eligible storage blocks. This should benefit particular usage models in which storage blocks (wblocks) continue depleting quickly and significantly after crossing their defrag-eligibility threshold.

    Bug Fixes

    • Enterprise & Community
      • [AER-3071] - (KVS) Discover minimum size needed for device IO operations using O_DIRECT.
      • [CASE-1793] - (UDF) Use 64-bit counters for tracking Lua cache attempts/misses.
      • [AER-3057] - (QUERY) Memory leak fix for aggregation, when client closes connection before processing all the results; aggregation digest array leak fix.
      • [AER-3017] - (QUERY) Fix rare race condition where an in-flight record may not get indexed on an index creation.
      • [AER-3070] - (KVS) Init script fix for shmall/shmax setting.
    • Enterprise Only
      • [AER-3065] - (ACL) LDT UDFs are recognized as read or write operations.

    Known Issues

  • 3.3.26
    Release Date: December 3, 2014
    • Support for per-transaction based policy for write-commit-level, read-commit-level, and read-replica.

    New Features

    • Enterprise & Community
      • [PROD-396] - (KVS) New per-transaction policy - (a) write-commit-level ('master' or 'all') (b) read-commit-level ('master' or 'all') (c) read-replica ('master' or 'any').
      • [AER-2449] - (KVS) Add 'virtual' as an option to network access-address, to allow NAT ip which are not defined on the node's network interface such as AWS
      • [AER-1025] - (KVS) Support batch bin name filtering.
      • [AER-3038] - (LDT) Support range deletes for LargeList
      • [AER-1047] - (UDF) Using lua-jit for Lua.
      • [AER-2946],[AER-2947] - (UDF) List feature enhancement - added insert(), remove(), concat(), and trim().
    • Enterprise Only
      • [AER-3024] - (XDR) Added the ability to forward XDR writes per namespace (using ns-forward-xdr-writes).

    Bug Fixes

    • Enterprise & Community
      • (KVS) Write version and help text to stdout (as opposed to stderr) and return 0 (as opposed to 1) from main() on these cases.
      • [AER-2923] - (KVS) Deprecated some expiration parameters - nsup-queue-hwm, lwm, escape, replaced with nsup-delete-sleep (microseconds, default 0).
      • [AER-3030],[AER-3008] - (KVS) Removing 'migrate-priority' from stats; deprecated config item 'high-water-pct'.
      • (KVS) Paxos Stability - Changed 'dun all' and 'undun all' command behavior to reform into a single cluster; send PREPARE COMMIT and CONFIRM messages only to the succession list, to avoid non-cluster members (and dead nodes) from getting into the succession list; Ensure all nodes in the succession list are alive.
      • (KVS) Fixed as_hashmap constructor to handle 0 capacity correctly. Fixes in as_list - toString and set methods.
      • [AER-2948],[AER-2952] - LMAP Fix for Overwrite; AER-2948 - Fixed LDT Type Fail; AER-2952 - Added LMAP exists() function. LDT Updates: Improved LLIST Delete handling, improved SubRec handling.LDT Control structure check consolidation.
      • (LDT) Fix LDT delete crash.
      • [AER-3040] - (LDT) Improve LDT sizing through use of configurator; default to no compact-list so inserts of large elements do not fail.
      • (SCAN) Scan performance improvement - use a bigger initial bufbuilder size. AER-2971 - Improvement in scan error return codes.
      • (PACKAGING) Change asinstall to use 'Uvh' instead of 'ivh'.
      • (PACKAGING) Added cleangit Makefile target to remove all none git tracked files.
      • [AER-2862] - (CLI) Resolved intermittent CLI error; Fix parsing of -d (digest) parameter.
      • (AQL) Support 64-bit integers; AER-2929 - Fix Json rendering crash; AER_2664 - Fix show-bins formatting; AER-2784 - generic fix for invalid commands."
      • [AER-2927] - (AQL) Add AQL support to display keys coming back for records.
      • [AER-2768] - (ASADMIN) Fixed issue with 'citrusleaf_stat' references.
      • [AER-2719],[AER-2691] - (BACKUP) for key storage.
    • Enterprise Only
      • (KVS) Correctly detect and handle non integer data on fast restart with data-in-index configuration.
      • [AER-2889] - (XDR) Handle the issue of a permanently failed node for XDR; Fix the possibility of sending a junk setname to destination during failednode/window processing.

    Known Issues

  • 3.3.22
    Release Date: October 31, 2014
    • Maintenance release.

    New Features

    • Enterprise & Community
      • (TOOLS) New asadm tool (beta).

    Bug Fixes

    • Enterprise & Community
      • [AER-2920] - (TOOLS) Rename asadmin to asadm to avoid installation conflict on Amazon EC2 (Amazon Linux OS).

    Known Issues

  • 3.3.21
    Release Date: October 14, 2014
    • Maintenance release.

    New Features

    • Enterprise & Community
      • [AER-2758] - (KVS) Added cold-start-empty configuration boolean to ignore reading data from raw devices.
      • (LDT) LList.update_all() function.
      • [AER-2772] - (AQL) Allow aql to set fail_on_cluster_change_policy for scans.
      • (TOOLS) New asadmin tool (beta).

    Bug Fixes

    • Enterprise & Community
      • [AER-2826] - (KVS) Minor logging changes in paxos, heartbeat.
      • (KVS) Enhanced hashmap implementation.
      • (KVS) Better logging around the defrag generation mismatch and related occurrences.
      • (KVS) Fix badly formed transaction message with bad namespace length.
      • [AER-2769] - (KVS) Fix memory accounting - the overhead of the as_bin_space struct is no longer included if there are no bins.
      • [AER-2728] - (KVS) Treat generation 0 consistently.
      • (LDT) Fix record type reset to allow warning-free sub-record delete.
      • (LDT) Respond 'record not found' as protocol error 2. Respond 'element not found' as protocol error 125.
      • [AER-2842] - (SINDEX) Fix for crash where multiple queries share same TRID.
      • [AER-2802] - (SINDEX) Fix possible crash on index removals.
      • [AER-2778] - (SINDEX) Range queries return less results than expected for keys with > 32 elements.
      • [AER-2748] - (SINDEX) Improve write performance on system w/ sindex - Maintain a binid_has_sindex lookup.
      • (UDF) Log warning when UDF called with more than 20 arguments.
      • [AER-2872] - (UDF) Fix crash on scan and query record UDF in duplicate resolution - jobType not saved.
      • [AER-2787] - (UDF) UDF-list calls may potentially fail all info calls on a node.
      • (UDF) Fix potential crash due to uninitialized set name for internal query transaction. Improve performance by reducing context lock scope.
      • [AER-2382] - (SCAN) Fixed scan job ref-counting. Fix possible causing excess response sent to client.

    Known Issues

  • 3.3.19
    Release Date: September 9, 2014
    • Install script renamed to asinstall to avoid potential conflicts with other install scripts.
    • MESH - Allow multiple seed addresses in network section.
    • Storage Write Durability Enhancements.
    • Other bug fixes.

    New Features

    • Enterprise & Community
      • [AER-2654] - (KVS) For Mesh HB, allow multiple seed addresses in network section (mesh-seed-address-port 192.168.1.215 3002).
      • [AER-2504] - (KVS) Added fsync-max-sec namespace storage configuration to specify fsync interval (default=0, never fsync). Add related storage-benchmark histogram.
      • (KVS) Added enable-osync namespace storage configuration to set O_SYNC for raw devices.
      • (KVS) Added flush-max-ms namespace storage configuration to flush inactive in-memory write buffer (swb) to device (default=1000ms, 0 means never flush).
      • [AER-1487] - (UDF) Bin iteration in UDF - add record.bin_names() function.
      • (UDF) Lua API - Adding map.remove().
      • [AER-2727] - (LDT) Add LLIST Update() function.

    Bug Fixes

    • Enterprise & Community
      • [AER-2662] - (KVS) Maintain Paxos Succession List in Descending Sorted Order.
      • [AER-2663] - (KVS) Fix incorrect node 'dead' state due to node-local blip.
      • [AER-847] - (KVS) Better error handling - added errors for no/unknown namespace (20) and bin name too long or exceeding quota (21).
      • [AER-2110] - (SINDEX) Making query threads detachable.
      • [AER 2715] - (SINDEX) Update sindex histogram correctly.
      • [AER-1549] - (UDF) UDF-list reads from system metadata instead of from directory. Restrict max UDF content length to 1MB.
      • [AER-2712] - (UDF) Fix crash when UDF executes on a record which does not exists.
      • (LDT) Stability fixes.
      • [AER-2340, AER-2339] - (INFO) Info service prints only when service is running; check for external-address validity.
      • (PACKAGING) Rename installer script to 'asinstall' to not shadow system command 'install'.
      • (PACKAGING) Change Makefile to take argument for optimization level.

    Known Issues

  • 3.3.17
    Release Date: August 26, 2014
    • New defrag algorithm with simplified configuration and tuning.
    • New packaging and simple install scripts provided in the tar ball, simply run 'sudo ./install'.
    • Beta release for Security features in Enterprise Edition only.

    New Features

    • Enterprise & Community
      • (KVS) Queue based defrag algorithm.
      • [AER-2278] - (UDF) Support dropping of stored-key via UDF
      • (UDF) Enhance byte-array access interface to support both little-endian and big-endian arrays; add bytes.get_var_int().
      • (PACKAGING) Generate check-sum for tgz's.

    Bug Fixes

    • Enterprise & Community
      • [AER-435],[AER-943],[AER-2617],[AER-2626] - (KVS) mesh stability fixes.
      • (KVS) Storage space check bug fix when storage under min-avail-pct - check against free wblock queue.
      • [AER-2657] - (KVS) Performance enhancement - removing redundant memmove calls in fabric system.
      • [AER-2579] - (KVS) Histogram accuracy cleanup (nanoseconds).
      • [AER-2652] - (KVS) Key storage - for 2.0 C clients, do not incorrectly save key on proxy requests.
      • [AER-2588] - (KVS) (non-master log line) update.
      • (KVS) Fixed rare cf_crash() when process fail to fork.
      • (KVS) as_hashmap 'NULL' map Parameter Checks.
      • (KVS) Fixed get-config info command to work for namespaces with names longer than nine characters.
      • [AER-2695],[AER-2639],[AER-2656] - (UDF) Fix udf storage sizing.
      • [AER-2678] - (UDF) Use as_nil to represent nil Lua stack values.
      • [AER-2647],[AER-2648],[AER-2655] - (LDT) Improve Search mechanism in LLIST; Fix Set/Get capacity API calls in LMAP, LSET, LLIST; Improve lstack management of capacity settings; memory leak fix due to reference counts.
      • (LDT) Stability fixes - add validate() function. log minimization.
      • [AER-2682] - (SINDEX) Fix rare record miss on sindex rebuilding during node restart for SSD configuration.
      • (KVS) Init script killproc change.
      • (PACKAGING) Add installation scripts for easy install and for security dependencies (bcrypt).
    • Enterprise Only
      • (KVS) Added logging for iparticle state on data-in-index check on fast restart.
      • [AER-2665] - (XDR) Fixed config parsing issue where xdr settings cannot come after storage sub-section.
      • [AER-2579] - (XDR) XDR does not ship record deletes via udf.

    Known Issues

  • 3.3.12
    Release Date: July 24, 2014
    • UDF and LDT features, bug fixes.

    • New Dependencies for tools package: python-devel, pip, and gcc.

    • Further details under the server installation instructions.

    New Features

    • Enterprise & Community
      • (LDT) Server Support for Range query for LargeList.
      • [AER-2545] - (UDF) Ability to set TTL in via UDF.

    Improvements

    • Enterprise & Community
      • [AER-2493] - (PACKAGING) Enhance rhel init script to accommodate rhel7.

    Bug Fixes

    • Enterprise & Community
      • [AER-2218] - (KVS) Ability to dynamically read network interface name.
      • [AER-2588] - (KVS) Fix assertion crash seen in rare cluster integrity situation.
      • (SINDEX) Fix gc histograms to only output once.
      • [AER-2602] - (SINDEX) Fix for possible crash in write_delete_local code path when records have secondary index.
      • (SINDEX) Garbage collector performance enhancement, counter fix; query microbenchmarks.
      • [AER-2578] - (SINDEX) Possible orphaned sindex entry on prole writes.
      • [AER-2601] - (UDF) Fix for hidden flag in bins.
      • [AER-1549] - (UDF) UDF-list reads from system metadata instead of from directory.
      • [AER-2541,[AER-2444],[AER-2550] - (UDF) Stability bug fixes.
      • [AER-2557] - (LDT) Fix crash for LDT on data-on-disk configuration.
    • Enterprise Only
      • [AER-2579] - (XDR) XDR does not ship deletes initiated from UDF.

    Known Issues

  • 3.3.9
    Release Date: July 15, 2014
    • Fix for single-bin configuration memory stomp causing server crash.
    • ascli tool - crash on query-kill/query-list/scan-kill/scan-list calls.

    Bug Fixes

    • Enterprise & Community
      • [AER-2563] - (KVS) Fixes for single-bin and data-in-memory bug fix - bin initialization no longer writes past end of allocated enclosing as_index structure.

    Known Issues

  • 3.3.8
    Release Date: July 9, 2014
    • In single-bin configuration, memory stomp causing server crash.
    • ascli tool - crash on query-kill/query-list/scan-kill/scan-list calls.

    New Features

    • Enterprise & Community
      • (KVS) Adding 'cache-read-pct' in namespace stats.

    Bug Fixes

    • Enterprise & Community
      • (KVS) Log edition & build on SIGABRT.
      • [AER-2531] - (KVS) Fix rare timing related crash on startup, seen on REL7.
      • (KVS) Fixed storage-engine memory paxos bug introduced in 3.3.5.
      • [AER-2469],[AER-2508] - (KVS) Stability fixes - log format fix; better error message when arena stage allocation fails.
      • [AER-2485] - (KVS) Expand command-line help and usage text.
      • [AER-2551] - (UDF) Fix crash caused by no arguments passed in.
      • (UDF) Fix missed generation increment for UDF with updates.
      • [AER-2534] - (UDF) Fix registration of .so UDF modules.
      • [AER-2175] - (UDF) Fix bug which causes UDF transactions to never timeout on server side.
      • [AER-2277],[AER-2278] - (UDF) Support key storage and checking via UDF operations.
      • [AER-2434] - (UDF) Delay commit to storage of aerospike:update until UDF finished. Enhance the parameter and validation check for udf_record/udf_aerospike.
      • (QUERY) Support aggregation error propagation to client.
      • [AER-2431] - (QUERY) Replica bin deletion bug fix for records with sindex.
      • (LDT) Stability bug fixes.
      • [AER-2463] - (LDT) Return hidden bin type as AS_PARTICLE_TYPE_NULL when return to client. Other stability fixes.
      • [AER-2269],[AER-2402],[AER-2410],[AER-2436],[AER-2456],[AER-2507],[AER-2533] - (AQL) Bug-fix for db operations using integer keys. Stability fixes.
      • (BACKUP) Added support for PHP,ERLANG,LUA type blob backup/restore.
      • [AER-2483] - (PACKAGING) Fix GUI install of ubuntu12.
      • (PACKAGING) Fix conflict of tool & aerospike.
      • [AER-2341] - (ASMON) Use master-objects stat in Namespace and display object count as numbers with comma as 1000 separator.
    • Enterprise Only
      • [AER-2506] - (XDR) Fix crash caused by FD_SET in glibc-2.15+ (ubuntu 12.0.4+).
      • [AER-2536] - (XDR) XDR compression enabling issues.

    Known Issues

  • 3.3.5
    Release Date: June 9, 2014
    • Enable add/replace-in-place of SSD drives.
    • The SSD drive can be added/replaced on a node fast-restart in Enterprise Edition only.

    New Features

    • Enterprise & Community
      • [AER-307] - (KVS) Enable drive add/replace 'in-place' without re-initializing existing drives.
    • Community Only
      • (KVS) Remove cluster size and storage limitation in community build.

    Bug Fixes

    • Enterprise & Community
      • (UDF) Stability fixes for user-defined-function. enhancement to gc heuristic. histogram fix.
      • [AER-2384] - (KVS) SWB to not have a full 1meg wasted size when wblock is only 128kb.
      • [AER-2301] - (KVS) Removal for migration assert for Repl Factor of 3.
      • [AER-2171] - (KVS) Fix for fail single-bin write transactions that contain more than one write op.
      • [AER-2316] - (KVS) Batch performance optimization.
      • [AER-2383] - (SINDEX) Sindex bin performance issue.
      • [AER-2392] - (SINDEX) Fix rare deadlock of sindex GC with journal_apply.

    Known Issues

  • 3.2.9
    Release Date: May 12, 2014
    • This release brings some significant performance enhancements and the ability to store the key with each record as well as enabling key collision check on a per transaction basis.

    New Features

    • Enterprise & Community
      • [AER-1881] - (KVS) Key Storage Ability to store key with the record and enable key collision check on a per transaction basis.
      • [AER-2264] - (KVS) Consistency enhancements during transient partition state.
      • (KVS)Enhanced handling of duplicate bin updates within same transaction.
      • (KVS)Re-organize structure to make it more cache-line friendly and reduce structure mem-zero overhead at the time of initialization.
      • (KVS)Performance enhancement: minimize thread context switching for data in memory config.
      • (KVS)Performance enhancement: allow read transactions to proceed ahead of write transactions.
      • (KVS)Network performance enhancement: don't send unnecessary LDT info (rec_props) in migration.

    Bug Fixes

    • Enterprise & Community
      • (KVS)Fix histogram and stat collection for the fire and forget option
      • (KVS)Fix crash seen on cold start eviction introduced in 3.2.8.
      • [AER-2087] - (UDF) Fix as_nil datatype in UDF.
      • (UDF) Fix lua map delete.
      • [AER-2268] - (SCAN) Fix job name on a job query.
      • [AER-2263],[AER-2270] - (STATS) Fix stat_read_req stat (caused migrations to sometimes not complete).
      • [AER-2094] - (AQL) Fix for sending record-timeout settings in client-calls via aql.
      • (AQL) Fix crash when inserting more than 4 bins in one command.
    • Enterprise Only
      • [AER-1607] - (XDR) Handling the non-shipping DC timelag properly.

    Known Issues

  • 3.2.3
    Release Date: April 10, 2014

    New Features

    • Enterprise & Community
      • [AER-2097] - (KVS) Allow -1 in config file (or info) for default-ttl, to mean 'never expire'. (Also means it's allowed for max-ttl to mean 'there's no max-ttl'.)
      • (KVS) Allowing the time-unit syntax (s, m, h, or d) on default-ttl and max-ttl via info.

    Bug Fixes

    • Enterprise & Community
      • (UDF) Handle case, where user sends no timeout value in the UDF timer code.
      • [AER-2044] - (KVS) and more - Renamed stat_storage_queue_full to err_storage_queue_full, and removed stat_storage_queue_delay, along with the actual delay. Made max-write-cache actually dynamically configurable. Streamlined the check for write queue too deep, with appropriate renaming. Return new error code AS_PROTO_RESULT_FAIL_DEVICE_OVERLOAD (18) when write queue is too deep, instead of the misleading out-of-space error code.
      • [AER-2125] - (KVS) Pull record locks at shutdown to prevent partially completed write operations.
      • [AER-1682],[AER-1704] - (KVS) applying a storage 'floor' and checks to make sure a local write has enough storage space to succeed, or fails without affecting existing record.
      • (KVS) Streamlined write sizing so total flat size is stored and not recalculated. Sizing check code is rearranged for easy removal eventually.
      • (SINDEX) Minor formatting for sindex scan messages.
      • (SINDEX) Changing the display of integer type sindex from 'INT UNSIGNED' to 'INT SIGNED' in asinfo -v sindex command.
      • (SINDEX) Fixing fan-out of sindex btree to a fix values.
      • (UDF) Add udf_context while executing the udf.
      • [AER-2088] - (KVS) Added start and restart, defaults to resume.
      • [AER-2201] - (TOOLS) Resolved issue that prevented tools package to be installed.
      • (TOOLS) Use select() based implementation to determine socket availability instead of epoll.
      • [AER-2141] - (ASMONITOR) Add -n option in asmonitor to display IP addresses.
      • [AER-2146] - (ASMONITOR) Add node name to asinfo outputs.
      • [AER-1948] - (ASMONITOR) Fix crash when running pmap.
      • [AER-1855] - (ASCOLLECTINFO) Offline state handling.
      • [AER-2103] - (ASGRAPHITE) Resolved clgraphite crash when graphite server is not running.
      • [AER-2098] - (ASGRAPHITE) Move all non int values to int.
    • Enterprise Only
      • (XDR) Use select() based implementation to determine socket availability instead of epoll.
      • (XDR) Turn off the version check of remote DC by default. Fix the issue where we are sending the lastshiptime too often in dlogreader Several minor fixes and warning-cleanup.
      • [AER-2180] - (XDR) Refactor the delete shipping and fix bugs.
      • [AER-2129] - (XDR) Adding infinite-ttl to void-time translation for xdr

    Known Issues

  • 3.2.0
    Release Date: March 19, 2014
    • This release addresses the issue with disk of size greater then 512G introduced in 3.1.3. It also improves the memory management and adds the ability to dynamically change the number of migrate threads to speed up migrations.

    New Features

    • Enterprise & Community
      • [AER-1524] - (KVS) Optimized Memory Management - Data Locality to minimize fragmentation in data-in-memory deployment.
      • (KVS) ASMalloc - Aerospike Memory Tracker.
      • [AER-1748] - (KVS) Add ability to dynamically change the number of migrate xmit threads. asinfo -v 'config-set:context=service;migrate-threads=' The permissible range for the number of migrate xmit threads is 0..100 inclusive.
      • [AER-2029] - (KVS) Time values in config file may now be expressed in units of seconds, minutes, hours, or days (add s, m, h, or d).

    Bug Fixes

    • Enterprise & Community
      • [AER-1965] - (STORAGE) 128b disk storage - Fixed unintended implicit typecast (bug affected drives > 512G).
      • [AER-2092] - (SINDEX) Sindex - Prevent crashes due to memory stomping when deleting a SIndex.
      • [AER_2018] - (SINDEX) Counter for garbage in sindex encountered through query. 2. AER-1396: Support range query for negative values.
      • [AER-1688] - (SINDEX) Source code organization - sindex tree into aerospike-server; removal of zmalloc & sds; removal of unused functionality.
      • [AER-1996] - (KVS) Moved histogram creation even earlier, so cf_crash on misconfigured tracking histogram doesn't force cold start.
      • [AER-2035] - (KVS) Set-name mismatch related cleanup.
      • (KVS) Fixed memory sizing to account for as_bin_space's 2 bytes.
      • (KVS) Add protection against receive migrates getting stuck at non-zero when the sender is at zero.
      • (KVS) Fix Proxy Crash before TSVC Transaction Queues Are Initialized.
      • (KVS) Optimized de/serialization of list/map data type.
      • (KVS) Make write_local()s record size check rigorous.
      • (SMD) Properly initialize thread attributes before creating the SMD thread.
      • (STATS) Renamed 'write-rq' to 'ongoing-write-rq'.
      • [AER-1985] - (STATS) Removed duplicate stats in clinfo -v namespace/
      • (DEPLOYMENT) Transaction-max-ms default to 1000 so no config is needed. changed defrag-startup-minimum default to 10. Changed fabric-workers (threads) default to 16. Changed nsup-queue-hwm/lwm/escape defaults to 500/1/10.
      • [AER-2042] - (UDF) Accessing uninitialized record index when executing not-found UDF record.
      • (UDF) Unprotected file reads causes weird corruption causing system to hang. Proper lock around file_read call.
      • (UDF) Statically linking lua & crypto.
      • (LDT) List fix crash in list.take().
      • (LDT) Fix the string to digest conversion function for Large Data Type.
      • (CLUSTERING) Fix for properly handling address any in heartbeat section.
      • (AQL) Print TRID correctly for high values for jobs.
      • (AQL) Fix the trailing comma in json output.
      • [AER-1535] - (AQL) Fix for integer-type data via aql.
      • [AER-1953] - (AQL) Fix for displaying result of 'show-bins' in the single-bin case, instead of crashing.
      • (AQL) Negative TRID bug.
      • [AER-2036] - (BACKUP/RESTORE) Support infinite TTL(-1) for backup and restore as per recent client change.
      • (BACKUP) Minor fix for number of objects print while given wrong namespace.
      • [AER-2060] - (PACKAGING) Prompt to continue instead of exit in case a file doesn't exist in fixownership.py
    • Enterprise Only
      • [AER-1994] - (XDR) Flush XDR named-pipe when shutting down.
      • [AER-2062] - (XDR) Improve XDR file system error warning messages to diagnose problem.
      • (XDR) Fixing missing set-name propagation in xds for single-get mode.
      • [AER-1994] - (XDR) While doing a polite shutdown, give XDR some grace period to flush the unlogged records. Added stat_xds_pipe_writes and stat_xds_pipe_miss about pipe reads/writes etc. Fixed a bug in calculating the min timestamp.
      • (XDR) Send the ttl properly during window shipping in XDR.
      • [AER-2008] - (XDR) Add stop-writes-noxdr to of get-config.
      • [AER-1879] - (XDR) Converting atomic_int counters in XDR to cf_atomic_int to avoid a mutex lock.
      • (XDR) Fix XDR shipping never-expire data to remote cluster.
      • [AER-2025] - (XDR) Fix crash caused by concurrent batch initialization.
      • (XDR) Support list & map bin types shipping.

    Known Issues

  • 3.1.14
    Release Date: February 25, 2014

    New Features

    • Enterprise & Community
      • (KVS) Repurposed stat_zero_bin_records to count records deleted because last bin was deleted.
      • [AER-1875] - (KVS) Added 'non-expirable-objects' to get the number of not expirable objects per namespace.
      • [AER-1846] - (KVS) Comment removed hard-coded pidfile usage, using --name instead (Debian only).
      • (KVS) Don't store 4 bytes of vinfo per record if we're not using vinfo.
      • [AER-1819] - (KVS) Deprecated 'empty writes' statistic.
      • (KVS) In write_local(), consolidated fail-out code, fixed set-ID assignment failure code, improved order of checks.
      • (KVS) Support asinfo -v get-config, without ':'.
      • [AER-1985] - (KVS) Fix for namespace duplicate statistics.
      • [AER 1885] - (KVS) Increase the default size of post-write queue. Benefits XDR and hot keys.
      • (KVS) Fix NPE seen on aggregation path for stream ending.
      • [AER-1943] - (KVS) Fix for properly handling address any in heartbeat section.
      • [AER-1891] - (SINDEX) Separate queues for short running and long running query jobs.
      • [AER-1927] - (SINDEX) Secondary Index - Use the correct accounted value of new and old bin value for sindex update while freeing the bins up.
      • [AER-1890] - (SINDEX) Secondary index accounting - query_queue_full was added twice in query_fail.
      • [AER-1799] - (SINDEX) Adding new error codes for secondary index operations.
      • [AER-1812] - (SINDEX) Secondary index building memory stat fix.
      • (SINDEX) Fix the default value to make sure accounting while increasing the query_threads.
      • (SINDEX) Bug in 'alc_arr_shrink()' for sindex shrinking.
      • (SINDEX) Query abort gets counted twice.
      • (SINDEX) Adding a log message for sindex creation and deletion requests coming via SMD.
      • [AER-1884] - (UDF) Fix accidental use of freed object (success value from Lua call).
      • (UDF) Updated to latest common and mod_lua.
      • [AER-1864] - (UDF) UDF registration - Remove lock inside verify_environment. Put read lock round file_read call inside udf_cask.
      • (LDT) Storage saving - LDT rec-prop if record is not LDT! This should (eventually) recover 10 storage bytes.
      • (LDT) Fix the string to digest conversion for LDT.
    • Enterprise Only
      • [AER-1875] - (XDR) XDR should appropriately send infinite TTL to destination DC.
      • [AER-1788] - (XDR) The err_ship_server metric should increment when remote D doesn't have namespace.
      • [AER-1895] - (XDR) Make XDR in 3.0 build with 2.0 C-Client.
      • (XDR) Port improvements to cl_cluster_node_fd_get() and the new function citrusleaf_cluster_get_version() from 3.0.
      • [AER-1879] - (XDR) Converting atomic_int counters in XDR to cf_atomic_int to avoid a mutex lock.
      • [AER-1954] - (XDR) Fix XDR shipping for LIST and MAP.

    Bug Fixes

    • Enterprise & Community
      • [AER-1660] - (ASMONITOR) Fix asmonitor on Debian 7 (set locale - Debian).
      • [AER-1591] - (AQL) Fix for unsupported execute query to return error.
      • [AER-1860] - (AQL) Fix for not being able to create/query secondary indices with leading numeric value.
      • [AER-1496] - (AQL) Fix for AQL segfault when non-existent file-name is passed-in.
      • (AQL) Changing help syntax for udf module registration.
      • [AER-1929] - (AQL) strtol glib function loses data when converting a uint64 value to int64.
      • [AER-1958] - (AQL) Only go to one node for sindex creation and deletion, and let SMD propagate.

    Known Issues

  • 3.1.10
    Release Date: February 12, 2014

    New Features

    • Enterprise & Community
      • [AER-923] - (KVS) Allow records to be set to NO EXPIRE via sending -1 from client.

    Bug Fixes

    • Enterprise & Community
      • [AER-896] - (KVS) Print all dynamic configuration changes in log file.
      • [AER-961],[AER-1851]- (KVS) Added 'CREATE_OR_REPLACE' proto flag to completely replace existing records (therefore avoiding reading the existing record during the write). Fixed for data-in-memory namespaces.
      • [AER-1374] - (KVS) Stop writes if disk available percent is less than min-avail-pct (default is 5). Storage stop-write now only based on available-percent, not disk-bytes used.
      • [AER-1456] - (KVS) Support persisting configuration parameters specific to a secondary index in the configuration file.
      • [AER-1553] - (KVS) Allow dynamic setting of memory-size to accept short form (e.g. 12G).
      • [AER-1645] - (KVS) Master and replica object counts are now included in namespace info.
      • [AER-1677] - (KVS) Only start info ticker and info-port after secondary indexes are fully loaded.
      • [AER-1741] - (KVS) Replica writes now bypass stop-writes.
      • [AER-1750] - (KVS) Info call- Split the network context in network.info and network. Heartbeat in get-config as in set-config.
      • [AER-1773] - (KVS) Change Debian init scripts to look for default pid file location. Change logrotate script to look for pid file in default location.
      • [AER-1799] - (KVS) Adding pre-checks for SI creation and deletion info calls.
      • [AER-1826] - (KVS) Fix partition state change crash seen on Debian7.
      • [AER-1885] - (KVS) Increase the default size of post-write queue. Benefits XDR and hot keys.
      • [AER-1925] - (KVS) Fix info calls (remove duplicate 'available_pct', missing ';').
      • [AER-1752] - (SINDEX) Optimization - skip secondary index building if index belongs to a set with zero records.
      • [AER-1816] - (SINDEX) Fix premature cluster formation before secondary index re-building finished. Caused by presents of data-in-memory namespaces in addition to SSD namespaces with secondary indexes.
      • [AER-1889] - (SINDEX) Failure to load sindex due to incorrectly looking up setname of the sindex, introduced in AER-1752.
      • [AER-1927],[AER-1896] - (SINDEX) Use the correct accounted value of new and old bin value for sindex update while freeing the bins up.
      • [AER-1485] - (UDF) Correctly return Aggregation UDF error back to the calling client.
      • [AER-1546] - (DEPLOYMENT) get-config should understand context like namespace,service,network,xdr etc.
      • [AER-1330] - (TOOLS) Enhancements to graphite tool.
      • [AER-1488] - (AQL) Adding checks to catch udf register/show/remove errors in aql.
      • [AER-1697] - (AQL) Fix for string-name length in aql/asql.
      • [AER-1685],[AER-1653] - (AQL) Fix for intermittent AQL connectivity failures.
      • [AER-1539] - (PACKAGING) enhancements to fixownership.py script for migrating system from root user to non-root user.
      • [AER-1734] - (BACKUP) Removed the 'concurrent' flag set by backup tool in scan parameters as it scans each node on its own.
      • (ASMONITOR) - Issue on debian: if the language pack supporting the system locales is not installed, asmonitor will fail. As a workaround until this issue is addressed, ensure that the language packs supporting your system locales are installed. You can check your locale values using: $ env | grep LC You can then configure the missing locale using 'sudo dpkg-reconfigure locales' and then install the required language pack as per your locale. For more details on locale, see https://wiki.debian.org/Locale .
    • Enterprise Only
      • [AER-1557] - (XDR) XDR will stay up when asd is shutdown. Also we control the messages getting printed in the log when asd is not up.
      • [AER-1702] - (XDR) Fix infinite loop because of a bad return value.
      • [AER-1777] - (XDR) Putting the time adjustment logic for failed node processing.

    Known Issues

  • 3.1.3
    Release Date: January 2, 2014
    • 128 Byte storage enhancement.
    • Recover up to 75% of your persistent storage (for integer records).
    • There is a known issue for SSD with sizes greater then 512 GB.
    • This release also adds support for running as a non-root user.
    • Downgrading to 3.0.X in Enterprise Edition requires special instructions.
    • Downgrading to 3.0.X in Community Edition requires disks to be zeroized.

    New Features

    Bug Fixes

    • Enterprise & Community
      • (KVS) When ‘any’ is set as heartbeat address, list on all the interfaces. (Earlier behavior was to listen only on the non-loopback IP of the machine.)
      • [AER-1644] - (KVS) Fix touch operations with data-in-index set to true.
      • [AER-1556] - (KVS) Changed owner of /var/log/aerospike for rpm/deb packages.
      • (KVS) Automate cold start speedup by saving eviction depth. Save write-block-size for sanity check during startup.
      • (KVS) Return meta data of the record (ttl, gen) for single key-get with NOBINDATA flag.
      • [AER-1670] - (KVS) Make asd start-able with non-privileged user.
      • [AER-1382] - (KVS) First log file is created as root for non-root asd run.
      • [AER-1594] - (KVS) Fix msgpack unpack of map failure.
      • [AER-1714] - (KVS) Resolve server crash when new node joins a cluster.
      • (SINDEX) Sindex ticker tscan_get_scan_type() related changes.
      • (SINDEX) Addition of si-memory for boot-populate-all from ns stats, removal of elapsed-time from ticker.
      • [AER-1539] - (PACKAGING) Script for fixing permissions for non root operation.
    • Enterprise Only
      • (XDR)Fix for use-default option parsing in xdr set-based shipping.
      • [AER-1643] - (XDR) Fix xds init script for debian platform.
      • [AER-1310] - (XDR) XDR multi-thread local get.
      • [AER-1256] - (XDR) Improve XDR config file parsing.
      • [AER-1252] - (XDR) Inconsistencies related XDR fixes.
      • [AER-1481] - (XDR) Call citrusleaf_get_all_digest_setname in single record get mode.
      • [AER-1473] - (XDR) Make the xdr record get threads dynamic.
      • [AER-1471] - (XDR) Introduce a counter on the server side of how many single records came from the local XDR.
      • [AER-1608] - (XDR) Avoid loop in dlogreader.
      • [AER-1656] - (XDR) Fix some config inconsistencies.
      • [AER-1597] - (XDR) XDR dc/dcname info state is wrong.
      • (XDR) Earlier batch-size is now split into max-recs-inflight + read-batch-size to allow fine granular control.
      • [AER-1702] - (XDR) Fix XDR infinite loop on batch request failure.

    Known Issues