LATEST VERSION: 8.1.0 - CHANGELOG
Pivotal GemFire® v8.1

Pivotal GemFire Version Compatibility Rules

Pivotal GemFire Version Compatibility Rules

This topic describes the compatibility rules for deploying different versions of Pivotal GemFire.

Version Compatibility Between Peers and Cache Servers

You can have peers or cache servers running Pivotal GemFire 8.0 and Pivotal GemFire 8.1 at the same time for the purposes of a rolling upgrade. You can also run different minor release versions such as 7.0.1 and 7.0.2 in the same distributed system cluster.
Note: Rolling upgrade support begins with version 8.0; therefore, you cannot perform a rolling upgrade from GemFire 7.0.x to GemFire 8.0.
See Performing a Rolling Upgrade for more details on how to upgrade your system between versions without taking your entire cluster offline. To view which versions of GemFire are currently running in your cluster, see Checking Member Versions in a Mixed Cluster.
Note: After you have upgraded all your locators during a rolling upgrade, do not start or restart any members that are running an older version of the software. These processes will either not be allowed to join the distributed system; or if allowed to join, can potentially cause a deadlock.

Version Compatibility Between Clients and Servers

GemFire clients can run an older version of GemFire and still connect to GemFire servers running a newer version. In other words, a client running GemFire 5.7 will be able to connect to a server running GemFire 6.6.2 or GemFire 7.0.1. Newer clients such as GemFire 8.0.0 or 7.0.2 clients, however, cannot connect to servers running older versions of GemFire such as GemFire 6.6.4.

Version Compatibility Between Sites in Multi-Site (WAN) Deployments

In multi-site (WAN) deployments, you can run different major versions of Pivotal GemFire on the different sites. For example, one site can be running GemFire 5.7 and another site running GemFire 6.6.2 and the sites should still be able to communicate with one another.