Pivotal GemFire® v9.1

Pivotal GemFire 9.1 Release Notes

Note: General support includes security vulnerability resolutions and critical bug fixes in all supported minor versions, while other maintenance is applied only to the latest supported minor release.

What’s New in Pivotal GemFire 9.1

  • Pivotal GemFire 9.1 is based on Apache Geode version 1.2.0. Pivotal GemFire 9.1 and Apache Geode share a common set of documentation. Therefore, references to both GemFire and Apache Geode appear throughout this documentation; consider them equivalents.

  • A fully-integrated Lucene text search using indexes. See Apache Lucene Integration.

  • Improved the resiliency of servers during SSL handshake.

  • A provided PartitionResolver enables the colocation of related data without writing and deploying a custom partition resolver.

  • There is a gfsh import option to invoke callbacks such as CacheListeners when importing a region snapshot file.

Installing Pivotal GemFire 9.1

You can download Pivotal GemFire 9.1 from the Pivotal GemFire product download page.

For details on how to install Pivotal GemFire 9.1, see Installing Pivotal GemFire.

Upgrading to Pivotal GemFire 9.1

To upgrade from an earlier version of GemFire to the current version, see Upgrading Pivotal GemFire.

Removed From Pivotal GemFire 9.1

The following previously-deprecated classes have been removed:

  • CacheEvent.isDistributed, CacheEvent.isExpiration
  • DataSerializer.register
  • EntryEvent.isBridgeEvent, EntryEvent.isLoad, EntryEvent.isLocalLoad, EntryEvent.isNetLoad, EntryEvent.isNetSearch
  • EntryNotFoundInRegion
  • some overloads of Execution.execute
  • some overloads of FunctionService.onMembers
  • LicenseException
  • ObjectSizerImpl
  • RemoteTransactionException
  • Region.entries(boolean), Region.keys

Resolved Issues in Pivotal GemFire


This GemFire 9.1.0 release is based on the Apache Geode 1.2.0 release. Here is a list of all issues resolved for Geode 1.2.0.

Known Issues

The following known issues affect GemFire 9.1:

  • GEM-868/GEODE-2180: Reconfiguration of the cache when autoreconnecting does not work with the default settings for use-cluster-configuration if the cache is configured through API calls. Either disable autoreconnect or disable using the cluster configuration service.