What to Know Before Upgrading
Planning reference for upgrading from GridGain 8.9 to 8.10: choosing a rolling or offline upgrade, upgrade constraints, and the scope and effort of each change.
Read this page before you upgrade a cluster from GridGain 8.9.39 to 8.10. It helps you choose an upgrade path, find the changes that affect you, and estimate the work. When you are ready, follow the Upgrade Procedure.
Supported Starting Versions
You can upgrade to 8.10 from the following 8.9.x releases.
Choose Your Upgrade Path
Rolling upgrade. You upgrade the nodes one at a time while the cluster stays available. It uses Rolling Upgrades, an Enterprise and Ultimate feature, and requires
rollingUpdatesEnabled=trueon every 8.9 node.Offline upgrade. You stop the cluster and start every node from the 8.10 distribution. It does not need
rollingUpdatesEnabled.
The right path depends on your 8.9 cluster:
Every node has rollingUpdatesEnabled=true
Rolling upgrade, with no downtime for the upgrade itself. On Enterprise Edition, the backup needs a short stop of the whole cluster. See Step 3.
rollingUpdatesEnabled is not set, and you can schedule one full-cluster restart
Offline upgrade in that window. It is simpler, because you stop the cluster anyway.
rollingUpdatesEnabled is not set, and you want a rolling upgrade
Restart the whole cluster once with the property set, then upgrade. See Step 2.
Upgrade Constraints
Java 17 or later is required. Every server node, client application, and application that embeds GridGain must run on it. See Java 17 or Later.
Downgrade is not supported. An 8.9 node cannot join the cluster after the rolling upgrade is finished. Back up the 8.9 data first. On Ultimate Edition, take a full snapshot. On Enterprise Edition, which has no snapshots, copy the
dbfolder of every node, and also the folders thatstoragePath,walPath, andwalArchivePathpoint to if you set them. After the upgrade, restoring that backup is the only way to recover 8.9, and everything written after the backup is lost. See Recovery Path.Caches without backups are unavailable during a rolling upgrade. Partitions on a stopped node cannot be served. See Application Behavior During a Rolling Upgrade.
Some integrations have no 8.10 replacement. Mesos deployments stay on 8.9.x. See Removed Modules and Integrations.
Which Pages Apply to You
Cluster administrators install, configure, and run the server nodes. Read the whole guide, starting with the Upgrade Procedure.
Application developers embed GridGain or connect to a cluster that someone else administers. Read Platform, Modules, and Packaging Changes, Client and Driver Changes, and the permission and REST changes in Security, Permission, and Licensing Changes. Coordinate the switch with the cluster administrators.
Teams that maintain operational tooling such as monitoring, scripts, and automation read Configuration and Default Value Changes, and the
control.sh, snapshot, and rolling-upgrade commands in the Upgrade Procedure.
Upgrade Scope and Effort
The tables list each change, when it applies to you, and the effort it needs. If an item does not apply to your deployment, skip it.
Effort is one of the following:
Mechanical. A rename, path change, or similar update with no logic changes.
Config-only. Set, remove, or restore a configuration property. No code changes.
Code. A contained code change, such as a renamed API call.
Redesign. Adopt a different system or API. Expect design work and retesting.
Contact Support. No documented replacement exists. Contact MariaDB support before you upgrade.
A range such as Mechanical to Code means that the effort depends on what you use.
For Application Developers
Java 17 or later
Always: embedding applications, the thin client, and the JDBC driver
Mechanical
Spring 7 and Spring Data module rename
Your application embeds GridGain through Spring
Mechanical to Code
AWS module replaced by ignite-aws-ext
You use the S3 checkpoint SPI or the S3, ELB, or ALB IP finders
Code
Machine learning module replaced by an extension
You use ignite-ml
Code
Local store replaced by native persistence or CacheStore
You use @CacheLocalStore or CacheFileLocalStore
Redesign
Cassandra store on DataStax driver 4
You use the Cassandra store
Code
Modules with no replacement
You use Mesos. Stay on 8.9.x or move to another system
Redesign
Java thin client timeouts
A thin client operation runs longer than 60 seconds
Config-only
Thin clients in a mixed-version cluster
An 8.10 client uses vector indexes or withPartitionRecover() against an 8.9 server, including during a rolling upgrade
Config-only
.NET and C++ client changes
You use the .NET or C++ client
Mechanical to Code
REST scan queries with a filter class
You send EXECUTE_SCAN_QUERY with className
Config-only
Thin client permission and filter checks
Thin clients call Java services or register continuous query remote filters
Config-only
JMX object metrics are strings
A JMX tool reads ObjectMetric attributes
Code
For Cluster Administrators
Per-feature license checks
Always. Compare your license with your configuration
Config-only
Jetty 12
You use a custom jetty.xml for the REST connector
Config-only
SFTP host key verification
You send snapshots to an SFTP destination
Config-only
Vector search limits
You use vectors with more than 4096 dimensions, or request more than 10000 neighbors
Config-only
Stale system properties
Your startup scripts set an unsupported Apache Ignite property
Config-only
Control Center agent and OpenCensus
Your 8.9 node loads control-center-agent or ignite-opencensus
Mechanical
This page is: Copyright © 2026 MariaDB. All rights reserved.
Last updated
Was this helpful?

