GridGain 8.8.37 Release Notes
GridGain 8.8.37 brings stability improvements and adds new service monitoring events. Released on 2023-12-29.
Release date: 29 Dec 2023
GridGain 8.8.37 brings stability improvements for GridGain, as well as new service monitoring events.
New Features
New IgniteServices Events
New events were added to help with monitoring GridGain services. The following events are now available:
EVT_SERVICE_METHOD_EXECUTION_STARTED- generated before service method execution starts.EVT_SERVICE_METHOD_EXECUTION_FINISHED- generated after service method execution finishes.EVT_SERVICE_METHOD_EXECUTION_FAILED- generated when service method execution fails.
Improvements and Fixed Issues
Community Edition Changes
GG-38157
Cluster Deployment
Added java.time package to Java 17 startup scripts.
GG-38149
Cluster Metrics & Monitoring
Fixed incorrect values of StorageSize and SparseStorageSize disk metrics for multiple cache groups.
GG-38148
Cluster Storage Engine
Updated grpc library from 1.57.2 to 1.60 to fix CVE-2023-44487.
GG-38146
Cluster Storage Engine
Introduced new method IgniteCache.touch(key) that allows to update the time to live vale for the specified key.
GG-38117
Cluster Storage Engine
Prevented partition inconsistently, which might happen on replicated cache during load on rebalance.
GG-38098
Cluster Storage Engine
Fixed an issue that could lead to partition inconsistency in replicated caches during rebalance process under load.
GG-38062
Platforms & Thin Clients
Fixed a potential infinite loop during SSL handshake with malicious or garbage data.
Enterprise Edition Changes
GG-38195
Cluster Metrics & Monitoring
Added API to access task session attributes from TaskWithAttributesEvent.
GG-38162
Cluster Metrics & Monitoring
Added new event types for service method invocation on a particular service instance.
GG-38126
Cluster Deployment
Added SunX509 SSL algorithm on IBM z/OS for Java 11+ to startup scripts.
Control Center Agent Changes
GG-38141
Control Center Agent
Added support for scan queries.
Installation and Upgrade Information
See the Rolling Upgrades page for information about how to perform automated upgrades and for details about version compatibility.
Older GridGain Versions Compatibility
Below is a list of versions that are compatible with the current version. You can rolling-upgrade from any of those. Compatibility with other versions is not guaranteed. If you are on a version that is not listed, contact GridGain for information on upgrade options.
8.7.22, 8.7.28, 8.7.29-p1, 8.7.32, 8.7.34, 8.7.38, 8.7.42-p2, 8.8.1, 8.8.2, 8.8.2-p1, 8.8.3, 8.8.4, 8.8.4-p2, 8.8.5, 8.8.6, 8.8.7, 8.8.8, 8.8.8-p1, 8.8.9, 8.8.9-p1, 8.8.10, 8.8.11, 8.8.12, 8.8.13, 8.8.13-p2, 8.8.14, 8.8.15, 8.8.16, 8.8.16-p2, 8.8.17, 8.8.18, 8.8.18-p1, 8.8.19, 8.8.19-p1, 8.8.20, 8.8.21, 8.8.22, 8.8.22-p1, 8.8.23, 8.8.23-p3, 8.8.24, 8.8.25, 8.8.25-p1, 8.8.26, 8.8.27, 8.8.28, 8.8.29, 8.8.30, 8.8.31, 8.8.32, 8.8.33, 8.8.34, 8.8.35, 8.8.36
Apache Ignite Versions Compatibility
Below is a list of versions that are tested for basic compatibility with the current version. If you are on a version that is not listed, contact GridGain for information on upgrade options.
2.11.1, 2.12.0, 2.13.0, 2.14.0, 2.15.0
Known Limitations
Jetty Configuration Incompatibility in GridGain 8.7.21 and Later
If you are upgrading from version 8.7.20 or earlier, consider an incompatibility issue related to Jetty configuration introduced in GridGain 8.7.21.
Your setup may be affected if:
You use the
ignite-rest-httpmodule (e.g. to connect to GridGain Web Console)You have a custom Jetty configuration that enables SSL for REST
Your Jetty configuration uses the
org.eclipse.jetty.util.ssl.SslContextFactoryclassThe keystore specified in the Jetty configuration contains both the CA certificate and the private certificate
In this case, after starting a new version, an exception is thrown with an error message similar to the following:
To workaround this issue, alter the Jetty configuration to use org.eclipse.jetty.util.ssl.SslContextFactory$Server or org.eclipse.jetty.util.ssl.SslContextFactory$Client. See the configuration example at the Client Certificate Authentication page.
Default rebalanceThreadPoolSize in GridGain 8.7.26 and Later
In GridGain 8.7.26, the default value of the property IgniteConfiguration.rebalanceThreadPoolSize changed from 1 to min(4, number of CPU / 4). It may cause a compatibility issue under the following conditions:
When a Rolling Upgrade is performed
The upgrade is performed from 8.5.7 version (or earlier) to 8.5.x or from 8.7.3 (or earlier) to 8.7.x
The server nodes have at least 8 CPU cores
The nodes configuration does not have the property
IgniteConfiguration.rebalanceThreadPoolSize, so the default value is used
In this case, an exception is thrown with an error message similar to the following:
To workaround this issue, change the configuration of the server nodes to rebalanceThreadPoolSize=1 so that it matches the previous default configuration. For example:
Jetty Doesn't Accept Incorrect Configuration in GridGain 8.7.31 and Later
In GridGain 8.7.31 Jetty was upgraded to 9.4.33. Starting that version, Jetty has more strict validation of the provided configuration files. Before that version, an incorrectly spelled property in the configuration file had no effect. Starting this version, errors in the configuration will lead to an error on start.
Your setup may be affected if:
You use the
ignite-rest-httpmodule (e.g. to connect to GridGain Web Console)You have a custom Jetty configuration for REST
The custom configuration has errors in it
You will need to fix the custom Jetty configuration before upgrading.
ignite.sh No Longer Enables Remote JMX by Default in GridGain 8.7.31 and Later
Starting from 8.7.31 version, GridGain no longer attempts to automatically enable the remote JMX. Default settings are known to cause issues if customized (for example, secure the connection). Also, in most cases, remote JMX is not required since many tools use local JMX connections (not using TCP).
Your setup may be affected if:
You start GridGain nodes via
ignite.shscriptYou connect to GridGain nodes' JMX interface remotely over TCP using the default configuration
To continue using remote JMX, you need to manually specify the required JMX settings. Please see the example below. Note that you don't need remote JMX if you use a local connection, such as connecting JConsole to a GridGain process on the same host.
.NET: GridGain Nuget Package Misses GridGain.Ignite Jars in 8.8.17 and Later
Add the GridGain.Ignite dependency to your project, so that jars from it are included.
.NET: Docker Images Need Additional Configuration
To run .NET SDK commands, install the .NET SDK. For more details, click here.
We Value Your Feedback
Your comments and suggestions are always welcome. You can reach us here: https://mariadb.com/support/
Please visit the documentation for more information.
This page is: Copyright © 2026 MariaDB. All rights reserved.
Last updated
Was this helpful?

