GridGain 9.1.24 Release Notes

GridGain 9.1.24 adds leaseholder balancing, improves the .NET cluster API, SQL system views, SQL planning, and transactions, and fixes issues in SQL, thin clients, and continuous queries.

Overview

GridGain 9.1.24 adds leaseholder balancing and improves .NET cluster API. It also extends SQL system views, improves SQL planning and transaction handling, and fixes a number of issues across the SQL engine, thin clients, and continuous queries.

Major Changes

JitPack Repository No Longer Required

GridGain no longer depends on artifacts published on JitPack. The dependency that previously required the jitpack.io repository (see the 9.1.21 release notes) is now served from the GridGain Maven repository.

It is recommended to remove jitpack.io dependency from your pom.xml to keep your configuration clean. If not updated, GridGain will automatically switch to the new source, and leave an unnecessary dependency in configuration.

New Features

.NET Compute Executor Runtime Configuration

The new ignite.compute.dotnet node-configuration section lets you tune the .NET runtime of the compute executor (sidecar) process. You can toggle Server GC and cap the executor's memory with an absolute or percentage-based GC heap hard limit.

ignite.compute.dotnet {
    serverGc = true               // enable .NET Server GC (default: true)
    gcHeapHardLimit = "512m"      // absolute GC heap hard limit; "" means no limit (default)
    gcHeapHardLimitPercent = 0    // GC heap hard limit as a percent of physical memory, 1-100; 0 means no limit (default)
}

See .NET Compute Executor for more information.

.NET Client: Cluster API

The .NET client adds the IIgnite.Cluster API, which exposes the cluster topology. Use Cluster.GetNodesAsync() to retrieve all nodes in the logical topology, and Cluster.LocalNode to get the hosting node from inside a compute job or data streamer receiver (it returns null on the client side). The previous IIgnite.GetClusterNodesAsync() method is now deprecated in favor of Cluster.GetNodesAsync().

// From the client: list all nodes in the cluster.
IList<IClusterNode> nodes = await client.Cluster.GetNodesAsync();

// Inside a compute job: the node that runs the job.
IClusterNode? local = context.Ignite.Cluster.LocalNode;

See Cluster API for more information.

CLI Command to Balance Leaseholders

GridGain 9 now lets you manually rebalance primary replica leaseholders across cluster nodes. The new distribution balance-leases CLI command tells the placement driver to redistribute leaseholders evenly - one leaseholder per replication group - forcing the move to a less-loaded node.

distribution balance-leases

See CLI tool documentation.

Idempotent Cluster Initialization

The cluster init CLI command now accepts two optional flags that make it safe to re-run from scripts and automation. Use --if-needed to skip initialization and exit with code 0 when the cluster is already initialized instead of failing. Add --if-nodes=<N> (which requires --if-needed) to also defer initialization until at least N nodes are visible in the physical topology.

cluster init --name=myCluster --license=/path/to/license --if-needed --if-nodes=3

See CLI tool documentation.

Data Streamer and Continuous Query Cooperation

The data streamer can now control how same-key updates within a single batch are surfaced to continuous queries. The new DataStreamerOptions.sameKeyUpdateMode option takes a DataStreamerSameKeyUpdateMode value: SQUASH (default) conflates multiple updates to the same key within a batch into a single continuous query event for better performance, while PRESERVE splits the batch so that each update produces a separate continuous query event.

var options = DataStreamerOptions.builder()
    .sameKeyUpdateMode(DataStreamerSameKeyUpdateMode.PRESERVE)
    .build();

See same-key update mode and continuous query events for more information.

Schema-Qualified Objects in SQL GRANT/REVOKE

SQL GRANT/REVOKE PRIVILEGES ... ON <object> now accepts a schema-qualified object name. A schema-qualified name such as PUBLIC.MY_TABLE grants the privilege on that single object, while a bare name such as PUBLIC still targets the whole schema. This lets you scope object-level privileges - for example, CREATE_INDEX on a specific table - directly from SQL.

GRANT PRIVILEGES CREATE_INDEX ON PUBLIC.MY_TABLE TO role1;

See GRANT for details.

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, 9.1.17, 9.1.18, 9.1.19, 9.1.20, 9.1.21, 9.1.22, 9.1.23

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.

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 1 day ago

Was this helpful?