Common issues that occur during the O&M of Lindorm instances - Lindorm

This topic provides FAQs about Lindorm instances in O&M scenarios, such as instance scaling, configuration upgrade and downgrades, instance restarts, and version upgrades. The FAQs involve various aspects, including operation duration, business impact, and fees and can help you understand the details and usage notes of O&M operations.

Overview

How long does it take to scale out the nodes of an instance?

The scale-out of nodes is performed in parallel. It takes about 10 to 15 minutes to scale out a single node. If your instance has a large number of nodes, the scale-out process may take a long time.

What is the impact on my business during the node scale-out?

During the scale-out of nodes in an instance, the instance can still handle read and write requests. Your business that runs on the instance is not interrupted. However, the average latency of some read and write requests jitters. Make sure that the client is configured to reconnect to the instance. If your business is sensitive to the latency of read and write requests, we recommend that you perform the scale-out during off-peak hours.

How long does it take to scale out the storage capacity of an instance? What is the impact on my business during the scale-out?

You can scale out storage capacity only for instances that use the Standard, Performance, and Capacity types of storage. It takes minutes to scale out the storage capacity of an instance. Your business that runs on the instance is not interrupted. If your instance used local SSDs or HDDs, you cannot directly scale out the storage capacity of the instance. In this case, you can add nodes to the instances to scale out the storage capacity.

How long does it take to enable cold storage? What is the impact on my business during the process?

When you enable cold storage for an instance, the nodes in the instance are restarted in sequence. It takes about 10 to 15 minutes to restart a single node. For example, if your instance contains four nodes, it takes about 60 minutes to enable cold storage for the instance.

The estimated time required to enable cold storage depends on the number of regions in the node. The more regions in a node, the more time required for the process.

During the restart, the instance can still handle read and write requests. Your business that runs on the instance is not interrupted. However, the average latency of some read and write requests jitters and the connection to the instance may be interrupted. Make sure that the client is configured to reconnect to the instance. If your business is sensitive to the latency of read and write requests, we recommend that you upgrade the instance configurations during off-peak hours.

How long does it take to scale out the cold storage capacity of an instance? What is the impact on my business during the scale-out?

It takes minutes to scale out the cold storage capacity of an instance. Your business that runs on the instance is not interrupted.

How long does it take to upgrade the configurations of an instance? What is the impact on my business during the upgrade?

The time required to upgrade the configurations of an instance depends on the number of nodes in the instance. When you upgrade the configurations of an instance, the nodes in the instance are upgraded in sequence. It takes about 10 to 15 minutes to upgrade a single node. For example, if your instance contains four nodes, it takes about 60 minutes to upgrade the configurations of the instance.

The estimated time required to upgrade a node depends on the number of regions in the node. The more regions in a node, the more time required for the process.

During the configuration upgrade, the instance can still handle read and write requests. Your business that runs on the instance is not interrupted. However, the average latency of some read and write requests jitters and the connection to the instance may be interrupted. Make sure that the client is configured to reconnect to the instance. If your business is sensitive to the latency of read and write requests, we recommend that you upgrade the instance configurations during off-peak hours.

How long does it take to scale in the nodes of an instance?

The time required for the data migration during the scale-in can be calculated based on the following formula: Total amount of data to migrate/(Number of nodes/30 MB/s). For example, the current instance stores 10 TB of data among 10 nodes, in which two nodes need to be scaled in. Data is evenly distributed among all nodes in the instance. Therefore, 2 TB of data needs to be migrated. The time required for the data migration during the scale-in can be calculated as follows: 2 TB/(10 x 30 MB/s) = 6990.5 seconds ≈ 2 hours.

Important

This time is only an estimate. The actual time required for scale-in varies based on the business load and storage medium.
If the usage of any storage medium becomes higher than 85% after the scale-in, the scale-in task cannot be submitted. For more information about the fees after scale-in, see Rules for unsubscribing from resources.

What is the impact on my business during the node scale-in?

During the scale-in, the instance can still handle read and write requests. Your business that runs on the instance is not interrupted.

How long does it take to downgrade the configurations of an instance? What is the impact on my business during the downgrade?

The time required to downgrade the configurations of an instance depends on the number of nodes in the instance. When you downgrade the configurations of an instance, the nodes in the instance are downgraded in sequence. It takes about 10 to 15 minutes to downgrade a single node. For example, if your instance has four nodes, it takes about 60 minutes to downgrade the configurations of the instance.

The estimated time required to downgrade a node depends on the number of regions in the node. The more regions in a node, the more time required for the process.

When you downgrade the configurations of an instance, the nodes in the instance are restarted in sequence. During the downgrade, the instance can still handle read and write requests. Your business that runs on the instance is not interrupted. However, the average latency of some read and write requests jitters and the connection to the instance may be interrupted. Make sure that the client is configured to reconnect to the instance. If your business is sensitive to the latency of read and write requests, we recommend that you downgrade the instance configurations during off-peak hours.

For more information about the fees after configuration downgrade, see Rules for unsubscribing from resources.

How long does it take to upgrade the minor version of an instance?

For LindormDFS: It takes about 10 to 15 minutes to upgrade the minor version for a single node. The upgrade is performed on each node in sequence. For example, if your instance has four LindormDFS nodes, it takes about 60 minutes to upgrade LindormDFS minor version of the instance.
For LindormTable: It takes about 10 to 15 minutes to upgrade the minor version for a single node. The upgrade is performed on each node in sequence. For example, if your instance has four LindormTable nodes, it takes about 60 minutes to upgrade the LindormTable minor version of the instance.

Can I select a minor version for minor version upgrade?

The minor version cannot be selected during the minor version upgrade. By default, the minor version of a Lindorm engine is upgraded to the latest stable version that is forward compatible.

What is the impact on my business during the minor version upgrade?

For LindormDFS: Your business that runs on the instance is basically not affected during the minor version upgrade.
For LindormTable: During the minor version upgrade, the instance can still handle read and write requests. Your business that runs on the instance is not interrupted. However, the average latency of some read and write requests jitters and the connection to the instance may be interrupted. Make sure that the client is configured to reconnect to the instance. If your business is sensitive to the latency of read and write requests, we recommend that you downgrade the instance configurations during off-peak hours.

How long does it take to restart an instance? What is the impact on my business during the restart?

When you restart an instance, the nodes in the instance are restarted in sequence. It takes about 10 to 15 minutes to restart a single node. For example, it takes about 60 minutes to restart an instance that contains four nodes.

The estimated time required to restart the instance depends on the number of regions in the node. The more regions in a node, the more time required for the process.