GridGain 8.9.34 Release Notes

Overview

GridGain 8.9.34 raises the .NET executable to .NET 8/10, parallelizes the LoadAll warm-up strategy, and ships dependency and Control Center Agent maintenance updates.

Major Changes

.NET Executable Now Targets .NET 8 and .NET 10

With this release, the GridGain.NET binary and bundled examples require .NET 8 or higher. The previous net6.0 target framework is no longer built.

The Apache.Ignite library itself remains on netstandard2.0, so applications that embed GridGain.NET as a library are not affected and can continue running on any compatible runtime, including .NET Framework 4.6.1+ and .NET Core 2.0+.

For more information about running the GridGain.NET node, see Standalone .NET Nodes.

New Features

Parallel Cache Warm-Up

With this release, LoadAllWarmUpStrategy loads pages into data regions in parallel rather than sequentially, reducing the time needed to warm up large caches on node start.

You can control the worker thread count through the new LoadAllWarmUpConfiguration#setThreads property. The value must be positive. Default value is max(8, Runtime.getRuntime().availableProcessors()).

Example usage:

LoadAllWarmUpConfiguration loadAllWarmUpStrategy = new LoadAllWarmUpConfiguration()
    .setThreads(16);

<bean class="org.apache.ignite.configuration.LoadAllWarmUpConfiguration">
    <property name="threads" value="16"/>
</bean>

For more information, see Cache Warm-Up Strategy.

Improvements and Fixed Issues

Community Edition Changes

Issue ID	Category	Description
GG-48851	General	Fixed an issue when IgniteLock cannot be acquired after release on JDK 17.
GG-48850	Cluster Storage Engine	Added new log messages that are printed during cache stop process when PME is done.
GG-48841	Platforms & Thin Clients	.NET: Updated examples and executable binary to .NET 8.
GG-48835	Cluster SQL Engine	Fixed a number of CWEs in H2 module.
GG-48814	Cluster Continuous Queries	Fixed an issue that could lead to an error during continuous query registration.
GG-48811	Builds and Deliveries	Updated grpc to version 1.81.0.

Issue ID

Category

Description

GG-48851

General

Fixed an issue when IgniteLock cannot be acquired after release on JDK 17.

GG-48850

Cluster Storage Engine

Added new log messages that are printed during cache stop process when PME is done.

GG-48841

Platforms & Thin Clients

.NET: Updated examples and executable binary to .NET 8.

GG-48835

Cluster SQL Engine

Fixed a number of CWEs in H2 module.

GG-48814

Cluster Continuous Queries

Fixed an issue that could lead to an error during continuous query registration.

GG-48811

Builds and Deliveries

Updated grpc to version 1.81.0.

Enterprise Edition Changes

Issue ID	Category	Description
GG-48849	Cluster Storage Engine	LoadAllWarmUpStrategy now warms up caches in parallel. Parallelism level can be configured using the LoadAllWarmUpConfiguration#setThreads property.
GG-48847	Cluster Data Replication	Fixed an issue that caused DC replication to pause when there were multiple DCR connections with heterogeneous DC ignore lists.
GG-48825	Builds and Deliveries	Updated all netty versions to 4.1.133.Final.
GG-48824	Builds and Deliveries	Updated awssdk bundle version to 2.44.7.
GG-48823	Builds and Deliveries	Updated Apache Commons configuration version to 2.15.0.

Issue ID

Category

Description

GG-48849

Cluster Storage Engine

LoadAllWarmUpStrategy now warms up caches in parallel. Parallelism level can be configured using the LoadAllWarmUpConfiguration#setThreads property.

GG-48847

Cluster Data Replication

Fixed an issue that caused DC replication to pause when there were multiple DCR connections with heterogeneous DC ignore lists.

GG-48825

Builds and Deliveries

Updated all netty versions to 4.1.133.Final.

GG-48824

Builds and Deliveries

Updated awssdk bundle version to 2.44.7.

GG-48823

Builds and Deliveries

Updated Apache Commons configuration version to 2.15.0.

Ultimate Edition Changes

Issue ID	Category	Description
GG-48818	Cluster Data Snapshots and Recovery	Fixed a rare node halt when a checkpoint races with snapshot cancellation.
GG-48808	Cluster Data Snapshots and Recovery	Fixed potential snapshot data corruption if it was created under load.

Issue ID

Category

Description

GG-48818

Cluster Data Snapshots and Recovery

Fixed a rare node halt when a checkpoint races with snapshot cancellation.

GG-48808

Cluster Data Snapshots and Recovery

Fixed potential snapshot data corruption if it was created under load.

Control Center Agent Changes

Issue ID	Category	Description
GG-48848	Control Center Agent	Added the ability to invoke control script commands directly from Control Center.
GG-48821	Control Center Agent	Control Center now determines cluster edition based on the license.

Issue ID

Category

Description

GG-48848

Control Center Agent

Added the ability to invoke control script commands directly from Control Center.

GG-48821

Control Center Agent

Control Center now determines cluster edition based on the license.

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.17 or Earlier With Java 8

Starting GridGain 8.9.18, GridGain uses Lucene 9 by default. As Lucene 9 requires Java 11, it will be impossible to run GridGain on Java 8 with default configuration.

To continue using Java 8 when migrating to GridGain 8.9.18 or later, replace the {GRIDGAIN_HOME}/libs/ignite-lucene-9 folder with {GRIDGAIN_HOME}/libs/optional/ignite-lucene-8.

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.9.34, 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 COPY command 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_LOAD parameter in the JDBC connection command:
```
jdbc:ignite:thin://127.0.0.1/?disabledFeatures=SERVER_BULK_LOAD
```
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.9.16, 8.9.16-p1, 8.9.16-p2, 8.9.16-p3, 8.9.17, 8.9.17-p1, 8.9.18, 8.9.19, 8.9.20, 8.9.20-p1, 8.9.21, 8.9.22, 8.9.22-p1, 8.9.22-p2, 8.9.23, 8.9.24, 8.9.25, 8.9.26, 8.9.27, 8.9.28, 8.9.29, 8.9.30, 8.9.31, 8.9.32, 8.9.33

Older Thin Clients Compatibility

In most cases, older versions of thin clients should be compatible with newer versions of GridGain. Below is the list of versions of thin clients that are tested for compatibility with the latest version. The compatibility also means that you can safely update from any version on the list to any subsequent version.

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

Apache Ignite thin clients are not compatible with GridGain. When switching to GridGain, follow the migration instructions to switch to GridGain clients.

Known Limitations

LEFT OUTER JOIN Behavior Change in GridGain 8.9.31

GridGain 8.9.31 fixes an issue in which the WHERE conditions could be incorrectly pushed down into the right branch of LEFT OUTER JOIN operations during query optimization. This optimization could cause queries to return incorrect results by effectively converting LEFT OUTER JOIN operations into INNER JOIN.

Starting with GridGain 8.9.31, the query optimizer correctly prevents WHERE conditions from being pushed down into the right branch of LEFT OUTER JOIN, ensuring that queries return the correct results according to SQL standards.

If your environment expects incorrect results, you set the new DIGNITE_FORCE_PUSHDOWN_CONDITIONS_TO_LEFT_JOIN system property to true on each node in your cluster. Review all affected queries and update them as needed before removing this property.

Java 8 Support in GridGain 8.9.18 and Later

Starting GridGain 8.9.18, GridGain uses Lucene 9 by default. As Lucene 9 requires Java 11, it will be impossible to run GridGain on Java 8 with default configuration.

We recommend switching to Java 11 or later before updating to GridGain 8.9.18 or later.

To continue using Java 8, replace the {GRIDGAIN_HOME}/libs/ignite-lucene-9 folder with {GRIDGAIN_HOME}/libs/optional/ignite-lucene-8.

Unsupported Features When Using Java 8 in GridGain 8.9.17

In GridGain 8.9.17, full text search is not supported when GridGain is running on Java 8. The new vector search feature requires using Java 11.

Additionally, GridGain 8.9.16 or earlier automatically created full text indexes for caches with string values, which may cause issues for working with the cache while using Java 8. To avoid this behavior, set the sql.disableCreateLuceneIndexForStringValueType property to true. If such index is already built for a cache with persistence, contact our support team for assistance with removing it.

We recommend switching to Java 11 or later before updating to GridGain 8.9.17 if you plan to use these features.

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_ENABLE property to false. 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.metricsEnabled value to false.
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.metricsEnabled value to false.
TcpCommunicationSpi communication 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_TX value to true.
Logs are now in verbose mode by default. You can use the -q command line argument in the ignite.sh script 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 readFromBackup property to true.
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_EXCHANGE setting to 0.
Data streamer now overwrites entries by default. You can keep the old behavior by setting the stmr.allowOverwrite property to false.
TCP discovery now uses static IP finder TcpDiscoveryVmIpFinder by default. To keep the old behavior, set the IP finder to use multicast IP finder.
Checkpointing process now starts upon reaching 75% of minWalArchiveSize instead of 25%. You can keep the old behavior by setting the IGNITE_CHECKPOINT_TRIGGER_ARCHIVE_SIZE_PERCENTAGE system variable to 0.25.

© 2026 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.

Last updated on Jun 03, 2026