Skip to content
Webinar - May 13th: How Criteo powers real-time decisions with a reduced footprintRegister now

Standard Database upgrade

Upgrade your Aerospike Database cluster to gain access to the latest features and bug fixes. A rolling upgrade, the standard cluster upgrade process, involves upgrading one server node at a time and results in no downtime for the cluster. Refer to Special upgrades and downgrades for important upgrade information relevant to specific versions.

Download the server package

  • Manually download the server package from the Aerospike Downloads page.

  • It is important to read the release notes for the version you are downloading.

  • You can automate server version downloads from the artifact repository. See the FAQ on downloads for details.

  • Base URL:

    https://download.aerospike.com/artifacts/aerospike-server-VERSION/SERVER-VERSION/

Download the server package and transfer it to the node. The name of the server package varies by version.

Starting with Database 6.2, which introduced support for ARM64, the server packages use the following naming convention:

aerospike-server-EDITION_VERSION_tools-TOOLS-VERSION_DISTRO_ARCHITECTURE.tgz

edition: community, enterprise, federal

version: 6.2.0.0

distro: debian10, debian11, debian12, ubuntu18.04, ubuntu20.04, ubuntu24.04,el7, el8, el9, amzn2023

architecture: x86_64, aarch64 based on uname -m


Stop the Aerospike service

Stop the Aerospike service as follows:

Terminal window
# On systemd Linux distributions
sudo systemctl stop aerospike
Terminal window
# On System V Linux distributions
sudo /etc/init.d/aerospike stop

Extract the server and tools package

To extract the contents of the package, run the following:

Terminal window
tar -xvf aerospike.tgz

You may need to delete the older version of Aerospike if you upgrade from a version prior to 3.3.x. To remove the packages, search for the old versions of aerospike-VERSION-server and aerospike-VERSION-tools.

Terminal window
# For RRMs
sudo rpm -qa | grep aerospike
sudo rpm -e RPM_NAME
Terminal window
# For Debian packages
sudo dpkg -l | grep aerospike
sudo dpkg -r DPKG_NAME

Install the new packages

Debian format

aerospike-server-EDITION_VERSION-1DISTRO_ARCHITECTURE.deb
aerospike-tools_VERSION-[commit]DISTRO_ARCHITECTURE.deb

edition: community, enterprise, federal

version: 6.2.0.0

distro: debian10, debian11, ubuntu18.04, ubuntu20.04

architecture: amd64, arm64 based on dpkg-architecture -qDEB_HOST_ARCH

Terminal window
sudo dpkg -i aerospike-server-enterprise_6.2.0.0-1ubuntu20.04_arm64.deb
sudo dpkg -i aerospike-tools_8.1.0-ubuntu20.04_arm64.deb

RPM format

aerospike-server-VERSION-1.RHEL.ARCHITECTURE.rpm
aerospike-tools-VERSION-1.RHEL.ARCHITECTURE.rpm

edition: community, enterprise, federal

version: 6.2.0.0

RHEL: el7, el8

architecture: x86_64, aarch64

Terminal window
sudo rpm -Uvh aerospike-server-enterprise-6.2.0.0-1.el7.aarch64.rpm
sudo rpm -Uvh aerospike-tools-7.4.0-1.el7.aarch64.rpm

Start the Aerospike service

Restart the server, and wait until the server confirms that the node is ready.

Terminal window
# On systemd Linux distributions
sudo systemctl start aerospike
Terminal window
# On System V Linux distributions
sudo /etc/init.d/aerospike start

Monitor the cluster state

Prior to upgrading another node, verify that the node has re-joined the cluster by checking the following items:

  • The cluster key is uniform across the cluster, see cluster_key.
  • The cluster is the expected size, see cluster_size.

This can be checked through asadm, asinfo or by tailing the logs.

After completing the upgrade across all nodes in the cluster, run asadm -e "info network" to verify that all the nodes have successfully upgraded to the correct version and that the cluster size is correct. You can look at asadm -e "info node" to check other statistics.

Admin> info network
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~Network Information (2020-12-16 21:45:32 UTC)~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Node| Node ID| IP| Build|Migrations|~~~~~~~~~~~~~~~~~~Cluster~~~~~~~~~~~~~~~~~~|Client| Uptime
| | | | |Size| Key|Integrity| Principal| Conns|
10.0.0.1:3000| BB9010016AE4202| 10.0.0.1:3000|C-5.3.0.1| 0.000 | 5|92DCF600367B|True |BB9050016AE4202| 2|00:07:48
10.0.0.2:3000| BB9020016AE4202| 10.0.0.2:3000|C-5.3.0.1| 0.000 | 5|92DCF600367B|True |BB9050016AE4202| 2|00:07:47
10.0.0.3:3000|*BB9030016AE4202| 10.0.0.3:3000|C-5.3.0.1| 0.000 | 5|92DCF600367B|True |BB9050016AE4202| 2|00:07:46
Number of rows: 5
Feedback

Was this page helpful?

What type of feedback are you giving?

What would you like us to know?

+Capture screenshot

Can we reach out to you?