Advanced
Тема интерфейса

Scaling Up a Cluster Instance

You can scale up the storage space of an instance, and the backup space increases accordingly.

  • If the purchased storage space exceeds 600 GB and the available storage space is 18 GB, the database will be set to the read-only state when the disk is full.
  • If the purchased storage space is less than or equal to 600 GB and the storage usage reaches 97%, the database is set to the read-only state.

In addition, you can set alarm rules for the storage space usage.

Precautions

  • Scaling is available when your account balance is sufficient.
  • For cluster instances, only shard nodes can be scaled up, and dds mongos and config nodes cannot be scaled up.
  • For a cluster instance, each shard can be scaled up for a maximum of eight times.
  • Storage space can only be scaled up. It cannot be scaled down.
  • If you scale up a DB instance with disks encrypted, the expanded storage space will be encrypted using the original encryption key.
  • An instance cannot be scaled up if it is in any of the following statuses:
    • Creating
    • Changing instance class
    • Adding node
    • Deleting node
    • Upgrading minor version
  • Services are not interrupted during scaling. The storage type cannot be changed.

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Document Database Service to go to the DDS console.
  4. On the Instances page, click the cluster instance name.
  5. In the Node Information area on the Basic Information page, click the shard tab, locate the shard node you want to scale, and click Scale Storage Space in the Operation column.
  6. On the displayed page, specify the desired amount of space to be added and click Next.

    Select at least 10 GB each time you scale up the storage, and the storage size must be multiples of 10 GB.

    If a shard node has fewer than 8 vCPUs, the maximum storage that can be scaled up to is 5,000 GB. If a shard node has 8 or more vCPUs, the maximum storage that can be scaled up to is 10,000 GB.

  7. On the displayed page, confirm the storage space.

    • If you need to modify your settings, click Previous to go back to the page for you to specify details.
    • If you do not need to modify the specifications, click Submit to scale up the storage space.

  8. Check the results.

    • This process takes about 3 to 5 minutes. The status of the DB instance in the instance list is Scaling up.
    • In the upper right corner of the instance list, click to refresh the list. The instance status changes to Available.
    • In the Node Information area on the Basic Information page, click the shard tab and check whether the scale up was successful.

Caution

If the storage space is scaled up to more than 4 TB, the following risks may occur:

  • If there is a large amount of data, the backup task may take a long time or even fail. In this case, the service SLA may be affected.
  • If data is deleted by mistake, it takes a long time to restore a table to a specified point in time or restore a backup to a new instance, affecting the restoration efficiency.
  • If the primary/secondary or read-only replication is delayed, it takes a long time to reconnect. As a result, the instance may be disconnected or fail to be reconnected.