This topic contains the release notes for VMware Tanzu GemFire.
Tanzu GemFire 10 has been designated the “Gideon” release in memory of our colleague, Gideon Low.
Released: April 17, 2024
Tanzu GemFire 10.1.1 includes updates to netty, spring, and spring-security to address the following security issues:
See Issues Resolved in Tanzu GemFire 10.1.1 for details regarding issues addressed in this release.
Tanzu GemFire contains a number of new features and improvements, including:
GemFire 10.1 deprecates Pulse in favor of VMware GemFire Management Console. Pulse will be removed in a future release.
See Issues Resolved in VMware GemFire 10.1 for details regarding issues addressed in this release.
The GemFire Session Management extension must be downloaded separately from the GemFire installation package and is no longer bundled in the GemFire .tgz
like it was in GemFire version 10.0. For more information about the GemFire Session Management extension, see:
In version 10.1, GemFire disk stores support increased parallelism through the use of segments. In many cases, this can improve recovery time by up to 10x depending on the underlying storage subsystems. For more information, see Segmented Disk Stores in Defining and Configuring Disk Stores. To learn how to migrate your disk stores to the new format, see upgrade offline-disk-store in gfsh Command Help.
Version 10.1 adds gfsh
commands that you can use to manage queries running in VMware GemFire clusters. For more information, see Managing Queries
In version 10.1, many gfsh
commands provide additional status and context. In particular, the following commands have been enhanced:
In version 10.1, clients may choose to filter Continuous Query events based on the type of the event. This is especially helpful when delete
events are not desired. For more information, see CQ Event Filter in How Continuous Querying Works.
Version 10.1 adds two parameters to more precisely tune client connections to the server that implement single-hop operations to and from partitioned regions. The new parameters are max-connections-per-server
and min-connections-per-server
. These parameters take effect when pr-single-hop-enabled=true
, overriding the settings of max-connections
and min-connections
. Because pr-single-hop-enabled=true
is the client pool’s default setting, the new per-server
parameters are also in effect by default.
For legacy applications, a conversion formula is applied to convert existing max-connections
and min-connections
settings to equivalent max-connections-per-server
and min-connections-per-server
settings. For details about this conversion formula, see Configuring Client Single-Hop Access to Partitioned Regions.
In version 10.1, server shutdown has been optimized to allow clients to failover more quickly. The server that is shutting down immediately forces a primary bucket election to ensure that incoming writes are redirected onto new servers.
By default, the following characters are not allowed in region names:
[
)]
)^
)`
)\)
To use any of these special characters in region names, set the value of the GemFire system property gemfire.allowSpecialRegionNameCharacters
to true
.
GemFire provides a Prometheus endpoint that allows the metrics to be gathered by a metrics collection agent and forwarded to a metrics monitoring platform (such as the GemFire Management Console) for further analysis and alerting.
These metrics are disabled by default. To learn how to enable and configure this endpoint when starting a GemFire member see Prometheus Metrics Endpoint.
This section describes issue resolutions that significantly affect VMware GemFire applications.
GEM-6318: Corrected an issue where GemFire Pulse (deprecated) queries when no server was selected returned empty results, and JMX query results were duplicated and showed an extra level of nesting in the JSON.
GEM-6664: Corrected an issue where client authorization exceptions could occur when integrated security caused the server’s ClientHealthMonitor
to clear a client’s proxy information but the client continued to hold and try to use the uniqueId
in later operations.
GEM-6693: Corrected an issue where indexes could fail to populate on server restart due to the default RestrictedMethodAuthorizer
being used instead of the configured method authorizer.
GEM-6885: Corrected an issue where multiple EvictionControllers
and HeapLRUStatistics
were being created for the same overflow region.
GEM-6892: Unnecessary ThreadMonitor
logging messages have been eliminated.
GEM-7052, GEM-7284: Updated spring to 5.3.33 to address CVE-2024-22243 and CVE-2024-22259.
GEM-7101: Corrected an issue where the verbose
option in the describe region
command in gfsh
could show an incorrect number of entries in the cache.
GEM-7310: Updated spring-security to 5.8.11 to address CVE-2024-22257.
GEM-7349: Updated netty to v4.1.108 to address CVE-2024-29025.
GEM-5397: In prior releases, the order of the operands in AND
and OR
expressions in OQL (Object Query Language) were incorrectly evaluated from right to left instead of from left to right. Because these operators use short-circuit evaluation, this could affect the behavior or performance of some types of queries. This issue has been resolved in 10.1.0.
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.
New versions of VMware GemFire often include important security fixes, so VMware recommends that you keep up-to-date with the latest releases.
For details about any security fixes in a particular release, see Security Advisories - Tanzu.