When a new minor engine version is released, you can upgrade the engines of your Lindorm instance to the latest minor version from the Lindorm console. A minor engine version upgrade delivers feature optimizations and new capabilities for the current version.
Prerequisites
Before you begin, ensure that you have:
A Lindorm instance. For details, see Create an instance
Service impact by engine
Review the expected impact before scheduling the upgrade:
| Engine | Service availability | Impact |
|---|---|---|
| LindormTable, underlying files, compute engine | Available | Read and write operations may experience jitter |
| LindormTSDB | May become unavailable | Service disconnection or unavailability for a short period; more engine nodes means longer duration |
| LindormSearch | May become unavailable | Service disconnection or unavailability for a short period; more engine nodes means longer duration |
| All engines | — | Network jitter may occur |
During the upgrade, management operations such as enabling a service or changing instance configurations are unavailable.
Before you upgrade
The instance restarts to apply the upgrade. Schedule the upgrade during off-peak hours, or make sure your application can automatically reconnect after restart.
Upgrade duration varies by the number of instances deployed in the region. More instances result in a longer upgrade.
Minor engine version upgrades cannot be rolled back. For LindormTSDB, upgrade to Stable Version to reduce the risk of unexpected issues.
Upgrade the minor engine version
Log on to the Lindorm console.
In the upper-left corner of the page, select the region where the instance is deployed.
On the Instances page, click the ID of the target instance or click View Instance Details in the Actions column.
In the Configurations section, click the
icon in the Actions column for the engine you want to upgrade.Click Upgrade Minor Version.
NoteClick the
icon next to an engine to view its current version details.
In the Upgrade Minor Version dialog box, set Target Version.
ImportantLindormTSDB supports upgrading to Latest Version or Stable Version. All other engines upgrade to Latest Version only.
Upgrades cannot be rolled back. For LindormTSDB, use Stable Version to reduce risk.
Click OK.
FAQ
Is the service affected during the upgrade?
Yes. The impact depends on which engine you are upgrading. See the Service impact by engine table for details. Schedule upgrades during off-peak hours to minimize disruption.
Are existing SDK calls affected after the upgrade?
No. Minor engine version upgrades do not remove or modify API operations, so existing SDK calls continue to work.
Can I choose the target version for the upgrade?
LindormTSDB supports upgrading to either Latest Version or Stable Version. All other engines always upgrade to Latest Version.
Can I upgrade multiple engines at the same time?
No. Complete the upgrade of one engine before starting the next.
Can I roll back after a minor engine version upgrade?
No. Minor engine version upgrades cannot be rolled back. For LindormTSDB, upgrade to Stable Version to reduce the risk of unexpected issues.