GridGain 8.8.39 Release Notes
GridGain 8.8.39 brings a variety of bugfixes and improvements for GridGain Platform.
New Features
New Metadata Management API
With GridGain 8.8.39, a new API was added that can be used to manage cache metadata in your environment from code. Previously, this was only available by using the --meta
command. For more information, see Metadata Management.
Sender Group Management from Thin Clients
With this release, you can manage your Data Center Replication from Java and .NET thin clients. For example:
IgniteClient client = Ignition.startClient(
new ClientConfiguration().setAddresses("localhost"));
ClientCacheConfiguration cacheCfg = new ClientCacheConfiguration()
.setName("dr-cache")
.setPluginConfigurations(new GridGainClientCacheConfiguration()
.setDrSenderConfiguration(new ClientCacheDrSenderConfiguration()
.setSenderGroup("foo-bar")));
ClientCache<Integer, Integer> cache = client.createCache(cacheCfg);
Improvements and Fixed Issues
Community Edition Changes
Issue ID | Category | Description |
---|---|---|
GG-38989 |
General |
Updated netty library to version 4.2.108.Final. |
GG-38985 |
General |
Updated Zookeeper dependency to version 3.8.4. |
GG-38984 |
Platforms & Thin Clients |
Fix compilation on VS 2022 in some configurations. |
GG-38788 |
Platforms & Thin Clients |
Java thin client: Addresses with no specified port now only mean a single endpoint: "127.0.0.1" now means "127.0.0.1:10800" instead of "127.0.0.1:10800..10900". |
GG-38782 |
Cluster SQL Engine |
New system views are added: BINARY_METADATA, TABLE_COLUMNS, VIEW_COLUMNS, VIEWS. |
GG-38718 |
Cluster Metrics & Monitoring |
RequestId parameter was added to the ServiceEvent. |
GG-38695 |
Platforms & Thin Clients |
.NET: Added IBinary.RemoveBinaryType method, added support IBinary.GetBinaryTypes in thin clients. |
GG-38686 |
Cluster Control Script |
The control.sh --meta command is no longer experimental. |
GG-38644 |
General |
Added the sun.security.ssl module to startup script. |
GG-38630 |
Cluster Continuous Queries |
Fixed a possible inconsistency when using a local query listener while data is filled by using the data streamer. |
GG-38612 |
Cluster Communication |
Node will try to delay outgoing communication connection in case when incoming connection was detected. |
GG-38606 |
Platforms & Thin Clients |
Java thin client: The first address to connect is now chosen randomly if multiple addresses are provided. |
Enterprise Edition Changes
Issue ID | Category | Description |
---|---|---|
GG-38950 |
Cluster SQL Engine |
The control utility meta --remove command now correctly removes all metadata. |
GG-38913 |
Cluster Continuous Queries |
Added the new IGNITE_SERVICES_SET_REMOTE_FILTER_ON_START system property. |
GG-38816 |
Platforms & Thin Clients |
.NET thin client: Added ClientCacheDrSenderConfiguration that can be used to configure DR sender for a new cache from the thin client. |
GG-38791 |
General |
Upgrade jackson-databind to 2.16.0. |
GG-38744 |
Platforms & Thin Clients |
Java thin client: added ClientCacheDrSenderConfiguration to configure DR sender for a new cache from the thin client. |
GG-38647 |
Cluster Control Script |
Fixed incorrect sender group argument parsing in data center replication full-state-transfer command. |
GG-38458 |
Cluster Data Replication |
Removed unnecessary information from cache partitions when data center replication is disabled. |
GG-38453 |
Platforms & Thin Clients |
.NET: Fixed failed node start due to missing jars when only GridGain package is referenced |
Control Center Agent Changes
Issue ID | Category | Description |
---|---|---|
GG-38693 |
Control Center Agent |
Added support for scheduling and managing snapshots from Control Center 2024.1 or later. |
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.39-p2
, 8.7.42-p2
, 8.8.1
, 8.8.2
, 8.8.2-p1
, 8.8.3
, 8.8.4
, 8.8.4-p1
, 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-p1
, 8.8.13-p2
, 8.8.14
, 8.8.15
, 8.8.16
, 8.8.16-p1
, 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.22-p2
, 8.8.23
, 8.8.23-p1
, 8.8.23-p2
, 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
, 8.8.37
, 8.8.37-p1
, 8.8.38
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-http
module (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.SslContextFactory
class -
The 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:
java.lang.IllegalStateException: KeyStores with multiple certificates are not supported on the base class
org.eclipse.jetty.util.ssl.SslContextFactory. (Use org.eclipse.jetty.util.ssl.SslContextFactory$Server
or org.eclipse.jetty.util.ssl.SslContextFactory$Client instead)
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:
сlass org.apache.ignite.IgniteException: Rebalance configuration mismatch (fix configuration or set -DIGNITE_SKIP_CONFIGURATION_CONSISTENCY_CHECK=true system property).
Different values of such parameter may lead to rebalance process instability and hanging. [rmtNodeId=5fc58fb7-209d-489a-8034-0127a81abed6, locRebalanceThreadPoolSize = 4, rmtRebalanceThreadPoolSize = 1]
To workaround this issue, change the configuration of the server nodes to rebalanceThreadPoolSize=1
so that it matches
the previous default configuration. For example:
<bean class="org.apache.ignite.configuration.IgniteConfiguration">
<property name="rebalanceThreadPoolSize" value="1"/>
<!-- The rest of the configuration goes here -->
</bean>
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-http
module (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.sh
script -
You 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.
export JVM_OPTS="-Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=33333 \
-Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false"
bin/ignite.sh
.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://gridgain.freshdesk.com/support/login or docs@gridgain.com
Please visit the documentation for more information.
© 2025 GridGain Systems, Inc. All Rights Reserved. Privacy Policy | Legal Notices. GridGain® is a registered trademark of GridGain Systems, Inc.
Apache, Apache Ignite, the Apache feather and the Apache Ignite logo are either registered trademarks or trademarks of The Apache Software Foundation.