You can upgrade directly to VMware Tanzu GemFire for VMs version v1.14.5 from the latest patch release of versions GemFire for VMs 1.10 or later. This "jump upgrade" is a two-step process:
Verify that your current version of GemFire for VMs has been updated to its latest patch release. If you have not installed the latest patch, then do so.
The latest patch releases are:
|GemFire for VMs Version (Major.Minor)||Latest Patch Release|
Upgrading to GemFire for VMs 1.14 from any version other than those shown requires multiple steps. For example, if your current version is v1.10.5, you must first upgrade to the latest patch of 1.10 shown in the table, from which you can then jump upgrade to 1.14.
In addition, be sure to check the following section for any version-specific upgrade considerations.
Each GemFire for VMs release is compatible with two VMware Tanzu Application Service for VMs (TAS for VMs) and Ops Manager versions. Incorporate those upgrades to TAS for VMs and Ops Manager in your upgrade process as required to maintain compatibility, as described in Upgrading Ops Manager in the VMware Tanzu Ops Manager documentation.
If your application connects via the Services Gateway feature, which was introduced in v1.13.0, you must first upgrade to the latest GemFire for VMs v1.13 patch before upgrading further. Then upgrade to 1.14, unbind, rebind and restart your application.
To upgrade to v1.9 from earlier releases, you must upgrade minor releases sequential order. For example, VMware Tanzu GemFire for VMs v1.7 must be upgraded to GemFire for VMs v1.8 prior to upgrading to GemFire for VMs v1.9.
VMware Tanzu GemFire for VMs version 1.13.1 included an Apache Geode v1.13.2 performance improvement that increased the defaults for maximum number of pooled message processor threads and maximum partitioned region message processor threads.
If you are upgrading from a version of VMware Tanzu GemFire for VMs earlier than version 1.13.1, and your system had been hitting the old, lower default maximums, then upgrading to v1.14.5 may cause increased use of system resources as the system is no longer constrained to the old values. If your system depends on constraining system resources to the old default values, you can set these properties explicitly using DistributionManager.MAX_THREADS and DistributionManager.MAX_PR_THREADS, respectively.
The following table shows the old and new maximum values.
|System Resource||Old Default Value||New Default Value|
|DistributionManager.MAX_PR_THREADS||The greater of (CPUs * 4) or 16||The greater of (CPUs * 32) or 200|
Follow these steps to upgrade GemFire for VMs:
Download the new version of the tile from VMware Tanzu Network.
Upload the product to Ops Manager.
Click Add next to the uploaded product.
Click on the GemFire for VMs tile and configure the upgrade options.
Click Review Pending Changes.For more information, see Reviewing Pending Product Changes in the VMware Tanzu Ops Manager documentation.
Click Apply Changes.
The default upgrade path upgrades all service instances as a result of a tile upgrade. This operation can take a lengthy amount of time. To expedite upgrades, an operator can permit developers to upgrade their own service instances once the tile has been upgraded.
An operator enables individual service instance upgrades during tile installation. This feature requires TAS for VMs/Ops Manager 2.7 or a higher version and works for upgrading from GemFire for VMs 1.9.0 to a higher version.
Within the GemFire for VMs tile, in the Errands section, the default for the Upgrade All Service Instances errand, which upgrades all service instances, appears as:
To change the state of this errand such that individual service instance upgrades are enabled, choose Off for this errand:
Once individual service instance upgrades are enabled, the developer upgrades an individual service instance following the instructions in Upgrade a Single Service Instance.