All Products
Search

This Product

    Lindorm:Modify the configurations of an instance

    Document Center

    Lindorm:Modify the configurations of an instance

    Last Updated:Jul 17, 2026

    Deactivate, change, and scale engines in Lindorm instances.

    Prerequisites

    • Ensure you have a Lindorm instance that is in the Running state. For more information, see Create an instance.

    • The Service Type of the instance is Lindorm V1 or Lindorm.

    • Before you deactivate an engine, complete the following tasks:

      • For Lindorm Tunnel Service (LTS): Delete all tasks before you deactivate the engine.

        Note

        You cannot deactivate LTS if it has active backup tasks, full-text search synchronization tasks, or other custom tasks.

      • For other engines: Clear all data from the engine before you deactivate it.

        Important

        You cannot deactivate an engine if it contains business data. Before you clear the data, back up your important data.

    Usage notes

    • The engine deactivation feature is in public preview. To use this feature, contact Lindorm technical support (DingTalk ID: s0s3eg3) to enable it for your account.

    • After you deactivate an engine, all data stored in it is cleared. To prevent data loss, back up your data in advance.

    • Deactivating an engine does not affect the read and write operations on other engines. During this process, the instance enters the Scaling in Node state. You cannot perform other management operations, such as enabling services or scaling the instance, until the instance returns to the Running state.

    • Changing the instance type may cause minor service jitter. The instance status changes to Changing Specifications. During this process, you can continue to read and write data, but other management operations like enabling services or changing nodes are unavailable. Perform this operation during off-peak hours to minimize impact.

    • When downgrading an engine's instance type, ensure the new configuration can handle your business workload.

    • When you evaluate the appropriate instance type for your workload, consider multiple factors beyond just read and write request volumes.

    • A cloud disk instance must retain at least two nodes to ensure service availability during maintenance.

    • A local disk instance stores data in three replicas. To maintain redundancy despite a node failure, keep at least three nodes.

    • When removing nodes, ensure the remaining nodes can handle your workload.

    Deactivate an engine

    Limitations

    • If the Service Type of your instance is Lindorm V1, you can only deactivate LTS and LindormSearch. Other engines cannot be deactivated.

    • If the Service Type of your instance is Lindorm, you can deactivate all engines except for the compute engine, message engine, and underlying storage.

    Billing

    For more information about unsubscription rules and the refund flow, see Rules for unsubscribing from resources and Refund flow.

    Procedure

    1. Log on to the Lindorm console.

    2. In the upper-left corner of the page, select the region where the instance is deployed.

    3. On the Instances page, click the ID of the target instance or click View Instance Details in the Actions column for the instance.

    4. In the Configurations section, find the engine that you want to deactivate and choose Deactivate Engine in the Actions column.

    5. Click OK. The downgrade page appears.

    6. Set the number of nodes for the engine to 0. To reduce the storage capacity of the instance, you can also drag the slider.

      Important

      • The amount of storage capacity you can reduce depends on the instance configuration and is limited to the minimum supported value.

      • When you deactivate LTS, you can only reduce the number of nodes. You cannot reduce the storage capacity.

    7. Read and select the terms of service, and then click Buy Now.

      Important

      The downgrade page displays the price for the new configuration.

    Change instance type

    Procedure

    The required steps vary depending on the Service Type of your instance.

    Lindorm instance

    1. Log on to the Lindorm console. In the upper-left corner of the page, select the region of the instance. On the Instances page, click the ID of the target instance or click View Instance Details in the Actions column for the instance.

    2. In the Configurations section, do one of the following:

      • To upgrade the instance type: In the Actions column for the target engine, click Upgrade Specifications.

      • To downgrade the instance type: In the Actions column for the target engine, choose image > Downgrade.

      Note

      Upgrade Specifications, Downgrade, and Search Engine support both Upgrade Instance Type and Downgrade Instance Type. Other engine types may support only some configuration changes. The options available in the console take precedence.

    3. On the Downgrade or Upgrade/Downgrade page, configure the engine's node specifications. For more information about how to select node specifications, see Select node specifications and quantity.

    4. Agree to the terms of service and click Buy Now.

      During the change, the instance status is Changing Specifications. The process is complete when the status returns to Running.

      Note

      The time required for the change depends on the number of engine nodes, typically 2 to 10 minutes per node.

    Lindorm V1 instance

    1. Log on to the Lindorm console. In the upper-left corner of the page, select the region of the instance. On the Instances page, click the ID of the target instance or click View Instance Details in the Actions column for the instance.

    2. In the Configurations section, click Upgrade Specifications in the Actions column of the target engine.

    3. On the Downgrade or Upgrade/Downgrade page, click the image icon in the top-right corner of the engine card to modify the node specifications.

    4. Agree to the terms of service and click Buy Now.

      During the change, the instance status is Changing Specifications. The process is complete when the status returns to Running.

      Note

      The time required for the change depends on the number of engine nodes, typically 2 to 10 minutes per node.

    LTS

    1. Log on to the Lindorm console. In the upper-left corner of the page, select the region of the instance. On the Instances page, click the ID of the target instance or click View Instance Details in the Actions column for the instance.

    2. In the Configurations section, click Manage, and then select Upgrade Specifications or Downgrade.

    3. On the Downgrade or Upgrade/Downgrade page, modify the Node Specifications.

    4. Agree to the terms of service and click Buy Now.

      During the change, the instance status is Changing Specifications. The process is complete when the status returns to Running.

      Note

      The time required for the change depends on the number of nodes, typically 2 to 10 minutes per node.

    Scale instance nodes

    Procedure

    The procedure varies based on the Service Type of your instance.

    Lindorm instance

    1. Log on to the Lindorm console. In the upper-left corner of the page, select the region of the instance. On the Instances page, click the ID of the target instance or click View Instance Details in the Actions column for the instance.

    2. Modify the node count.

      • To add nodes: In the Configurations section, find the target engine and click Create Node in the Actions column.

      • To remove nodes: In the Configurations section, find the target engine and select image.png > Reduce Nodes in the Actions column.

        Important

        【Lindorm instance - Local disk】A local disk instance must retain at least three nodes for three-replica redundancy.

    3. On the Upgrade/Downgrade page, set the node count and storage capacity.

      Note

      Select node specifications and quantity for node count recommendations.

    4. Click Create.

      During scaling, the instance status changes to Changing Specifications. When it returns to Running, the scaling is complete.

      Note

      Scaling typically takes 2 to 10 minutes per node.

    Lindorm V1 instance

    Important

    【Lindorm V1 instance】A Lindorm V1 production instance requires at least 2 nodes; a test instance requires at least 1 node.

    1. Log on to the Lindorm console. In the upper-left corner of the page, select the region of the instance. On the Instances page, click the ID of the target instance or click View Instance Details in the Actions column for the instance.

    2. In the Configurations section, find the target engine and click Create Node in the Actions column.

    3. On the Upgrade/Downgrade page, click image in the upper-right corner of the engine card to modify the node count.

    4. Click Create.

      During the specification change, the instance status is Changing Specifications. When it returns to Running, the operation is complete.

      Note

      The operation typically takes 2 to 10 minutes per node.

    LTS

    1. Log on to the Lindorm console. In the upper-left corner of the page, select the region of the instance. On the Instances page, click the ID of the target instance or click View Instance Details in the Actions column for the instance.

    2. In the Configurations section, click Manage and select Reduce Nodes or Create Node from the drop-down list.

    3. On the Upgrade/Downgrade page, modify the number of nodes.

      Important

      【LTS】An LTS instance requires a minimum of three nodes. You cannot remove nodes from an instance with only three nodes.

    4. Click Create.

      During the specification change, the instance status is Changing Specifications. When it returns to Running, the operation is complete.

      Note

      The operation typically takes 2 to 10 minutes per node.