GridGain Developers Hub

Version Upgrade

This page covers the basic upgrade process for local GridGain installations.

Upgrading ZIP Installation

Before Upgrade

Before performing an upgrade, consider that it may accidentally overwrite important data stored in the installation directory. If you plan to do an upgrade, it’s strongly recommended moving critical data outside the installation folder:

  • The work folder contains persistent storage and all data required for node operation.

  • The etc folder holds the node’s configuration files, which are loaded at startup.

  • The log folder stores all log files generated by the node.

You can change the location of these folders by editing the etc/vars.env file or by setting corresponding environment variables.

Upgrade

To upgrade a GridGain ZIP installation, follow these steps:

  1. First stop all the nodes in the cluster. Do not perform an upgrade while the cluster is running, unless the Rolling Upgrade is used. Navigate to the existing installation’s etc folder and delete the ignite.version.full file.

  2. Replace the binaries with the new version. Copy the ignite.version.full file from the new ZIP’s etc directory into yours.

  3. Start the cluster again.

Upgrading Docker Installation

When updating a docker installation, all information in the container with GridGain will be lost. To keep your configuration, logs and other data, mount a volume for any persistent data you need.

Upgrading DEB/RPM Package Installation

You can use the standard update command provided by your operating system’s package manager to upgrade a package-based installation.

To perform an upgrade, take the following steps:

  1. First stop all the nodes in the cluster. Do not perform an upgrade while the cluster is running, unless the Rolling Upgrade is used.

  2. Then update the installation:

    sudo apt-get upgrade gridgain9-db-gridgain-9.1.0.deb
    sudo rpm -U gridgain9-db-gridgain-9.1.0.noarch.rpm
  3. Once the update is completed, start the cluster.