GridGain 8.7.39 Release Notes
GridGain 8.7.39 adds C++ Java compute execution, Hibernate L2 cache templates, and configurable page replacement algorithms, along with improvements and fixed issues across all editions.
GridGain 8.7.39 provides access to a number of improvements and bug fixes.
New Features
Added Support for C++ Java Compute
You can now use the new Compute::ExecuteJavaTask method to execute Java compute tasks from C++ code by their names. For example:
Ignite ignite = Ignition::Get();
compute::Compute compute = ignite.GetCompute();
std::string echoValue = "Task returns this value";
std::string res = compute.ExecuteJavaTask<std::string>("my.company.MyEchoTask", echoValue);
assert(res == echoValue);Added Support for Compute Tasks in C++ Thin Clients
Compute tasks can now be performed by using C++ thin clients. For example, here is how you can execute a newly added compute task on :
IgniteClient client = IgniteClient::Start();
compute::ComputeClient compute = ignite.GetCompute();
std::string echoValue = "Task returns this value";
std::string res = compute.ExecuteJavaTask<std::string>("my.company.MyEchoTask", echoValue);
assert(res == echoValue);Added Support for Cache Templates in Hibernate L2
When working with Hibernate L2, you may want to use the same cache configuration for multiple caches. Now you can use preconfigured Cache Templates to apply the same configuration to multiple caches.
For example, the following configuration uses a single transactional-cache bean for multiple entities:
Implemented Page Replacement Algorithms
When the amount of data stored on disk is bigger than the off-heap memory amount allocated for the data region, another page should be removed from off-heap to the disk to preload an appropriate page to off-heap memory.
There are three available algorithms:
Random-LRU algorithm;
Segmented-LRU algorithm;
CLOCK algorithm.
By default, CLOCK algorithm is used.
Page replacement algorithm is configured by the PageReplacementMode property of DataRegionConfiguration.
unsupported
unsupported
Improvements and Fixed Issues
Community Edition Changes
GG-33715
Cluster Security
Upgraded slf4j from 1.7.7. to 1.7.32 version to fix vulnerability.
GG-33714
Cluster Security
Upgraded Tomcat from 9.0.21 to 9.0.52 version to fix vulnerability.
GG-33713
Cluster Security
Upgraded Hadoop from 2.7.7 to 2.8.5 version to fix vulnerability.
GG-33692
Cluster Storage Engine
Fixed an issue that could lead to data desynchronization if a node is restarted during rebalancing under the load.
GG-33635
Platforms & Thin Clients
CPP: Added an ability to run Java tasks by name: Compute::ExecuteJavaTask.
GG-33634
Platforms & Thin Clients
Added compute functionality to C++ thin client.
GG-33586
Cluster Storage Engine
Replaced the IGNITE_THRESHOLD_WAL_ARCHIVE_SIZE_PERCENTAGE system property with the DataStorageConfiguration#minWalArchiveSize public property.
GG-33564
Cluster Storage Engine
Fixed possible failure of background cleanup of dropped SQL indexes.
GG-33520
Cluster Storage Engine
Fixed a rare issue on joins with empty LFS.
GG-33502
Cluster SQL Engine
Log messages about long running and huge results queries are now throttled.
GG-33494
Cluster Storage Engine
Corrected exception handling for checkpoint marker reading error.
GG-33472
Cluster Storage Engine
Added new page replacement algorithms: Replaced default implementation with the Clock algorithm.
GG-32206
Diagnostics and Failure Handling
Improved diagnostic capabilities for assertion errors in internal data structures.
Enterprise Edition Changes
GG-33694
Cluster Communication
Fixed an issue that could cause PME freezing during the expiration of thin clients security sessions.
GG-33590
Cluster Communication
Updated Jetty dependency to fix CVE.
GG-33550
Cluster Storage Engine
If no WAL segment is found during historical rebalance, full rebalance will be performed instead.
GG-33543
Platforms & Thin Clients
.NET: Removed unnecessary code analysis results from the release package.
Ultimate Edition Changes
GG-33656
Cluster Data Snapshots and Recovery
Fixed potential deadlock during snapshot creation.
GG-33528
Cluster Data Snapshots and Recovery
Introduced "-keep=N" option for snapshot schedule utility delete operation.
Control Center Agent Changes
GG-33638
Control Center Agent
Old deployment unit versions are now stored in metastore.
GG-33589
Control Center Agent
The cache schema is not sent until the cluster attaches.
GG-33525
Control Center Agent
Changed the start message of Control Center Agent
GG-33504
Control Center Agent
Sanitized sensitive information sent to Control Center by Control Center Agent.
GG-33497
Control Center Agent
You can now change Control Center URI without changing Control Center Agent status.
GG-33477
Control Center Agent
Changed start message of Control Center Agent
GG-33463
Control Center Agent
Fixed an issue with Control Center Agent on zOS systems.
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.2-p15, 8.7.3, 8.7.4, 8.7.5, 8.7.5-p1, 8.7.6, 8.7.6-p1, 8.7.7, 8.7.8, 8.7.9, 8.7.10, 8.7.11, 8.7.12, 8.7.13, 8.7.14, 8.7.15, 8.7.16, 8.7.17, 8.7.18, 8.7.19, 8.7.19-p1, 8.7.20, 8.7.21, 8.7.22, 8.7.23, 8.7.24, 8.7.25, 8.7.26, 8.7.26-p1, 8.7.27, 8.7.27-p1, 8.7.28, 8.7.29, 8.7.29-p1, 8.7.30, 8.7.31, 8.7.32, 8.7.33, 8.7.33-p2, 8.7.34, 8.7.35, 8.7.36, 8.7.37, 8.8.1, 8.8.2, 8.8.3, 8.8.4, 8.8.5, 8.8.6
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.
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?

