GridGain 9.1.16 Release Notes

GridGain 9.1.16 brings a large number of new features, including a reworked JDBC driver, Java records support, custom object mapping in .NET, and new configuration options and metrics.

Overview

GridGain 9.1.16 is a private release that brings a large number of new features, including reworked JDBC driver and record support in Java.

Major Changes

New JDBC Driver Implementation

This release includes a complete rework of the JDBC driver. The new driver provides improved reliability, better connection management, support for connection pools and enhanced batch processing capabilities.

The example below shows how you can connect to multiple endpoints:

Connection conn = DriverManager.getConnection(
  "jdbc:ignite:thin://192.168.1.10:10800,192.168.1.11:10800,192.168.1.12:10800"
);

Additionally, the JDBC configuration was expanded with backgroundReconnectInterval and partitionAwarenessCacheSize properties, and units of measurement were added to connectionTimeoutMillis and queryTimeoutSeconds properties.

The previous JDBC driver is now deprecated and support for it will be removed in a later release. Make sure to migrate to the new JDBC driver.

New Features

Java Records Support

You can now use Java records to work with GridGain tables. The example below shows how you can create a simple record:

public record Person(
    @Column("id") Integer id,
    @Column("name") String name,
    @Column("age") Integer age
) {}

For more information about using records, see Record API documentation.

Custom Object Mapping in .NET

This release adds interfaces for custom row mapping in .NET thin client. You can use them for complex mapping scenarios or when reflection is limited (Native AOT).

The example below shows how to use reflection-free mapping:

public class PocoMapper : IMapper<Poco>
{
    public void Write(Poco obj, ref RowWriter rowWriter, IMapperSchema schema)
    {
        rowWriter.WriteLong(obj.Key);
        if (schema.Columns.Count > 1)
        {
            rowWriter.WriteString(obj.Val);
        }
    }
    public Poco Read(ref RowReader rowReader, IMapperSchema schema)
    {
        return new Poco
        {
            Key = rowReader.ReadLong()!.Value,
            Val = schema.Columns.Count > 1 ? rowReader.ReadString() : null
        };
    }
}

For more information about using improved mapping, see .NET client documentation.

Improved Configuration

In this release, cluster configuration is extended with a number of new configurations:

ignite.sql.statementMemoryQuota and ignite.sql.offloadingEnabled parameters can now be used to fine-tune SQL memory usage.
ignite.sql.statistics.autoRefresh.staleRowsCheckIntervalSeconds parameter can be used to fine-tune how often GridGain checks for stale rows.

Distribution Zones Reset

With the release, a new distribution zones data nodes reset command was added to the CLI tool. You can use this command to force the cluster to recalculate data nodes for given zones immediately. GridGain will ignore given zones' scale up and down timers. Data nodes reset will check the state of cluster topology and will trigger partition rebalance if required.

zone datanodes reset --zone-names=ZONE_NAME_1,ZONE_NAME_2

C++ Client Request Timeouts

C++ client now supports request timeouts. By default, request timeout is set to 0 (no timeout).

ignite_client_configuration cfg{"127.0.0.1"};
cfg.set_operation_timeout(std::chrono::seconds{2});
auto client = ignite_client::start(cfg, std::chrono::seconds(5));

For more information, see C++ client documentation.

ODBC Connection Heartbeats

You can now configure heartbeats in ODBC driver connection string with the HEARTBEAT_INTERVAL parameter. By default, heartbeat messages are sent every 30 seconds.

String Configuration Support

When starting the node in embedded mode, you can now provide configuration in string format. Previously, it was required to provide configuration as a path to the file.

For example:

Path myWorkDir = Path.of("/home/gridgain");

IgniteServer node = IgniteServer.start("node", "{"ignite":{"network":{"port":3344,"nodeFinder":{"netClusterNodes":["localhost:3344"]}}}}", myWorkDir);

Index Build Metrics

New metrics are available for monitoring secondary index building progress. The following index.builder metrics were added:

TotalIndexesBuilding - Total number of indexes the node is currently building.
IndexesReadingStorage - Number of indexes that are currently reading data from storage.
IndexesWaitingForTransactions - Number of indexes that are currently waiting for transactions to complete.
TransactionsWaitingFor - Number of transactions that indexes are currently waiting for.
IndexesWaitingForReplica - Number of indexes that are currently waiting for replica response.

SQL Virtual Column for Partition Information

A new virtual column __PARTITION_ID is now available in SQL queries. This column allows you to query which partition data resides in, enabling better partition-aware application logic.

Example usage:

SELECT id, name, __PARTITION_ID FROM my_table;

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

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?