GridGain 8.9.14 Release Notes
GridGain 8.9.14 is a regular release bringing new features and performance improvements. Released on 2024-11-07.
Release date: 7 Nov 2024
Overview
GridGain 8.9.14 is a regular release bringing new features and performance improvements.
New Features
Touch Metrics
This release brings a number of new metrics that allow you to keep track of how often touch requests were performed and their success rate. The following metrics were added:
cacheTouches- the total number of touch requests to the cache.cacheTouchHits- the number of successful touch requests.cacheTouchMisses- the number of failed touch requests.
Improvements and Fixed Issues
Community Edition Changes
GG-40919
Cluster Storage Engine
Fixed an issue that could lead to NullPointerException when committing a transaction while a node is stopping or reconnecting.
GG-40846
Diagnostics and Failure Handling
A warning is now displayed when the DisableExplicitGC flag is enabled.
GG-40580
Cluster Storage Engine
Page replacement now occurs before the fsync phase of partition files, which eliminates the chance of data corruption.
GG-39144
Cluster Metrics & Monitoring
Added touch metrics to CacheMetrics that can be used to track touch operations.
GG-38434
Cluster SQL Engine
Fixed an issue with calculating statistics for tables with size over 2147483648 rows.
GG-37424
Cluster SQL Engine
Disabled support for triggers in H2.
GG-36941
Cluster Storage Engine
Improved performance of read-only transactions over persistent caches.
GG-35240
Cluster Storage Engine
One-phase commit is now disabled when using JTA transaction manager.
Enterprise Edition Changes
GG-40861
Cluster Data Replication
Improved internal handling of data structures during DR.
GG-40410
GridGain Integrations
Kafka connector: Added policies to control error handling behavior during source cache entry or sink record processing.
Ultimate Edition Changes
GG-40720
Cluster Data Snapshots and Recovery
Fixed a rare issue that could lead to skipping a committed cross-cache transaction during point-in-time recovery.
Installation and Upgrade Information
See the Rolling Upgrades page for information about how to perform automated upgrades and for details about version compatibility.
Migrating From GridGain 8.9.0
GridGain 8.9.1 introduced a large number of changes in default configuration values. Your setup may be affected if you are using default configuration.
When migrating to GridGain 8.10, make sure to check Changed Default Values in GridGain 8.9.1 and Later section for any parameters you need to change.
Migrating From GridGain 8.X
When migrating from GridGain 8.8 to GridGain 8.9, no special actions are required for core functionality migration. By using rolling upgrades, you can update from any GridGain version listed below. You may need to perform minor configuration changes to ensure stability post migration.
If you are using GridGain Enterprise or Ultimate, the
COPYcommand was reworked as described in the COPY Command Changes section. The syntax for working with CSV remains the same, but the path is now calculated on the node and the client. This change does not affect GridGain Community edition.To disable this behavior and use the old copy command, pass the
disabledFeatures=SERVER_BULK_LOADparameter in the JDBC connection command:If you are using one of the optional modules listed in the Removed Modules section, they will continue to work, but compatibility and stability on GridGain 8.9 is not guaranteed. Consider using the alternatives:
Visor CMD and GUI can be replaced by GridGain Control Center.
The spark module can be replaced by the Spark Ignite Extension.
If you are using default values in your configuration, you may need to set them manually to keep you cluster working the same way as in previous versions. Make sure to check Changed Default Values in GridGain 8.9.1 and Later section for any parameters you need to change.
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, 8.8.39, 8.8.40, 8.8.41, 8.8.42, 8.8.43, 8.9.0, 8.9.1, 8.9.2, 8.9.3, 8.9.4, 8.9.5, 8.9.6, 8.9.7, 8.9.8, 8.9.9, 8.9.10, 8.9.11, 8.9.12, 8.9.13
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
Changed Permissions for Control Center Agent in GridGain 8.9.4 and Later
GridGain 8.9.4 introduced stricter permissions checking for Control Center Agent. When running secured clusters, some actions that previously were available without permissions, will now require additional permissions.
Before updating, make sure to provide the required permissions, otherwise some actions may become unavailable.
New TRACING_CONFIGURATION_UPDATE Permission in GridGain 8.9.2 and Later
GridGain 8.9.2 introduced the TRACING_CONFIGURATION_UPDATE permission. If you were using security on a cluster before updating to this version, make sure that you provide the permissions to control utilities or users who need to update cluster permissions. Otherwise, they will not be able to update
Changed Default Values in GridGain 8.9.1 and Later
If you are updating from GridGain 8.8.X or 8.9.0, a large number of default values have been changed.
These changes may affect the stability or performance of your cluster if you are using default values.
We recommend checking the list below to make sure the changes do not have an adverse effect, and setting the value manually if necessary.
Service processor now use event-driven implementation by default. You can keep the old behavior by setting the
IGNITE_EVENT_DRIVEN_SERVICE_PROCESSOR_ENABLEproperty tofalse. Make sure that all nodes in the cluster are set to the same value. See Services documentation for more information.Data region metrics are now enabled by default. This may have a minor (within 2%) adverse effect on performance. You can keep the old behavior by setting the
DataRegionConfiguration.metricsEnabledvalue tofalse.Data storage metrics are now enabled by default. This may have a minor (within 2%) adverse effect on performance. You can keep the old behavior by setting the
DataStorageConfiguration.metricsEnabledvalue tofalse.TcpCommunicationSpicommunication protocol now has a limit of 4096 messages for the outgoing messages queue by default.Atomic operations are now not allowed in transactions by default. You can keep the old behavior by setting the
IGNITE_ALLOW_ATOMIC_OPS_IN_TXvalue totrue.Logs are now in verbose mode by default. You can use the
-qcommand line argument in theignite.shscript to keep current log behavior.SQL queries are now loaded lazily by default. This reduces memory consumption on medium and large queries and potentially improves garbage collection performance. You can keep the old behavior by setting the
SqlFieldsQuery.setLazy(false).Cache entries are now read from primary partitions by default, even if an entry is available on the node in a backup partition. This may have a minor performance impact, but significantly increases cluster stability. You can keep the old behavior by setting the
readFromBackupproperty totrue.Partition map exchange transactions now time out after 1 minute instead of 0 (infinite) by default. You can keep the old timeout by setting the
TX_TIMEOUT_ON_PARTITION_MAP_EXCHANGEsetting to 0.Data streamer now overwrites entries by default. You can keep the old behavior by setting the
stmr.allowOverwriteproperty tofalse.TCP discovery now uses static IP finder
TcpDiscoveryVmIpFinderby default. To keep the old behavior, set the IP finder to use multicast IP finder.Checkpointing process now starts upon reaching 75% of
minWalArchiveSizeinstead of 25%. You can keep the old behavior by setting theIGNITE_CHECKPOINT_TRIGGER_ARCHIVE_SIZE_PERCENTAGEsystem variable to0.25.
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
Starting with GridGain 8.8.17, the GridGain.Ignite dependency is not included in the Nuget package. To use GridGain in your project, make sure to include the dependency explicitly so that jars from it are included.
We Value Your Feedback
Your comments and suggestions are always welcome. You can reach us here: https://mariadb.com/support/
This page is: Copyright © 2026 MariaDB. All rights reserved.
Last updated
Was this helpful?

