# Aerospike Server 5.0.0.3 (May 14, 2020)

**URL:** <https://discuss.aerospike.com/t/aerospike-server-5-0-0-3-may-14-2020/7437>\
**Category:** Releases (Server, Client & Tools)\
**Created:** [May 15, 2020, 1:18am UTC](https://discuss.aerospike.com/t/aerospike-server-5-0-0-3-may-14-2020/7437 "2020-05-15T01:18:39Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![mcoberly](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/mcoberly/32/637_2.png) [@mcoberly](https://discuss.aerospike.com/u/mcoberly)\
**Post date:** [May 15, 2020, 1:18am UTC](https://discuss.aerospike.com/t/aerospike-server-5-0-0-3-may-14-2020/7437/1 "2020-05-15T01:18:40Z")

</div>

[Aerospike Server version 5.0.0.3](https://www.aerospike.com/download/server/notes.html#5.0.0.3) was released on May 14, 2020.

This major release contains a New Feature, and Improvements.

- **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:
  - [Improvements in Cross-Datacenter Replication (XDR)](https://www.aerospike.com/docs/operations/upgrade/aerospike/special_upgrades/50_upgrade.html#improvements-in-cross-datacenter-replication-xdr-)
  - [XDR Architecture](https://www.aerospike.com/docs/architecture/xdr.html)
  - [Configure XDR](https://www.aerospike.com/docs/operations/configure/cross-datacenter/index.html)

- 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** 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](https://www.aerospike.com/docs/operations/upgrade/aerospike/special_upgrades/index.html) documentation.

- The Aerospike Server **will not start** if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
  - Refer to: [Configuration parameters that must be removed for Aerospike Server version 5.0](https://www.aerospike.com/docs/operations/upgrade/aerospike/special_upgrades/50_removed_parameters.html)

- 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.
  - For expirations, ‘[nsup-period](https://www.aerospike.com/docs/reference/configuration/index.html#nsup-period)’ must be configured (new default is 0).
  - For evictions, the relevant ‘[high-water-disk-pct](https://www.aerospike.com/docs/reference/configuration/index.html#high-water-disk-pct)’/‘[high-water-memory-pct](https://www.aerospike.com/docs/reference/configuration/index.html#high-water-memory-pct)’/‘[mounts-high-water-pct](https://www.aerospike.com/docs/reference/configuration/index.html#mounts-high-water-pct)’ must be configured (new defaults are 0).
  - For details refer to the ‘[Namespace Retention Configuration](https://www.aerospike.com/docs/operations/configure/namespace/retention/index.html)’ documentation.

- 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:
  - [Known Limitations](https://www.aerospike.com/docs/guide/limitations.html)

- Please reach out to your account representative if you are interested in Kerberos support.

#### 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](https://www.aerospike.com/docs/reference/metrics/index.html#bin_names_quota)’ to 65535.
  - [AER-6218] - (KVS) Service context configuration item ‘[proto-fd-max](https://www.aerospike.com/docs/reference/configuration/index.html#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.

#### Updates

- **aerospike-tools** [3.26.2](https://www.aerospike.com/download/tools/3.26.2/)