GridGain 9.1.17 Release Notes

GridGain 9.1.17 brings monitoring improvements and new .NET features, removes APIs and REST endpoints for table-based partitions, and notes a Control Center compatibility requirement.

Overview

GridGain 9.1.17 is a private release that brings monitoring improvements and exciting new .NET features.

Major Changes

Removal of Table-Based Partitions

This release starts removing APIs and system views that were used for working with table-based partitions that are no longer supported since GridGain 9.1.15.

Removed System Views

In this release, the GLOBAL_PARTITION_STATES and LOCAL_PARTITION_STATES system views were removed. Make sure to use the GLOBAL_ZONE_PARTITION_STATES and LOCAL_ZONE_PARTITION_STATES zone-based system views instead.

Removed REST Endpoints

In this release, table-based data recovery REST endpoints were removed.

The /management/v1/recovery/partitions/restartWithCleanup is replaced by /management/v1/recovery/zone/partitions/restartWithCleanup,
The /management/v1/recovery/partitions/reset is replaced by /management/v1/recovery/zone/partitions/reset,
The /management/v1/recovery/state/global is replaced by /management/v1/recovery/zone/state/global,
The /management/v1/recovery/state/local is replaced by /management/v1/recovery/zone/state/local,
The /management/v1/recovery/partitions/restart is replaced by /management/v1/recovery/zone/partitions/restart.

If you were using the removed endpoints for monitoring and managing your partitions, make sure to switch to the new ones. As the new endpoints use zone-based partitions, all table-related fields are no longer applicable and have been removed. Make sure to modify your requests appropriately. For more information on the new request and response fields, see the OpenAPI specification.

Control Center Incompatibility

Due to the changes in the sections above, Control Center 2025.5 and earlier are not compatible with GridGain 9.1.17. The Control Center 2025.5.2 patch release addressed these compatibility issues.

If you are using Control Center to monitor your GridGain 9 cluster, upgrade your Control Center to version 2025.5.2 and before updating to GridGain 9.1.17.

New Features

Timed SQL Requests

A new --timed option has been added to the CLI, and can be used to measure the execution time of SQL queries and other CLI commands. When enabled, the timing information includes the total execution time for the command. The timing information is displayed after the query results in the CLI.

Example usage:

sql --timed "select * from system.system_views;"

Improved Snapshots Monitoring

A new snapshot list CLI command has been added to help administrators monitor and manage cluster snapshots. This command provides visibility into all available snapshots, including those stored on remote paths.

ignite3 snapshot list

Expanded Metrics

This release adds new metrics to improve monitoring aipersist storage. The metrics cover checkpoint behavior.

Another set of new metrics helps monitor Raft snapshots activity, providing better visibility into the snapshot lifecycle. These metrics help detect stalled replication, slow recovery and excessive snapshot load.

Storage Metrics

Checkpoint Metrics
- ReadLockAcquisitionTime – Time from requesting the checkpoint read lock until acquisition, in nanoseconds.
- ReadLockHoldTime – Duration between checkpoint read lock acquisition and release, in nanoseconds.
- ReadLockWaitingThreads – Current number of threads waiting for the checkpoint read lock.

Raft Snapshot Metrics

IncomingSnapshots – Number of incoming Raft snapshots currently in progress.
IncomingSnapshotsLoadingMeta – Number of incoming Raft snapshots loading metadata.
IncomingSnapshotsWaitingCatalog – Number of incoming Raft snapshots waiting for catalog availability.
IncomingSnapshotsPreparingStorages – Number of incoming Raft snapshots preparing storages.
IncomingSnapshotsPreparingIndexForBuild – Number of incoming Raft snapshots preparing indexes for build.
IncomingSnapshotsLoadingMvData – Number of incoming Raft snapshots loading multi-versioned data.
IncomingSnapshotsLoadingTxMeta – Number of incoming Raft snapshots loading transaction metadata.
OutgoingSnapshots – Number of outgoing Raft snapshots currently in progress.

.NET Improvements

.NET Custom Mapping Support

This release introduces new IMapper<T> support to SQL, Compute and PartitionManager .NET APIs, enabling custom object mapping for serialization and deserialization, including AOT-friendly scenarios where reflection-based mapping is not suitable.

For example, that is how you use it to create a colocated compute job target for a specific table and key:

public sealed class PocoMapper : IMapper<Poco> {}
IJobTarget<Poco> target = JobTarget.Colocated("PUBLIC.MY_TABLE", key, new PocoMapper());

For more details on usage of IMapper<T> see corresponding SQL and Partition Manager API sections.

.NET Client AOT Compilation

This release adds official support for Native AOT. Applications using the .NET client can be compiled in AOT mode. Most client APIs are supported. Unsupported APIs (LINQ and reflection-based mappers) will produce trim warnings during build.

.NET Continuous Query API

Continuous Query .NET API is extended with the new IContinuousQueryWatermark.AfterTransaction interface to allow the user to obtain a consistent view of table data and future updates.

This is how to start a continuous query with transaction watermark:

var watermark = IContinuousQueryWatermark.AfterTransaction(tx);

Improvements and Fixed Issues

Issue ID

Upgrade Information

You can upgrade to current GridGain version from previous releases. Below is a list of versions that are compatible with the current version. Compatibility with other versions is not guaranteed. If you are on a version that is not listed, contact GridGain for information on upgrade options.

9.1.8, 9.1.9, 9.1.10, 9.1.11, 9.1.12, 9.1.13, 9.1.14, 9.1.15, 9.1.16

When performing a rolling upgrade from GridGain 9.1.8 or 9.1.9, it is required to update to 9.1.10 first.

When updating from older versions, we recommend updating to version 9.1.8 first, before performing an update to current version.

Client Compatibility

GridGain Clients

GridGain clients and servers are both backward and forward compatible. An older client can connect to a newer server, and a newer client can connect to an older server. As a result, clients and servers can be upgraded independently and in any order.

GridGain JDBC Driver

GridGain JDBC driver was reworked in GridGain 9.1.16. The new driver is only compatible with GridGain 9.1.16 or newer. Previously used JDBC driver is forwards-compatible with newer server, however it is deprecated and support for it will be removed in a later release.

Apache Ignite 3 Clients

Apache Ignite thin clients are not compatible with GridGain. When switching to GridGain, change the dependency to GridGain client as described in the GridGain client documentation.

Known Limitations

Rolling Upgrade Over 9.1.10

When performing a rolling upgrade from GridGain 9.1.9 or earlier, it is necessary to first upgrade to 9.1.10 before upgrading to 9.1.11 or a later version. This is caused by improvements in rolling upgrade procedure that make skipping 9.1.10 with a rolling upgrade impossible.

The upgrade to 9.1.10 must be performed for the whole cluster and committed before the next upgrade can be started.

You do not need to perform this intermediary upgrade when upgrading with downtime, as it only affects the rolling upgrade procedure.

Data Restoration After Data Rebalance

Currently, data rebalance may cause partition distribution to change and cause issues with snapshots and data recovery. In particular:

It is currently not possible to restore a LOCAL snapshot if data rebalance happened after snapshot creation. This will be addressed in one of the upcoming releases.
It is currently not possible to perform point-in-time recovery if data rebalance happened after table creation. This will be addressed in one of the upcoming releases.

SQL Performance in Complex Scenarios

There are known issues with the performance of SQL read-write transactions in complex read-write scenarios. These issues will be addressed in upcoming releases.

We Value Your Feedback

Your comments and suggestions are always welcome. You can reach us here: http://support.gridgain.com/.

Last updated 7 days ago

Was this helpful?