Version Upgrade
Upgrade is an important part of the lifecycle of any software system. This page covers the basic upgrade process for GridGain.
Upgrading Nodes
Updating node version is as simple as replacing the GridGain binaries with a new version. However, there are several things to keep in mind when performing the upgrade:
-
GridGain cluster cannot have nodes that run on different GridGain versions. You need to stop the cluster and start it again on the new GridGain version.
-
It is possible to accidentally overwrite your persistent storage or other important data during the upgrade. It is recommended to move this data outside of intallation folder if you are planning upgrades:
-
The work directory is used to store application data and all data required for the node to work. You can change its location as described in tge Configuring Work Directory section.
-
The persistent storage holds all information stored on the node. You can change its location as described in the Configuring Persistent Storage Directory section.
-
WAL Archive os used to store WAL segments for recovery. You can change its location as described in WAL Archive section.
-
Version Compatibility
GridGain is tested for safe upgrade compatibility with recent versions. For the list of versions, check the release notes for the version you intend to update to.
If your planned update is not on the list, you may need to perform additional work to safely migrate to the new version.
© 2024 GridGain Systems, Inc. All Rights Reserved. Privacy Policy | Legal Notices. GridGain® is a registered trademark of GridGain Systems, Inc.
Apache, Apache Ignite, the Apache feather and the Apache Ignite logo are either registered trademarks or trademarks of The Apache Software Foundation.