Updated on 2023-03-15 GMT+08:00

Adding Cluster Instance Nodes

As service data increases, the number of current database nodes cannot meet the service requirements. In this case, you can add more nodes to the instance.

Precautions

  • To add nodes, instance status must be Available, Deleting backup, or Checking restoration.
  • Nodes cannot be added to a DB instance that is being backed up.
  • A DB instance cannot be deleted while nodes are being added.

Pricing Details

  • A pay-per-use instance is still billed on an hourly basis after new nodes are added.
  • If you add nodes to a yearly/monthly instance, you will pay price difference or get a refund.

Adding mongos Nodes

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click in the upper left corner of the page and choose Databases > Document Database Service.
  4. On the Instances page, click the cluster instance name.
  5. On the mongos tab in the Node Information area, click Add mongos.

    Figure 1 Node information

  6. On the displayed page, specify Node Class, Nodes, and Parameter Template and click Next.

    Figure 2 Adding mongos Nodes

    A Community Edition cluster instance supports up to 32 mongos nodes.

  7. On the displayed page, confirm the node configuration information.

    • Yearly/Monthly
      • 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 your settings, click Submit to go to the payment page and complete the payment.
    • Pay-per-use
      • 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 your settings, click Submit to add the nodes.

  8. View the results.

    • This process takes about 10 to 15 minutes. During that time, the status of the DB instance in the instance list is Adding node.
    • In the upper right corner of the DB instance list, click to refresh the list. The instance status changes to Available.
    • On the mongos tab in the Node Information area, view the information about the node you added.
    • If the mongos fail to be added, you can revert them in batches or delete them one by one. For details, see section Reverting Cluster Instance Nodes.

Adding shard Nodes

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click in the upper left corner of the page and choose Databases > Document Database Service.
  4. On the Instance Management page, click the target cluster instance.
  5. On the shard tab in the Node Information area, click Add shard.

    Figure 3 Node information

  6. Specify Node Class, Storage Space, Nodes, and Parameter Template and click Next.

    Figure 4 Add shard
    • The storage space you applied for will include the system overhead required for inode, reserved block, and database operation. The storage space must be a multiple of 10.
    • A Community Edition cluster instance supports up to 32 shard nodes.

  7. On the displayed page, confirm the node configuration information.

    • Yearly/Monthly
      • 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 your settings, click Submit to go to the payment page and complete the payment.
    • Pay-per-use
      • 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 your settings, click Submit to add the nodes.

  8. View the results.

    • This process takes about 10 to 15 minutes. The status of the DB instance in the instance list is Adding node.
    • In the upper right corner of the DB instance list, click to refresh the list. The instance status changes to Available.
    • On the shard tab in the Node Information area, view the information about the node you added.
    • If shard addition fails, you can rolls back the operation in batches or delete shards one by one. For details, see Reverting Cluster Instance Nodes.