GridGain 8.9.35 Release Notes

Overview

GridGain 8.9.35 adds Kubernetes readiness probe, as well as a number of library updates.

New Features

Kubernetes Liveness and Readiness Probes

With this release, the REST API provides a probe command that you can use as a Kubernetes liveness, readiness, or startup probe. The probe type is selected with the optional kind query parameter:

liveness (the default when kind is omitted) - reports whether the node has started. Returns HTTP 200 once the node is up, or HTTP 503 while it is still starting.
readiness - reports whether the node is ready to serve requests. The node is considered ready only after it has started, is not in maintenance mode, and has completed its initial rebalancing. Otherwise, the endpoint returns HTTP 503.

Use the readiness endpoint for Kubernetes startup probes as well.

http://host:port/ignite?cmd=probe
http://host:port/ignite?cmd=probe&kind=readiness

For details on the probe command, see probe in the REST API reference. For how to set up the liveness, readiness, and startup probes in a Kubernetes deployment, see Readiness Probe.

DCR Partition Tree Reset

With this release, you can reset the data center replication (DR) partition update log at run time by using the new control.sh --dr reset-partition-tree command. Unlike dr cleanup-partition-tree, this command does not require maintenance mode. You can optionally limit the reset to specific caches, partitions, or nodes.

control.sh --dr reset-partition-tree [--caches <cacheName1,...,cacheNameN>] [--partitions <0,1,...,N>] [--nodes <consistentId0,...,consistentIdN>] [--yes]

For more information, see dr reset-partition-tree in the control script reference.

Partition State Validation Events

With this release, GridGain emits two new event types when the cluster coordinator validates partition states during a partition map exchange (PME):

EVT_PARTITIONS_STATE_VALIDATION_SUCCEEDED - partition states are consistent across the cluster.
EVT_PARTITIONS_STATE_VALIDATION_FAILED - one or more partitions have inconsistent states. The event reports the affected caches and partitions, along with the topology version on which the validation ran.

Both events are instances of the PartitionsStateValidationEvent class and are fired on the coordinator node only. As with other events, enable them through IgniteConfiguration.setIncludeEventTypes() before you can listen for them.

For more information, see Partition State Validation Events.

Improvements and Fixed Issues

Community Edition Changes

Issue ID	Category	Description
GG-49398	Cluster SQL Engine	Improved index usage by IN operator.
GG-49361	Builds and Deliveries	Updated OpenTelemetry from version 1.60.1 to version 1.63.
GG-49358	Cluster Metrics & Monitoring	Added REST endpoint for the k8s liveness/readyness/startup probes.
GG-49352	Cluster Storage Engine	Fixed an issue when a corrupted index would lead to an infinite node restart.
GG-49328	GridGain Integrations	Hibernate integration modules for versions 4.2, 5.1, 5.3 are now deprecated.
GG-48976	Cluster Storage Engine	Added two new event types EVT_PARTITIONS_STATE_VALIDATION_FAILED, EVT_PARTITIONS_STATE_VALIDATION_SUCCEEDED.

Issue ID

Enterprise Edition Changes

Issue ID	Category	Description
GG-49224	Builds and Deliveries	Updated Netty from version 4.1.133 to version 4.1.135.
GG-48889	Cluster Control Script	Exposed dr.sender.store_scan_policy on data nodes even if there is no local sender instance.
GG-48872	Cluster Data Replication	Added control.sh task for cleanup of DR queue at runtime.

Issue ID

Control Center Agent Changes

Issue ID	Category	Description
GG-49418	Control Center Agent	Updated awssdk from version 2.46.7 to version 2.46.11.
GG-49317	Control Center Agent	Managed deployment no longer occupies system threads for processing.
GG-49217	Control Center Agent	The Control Center Agent now sends system view feature flag to Control Center.
GG-49044	Control Center Agent	The Control Center Agent now sends system views information.

Issue ID

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.35, 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

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 Jul 07, 2026