GridGain 8.9.24 Release Notes
GridGain 8.9.24 is a maintenance release focused on improving stability and providing better SQL query management. Released on 2025-09-01.
Release date: 1 Sep 2025
Overview
GridGain 8.9.24 is a maintenance release focused on improving stability and providing better SQL query management.
Resolved Known Issues
Cancellation Management API
The control script was extended with options for stopping compute tasks, services and transactions.
Improved Debug Info Collection
Starting from this version, GridGain 8 exposes additional debug information to Control Center. When connected, you can quickly download all required information from Control Center UI.
Improvements and Fixed Issues
Community Edition Changes
GG-44530
Cluster Storage Engine
Changed MAX_INDEX_PAYLOAD_SIZE default from 427 to 64.
GG-42384
Cluster SQL Engine
Added an event for finished SQL queries.
Enterprise Edition Changes
GG-44781
Builds and Deliveries
Updated bouncycastle dependency from 1.78 to 1.79.
GG-44778
Builds and Deliveries
Updated Netty dependency from 4.1.119.Final to 4.1.124.Final.
GG-44777
Builds and Deliveries
Updated Jackson dependency from 2.13.4 to 2.16.0.
GG-44707
Cluster Data Replication
Fixed an issue that could cause infinite loop when DR log tree is destroyed in maintenance mode after a node enters it without making a checkpoint.
GG-39036
Cluster Architecture
Added an API for cancelling compute jobs, services and transactions.
Control Center Agent Changes
GG-44429
Control Center Agent
Deployment units are now redeployed to the entire cluster when a client node is restarted.
GG-44406
Control Center Agent
Fixed an issue that caused NPE in Control Center Agent when binary metadata was missing on the cluster.
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.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.8.4, 8.8.13, 8.8.18, 8.8.22, 8.8.24, 8.8.27, 8.8.30, 8.8.37, 8.8.39, 8.8.43, 8.8.44, 8.9.0, 8.9.1, 8.9.5, 8.9.9, 8.9.12, 8.9.13, 8.9.14, 8.9.15, 8.9.16, 8.9.16-p1, 8.9.16-p2, 8.9.17, 8.9.18, 8.9.19, 8.9.20, 8.9.21, 8.9.22, 8.9.22-p1, 8.9.22-p2, 8.9.23
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.
8.8.4, 8.8.13, 8.8.18, 8.8.22, 8.8.24, 8.8.27, 8.8.30, 8.8.37, 8.8.39, 8.8.43, 8.8.44, 8.9.0, 8.9.1, 8.9.5, 8.9.9, 8.9.12, 8.9.13, 8.9.14, 8.9.15, 8.9.16, 8.9.16-p1, 8.9.16-p2, 8.9.17, 8.9.18, 8.9.19, 8.9.20, 8.9.21, 8.9.22, 8.9.22-p1, 8.9.22-p2, 8.9.23
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
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_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.
This page is: Copyright © 2026 MariaDB. All rights reserved.
Last updated
Was this helpful?

