GridGain Developers Hub

GridGain 8.8.21 Release Notes

Packaging and Trial License File Changes

In the course of streamlining our licensing and trial policies, GridGain Ultimate® and GridGain Enterprise® artifacts have been changed. Direct link downloads, Maven and Docker artifacts no longer include a trial license file. A 30-day trial license with no CPU or node limit and a limited uptime is included with the downloads available on the Try Free section of the website. If you use a trial license in a production or development environment, you will need to install your purchased license files. Otherwise, the cluster will not start after the upgrade is done, and you will see an error message on node startup.

If you have any questions, please contact your GridGain Account Executive or GridGain Support.

These changes do not affect GridGain Community Edition.

New Features

New Control Script Commands

New commands idle_verify and rebuild-partition-tree were added to control script. With these commands, you can detect partition reserve counter(HWM) inconsistency or rebuild the B+Tree for a partition.

Known Issues

Docker Images

Due to a known issue, GridGain does not provide .NET Docker images for this release. This will be fixed in the next release.

Improvements and Fixed Issues

Community Edition Changes

Issue ID Category Description


GridGain Integrations

AWS SDK version upgraded to 1.12.261 to fix CVE-2022-31159.


Cluster Storage Engine

Fixed an issue when an index was not rebuilt if a node was restarted during schema change process.


GridGain Integrations

Updated jnr-posix from 3.0.50 to 3.1.15 to fix CWE-416.


Platforms & Thin Clients

Improved service name lookup performance and reduced service startup times.


Cluster Storage Engine

Fixed logical recovery of TDE caches.


Cluster Continuous Queries

Added an ability to use Java-based remote filter for continuous query from C++ thick client.


Platforms & Thin Clients

Java thin: Fixed hang on client startup when deprecated TLS version is used.


Cluster Discovery

Fixed the node resolving obsolete addresses from the previously restarted and killed nodes.


Cluster Communication

Spring Core version upgraded from 5.2.21 to 5.2.22.


Cluster SQL Engine

Fixed an issue causing a wrong result to be returned if subquery with filter is used on the left table of LEFT JOIN.


Cluster Affinity and Baseline Topology

Fixed an issue that could lead to unexpected partition map exchange on client nodes.


Cluster SQL Engine

Fixed the issue when a query with 'in' condition with a sub-query returned multiplicative data.


Cluster Storage Engine

Sped up of partition state restoration on node startup.


GridGain Integrations

Updated jcloud to fix a guava-related CVE.


Control Center Agent

Included common dependencies (Spring, Jackson) into control center agent jar to prevent possible Maven issues.


Data Regions

Added numa-aware allocation for data regions.

Enterprise Edition Changes

Issue ID Category Description


Cluster Data Replication

Fixed a rare issue that caused DR thread failure.


Cluster Communication

The script now also pulls gridgain-ultimate binaries if you use GridGain Ultimate Edition.


GridGain Integrations

Fixed CVE-2022-22971 and CVE-2022-22970.


GridGain Integrations

Updated Jetty from 9.4.43 to 9.4.48 to fix CVE-2022-2047.


Cluster Data Replication

Fixed the issue when node could fail to start with NPE during activation.


Cluster Data Replication

Added rebuild-partition-tree command to control script.


Cluster Data Replication

Fixed bad network utilization by DR due to the batching process.


GridGain Integrations

Fixed data region validation when BACKLOG policy is used


Control Script command 'idle_verify' can now detect partition reserve counter inconsistencies.

Control Center Agent Changes

Issue ID Category Description


Control Center Agent

Fixed saving of an artifact with a query in an external link.


Control Center Agent

Fixed a node failing to restart when a code deployment artifact is not available.


Control Center Agent

Fixed sending multiple instances of metrics after reconnecting the agent.


Control Center Agent

Fixed an issue when websocket connection failed.


Control Center Agent

Added Control Center server URI validation.

Installation and Upgrade Information

See the Rolling Upgrades page for information about how to perform automated upgrades and for details about version 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.29-p1, 8.7.42-p2, 8.8.2-p1, 8.8.4-p2, 8.8.8-p1, 8.8.9-p1, 8.8.13-p2, 8.8.16-p2, 8.8.18-p1, 8.7.22, 8.7.28, 8.7.32, 8.7.34, 8.7.38, 8.8.1, 8.8.2, 8.8.3, 8.8.4, 8.8.5, 8.8.6, 8.8.7, 8.8.8, 8.8.9, 8.8.10, 8.8.11, 8.8.12, 8.8.13, 8.8.14, 8.8.15, 8.8.16, 8.8.17, 8.8.18, 8.8.19, 8.8.20

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 -->

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. 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 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=" \"


.NET: GridGain Nuget Package Misses GridGain.Ignite Jars in 8.8.17

Set <PrivateAssets>None</PrivateAssets> for the GridGain.Ignite dependency in GridGain project, so that jars from there 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: or

Please visit the documentation for more information.