Windows/Unix/Linux: Upgrade Pivotal GemFire from a ZIP or tar.gz File
Windows/Unix/Linux: Upgrade Pivotal GemFire from a ZIP or tar.gz File
For all other OS users, upgrade Pivotal GemFire on every virtual and physical machine that will run GemFire.
Procedure for Upgrading Pivotal GemFire 6.X to 8.2.X
Use the following procedure to upgrade your Pivotal GemFire deployment:
Note: Thoroughly test your development systems with the new version before
moving into production.
- Review the items listed in Before You Upgrade and make any appropriate preparations.
- Install the latest version of GemFire in a
different directory than the existing version. See Windows/Unix/Linux: Install Pivotal GemFire from a ZIP or tar.gz File. Note: GemFire is installed as a complete product, rather than as a modification to a prior version. In addition, the Java JRE runtime environment is not bundled with GemFire, so you need to have an appropriate JDK or JRE installed and configured to comply with GemFire requirements and your unique system needs. See Supported Configurations and System Requirements for the configuration requirements of GemFire 8.2.x.
- Review the changes and upgrade notes
that are documented in the Pivotal GemFire Release Notes.
- Review the Pivotal GemFire 8.0.x Release Notes that are available at http://gemfire.docs.pivotal.io/index.html. Make any changes to your applications that are required for you to migrate to this version.
- Review the Pivotal GemFire 7.0.x Release Notes that are available at http://gemfire.docs.pivotal.io/index.html and https://www.vmware.com/support/pubs/vfabric-gemfire.html. Make any changes to your applications that are required for you to migrate to this version.
- If you are upgrading to 8.0.x from a version earlier than GemFire 6.6, review all changes documented in the Pivotal GemFire 6.6.x Release Notes. (At https://www.vmware.com/support/pubs/vfabric-gemfire.html, select Release 6.6.x.) Make any changes to your programs required for you to migrate to this version.
- Recompile your Java applications against the gemfire.jar in this version of the product. After you have recompiled your Java applications, the location where you place the updated JARs will vary depending on your configuration. You may put them in the GemFire product tree or you could directly copy in the gemfire.jar file to a location appropriate for your application.
- Stop all members of the system running
with the prior 6.x.x version.
- Shut down all members running a
cache by using the gemfire shut-down-all command:
sudo -u gemfire -E gemfire –J-DgemfirePropertyFile=mygemfire.properties shut-down-all
In the sample command, substitute mygemfire.properties with the location of the previous Pivotal GemFire's gemfire.properties file for the distributed system you are shutting down. -
Shut down any locators. To shut down a locator in 6.x.x deployments, issue the following command:
gemfire stop-locator -port=port -address=ipAddr -dir=locatorDir
Replace port, ipAddr and locatorDir with the appropriate values.
- Shut down all members running a
cache by using the gemfire shut-down-all command:
- Upgrade your disk store files.
- If you will be upgrading to GemFire 8.2.x from a GemFire version earlier than 6.5.x, upgrade your disk store files by using the DiskConverterPre65to65 tool. See DiskConverterPre65to65 for instructions on running the tool.
- If you are upgrading from GemFire 6.5.x or 6.6.x (or have just upgraded your disks to 6.5 compatibility with the DiskConverterPre65to65 tool), run the gfsh command upgrade offline-disk-store tool to upgrade the disk stores to Pivotal Gemfire 8.2.x. See upgrade offline-disk-store for more information.
- Redeploy your environment's
configuration files to the new version's installation. For example, you may need
to do one of the following tasks depending on your GemFire deployment
configuration:
- If you are want to use the cluster configuration service to configure your entire cluster, see Loading Existing Configuration Files into Cluster Configuration.
- If you are using local configuration files, update each set of configuration files that are local to the distributed system you are upgrading. See Deploying Configuration Files without the Cluster Configuration Service for more information on how to deploy configuration files.
- Point all member sessions to the new
installation of GemFire. For example, you may need to do one of the following
tasks depending on your application's configuration:
- Modify your applications to point to the new GemFire product tree location.
- Copy the gemfire.jar file out of the new GemFire product tree location and replace the existing gemfire.jar file in your application.
- Restart all system members according to your usual procedures. See Starting Up Your System for more information.
Procedure for Upgrading Pivotal GemFire 7.0.x to 8.2.0
The following procedure describes how to upgrade your entire distributed system from Pivotal GemFire 7.0.x to 8.2.0.
- Review the items listed in Before You Upgrade and make any appropriate preparations.
- Install the latest version of GemFire
in a different directory than the existing version. See Windows/Unix/Linux: Install Pivotal GemFire from a ZIP or tar.gz File. Note: GemFire is installed as a complete product, rather than as a modification to a prior version. The Java JRE runtime environment is not bundled with GemFire, so you need to have an appropriate JDK or JRE installed and configured to comply with GemFire requirements and your unique system needs.
- Repeat this upgrade procedure for every virtual or physical machine on which you will run Pivotal GemFire.
- Stop all members of the system running
with the prior version. For example, using the gfsh shutdown
command:
- Open a gfsh prompt.
- Make sure you are connected (via its JMX Manager) to the distributed system you wish to shutdown.
- At the gfsh prompt, type:
gfsh>shutdown
- Type y at the prompt to shutdown your entire distributed system.
- Shut down each locator in the
distributed system by using the stop locator command.
For example:
gfsh>stop locator (-)name=locator_name
- Redeploy your environment's configuration files to the new version's
installation. For example, you may need to do one of the following tasks
depending on your GemFire deployment configuration:
- If you are want to use the cluster configuration service to configure your entire cluster, see Loading Existing Configuration Files into Cluster Configuration.
- If you are using local configuration files, update each set of configuration files that are local to the distributed system you are upgrading. See Deploying Configuration Files without the Cluster Configuration Service for more information on how to deploy configuration files.
- Point all member sessions to the new
installation of GemFire. For example, you may need to do one of the following
tasks depending on your application's configuration:
- Modify your applications to point to the new GemFire product tree location.
- Copy the gemfire.jar file out of the new GemFire product tree location and replace the existing gemfire.jar file in your application.
- Restart all system members according to your usual procedures. See Starting Up Your System for more information.
What to Do Next
After you upgrade, perform the following tasks:
- Run the product tutorial and examples. See Setting Up the Product Examples and Pivotal GemFire Tutorial.
- If you need to uninstall GemFire, see How to Uninstall GemFire.