After you create an ApsaraDB for MyBase dedicated cluster, you can view, modify, and delete the dedicated cluster.

Background information

For more information about ApsaraDB for MyBase, see What is ApsaraDB for MyBase?.

View the basic information about an ApsaraDB for MyBase dedicated cluster

  1. Log on to the ApsaraDB for MyBase console.
  2. In the upper-left corner of the page, select the region where you want to deploy the dedicated cluster.
    Select a region
  3. On the Clusters page, view the dedicated cluster information. You can also download the information to an on-premises location.
    • By default, the Dedicated Cluster ID, VPC, and Hosts columns are displayed on the list. You can click The Custom Columns icon to select columns to be displayed.Specify the columns that you want to view for a dedicated cluster
    • You can click The Export Resources icon to download the information about the dedicated clusters to an on-premises location.
  4. Find the dedicated cluster that you want to view, and click Details in the Actions column.
  5. On the Basic Information page, view the parameter settings of the dedicated cluster.
    View the basic information about a dedicated cluster.The following table describes the parameters.
    Parameter Description
    Dedicated Cluster ID/Name The ID and the name of the dedicated cluster.
    VPC The virtual private cloud (VPC) to which the dedicated cluster is connected.
    Hosts The number of hosts in the dedicated cluster.
    Instances The number of instances in the dedicated cluster.
    Host Troubleshooting Policy The policy that is used to handle host failures in the dedicated cluster.
    • Automatic Host Replacement: The system automatically replaces faulty hosts.
      Note
      • If a faulty host uses disks, the host is replaced only after the auto snapshot feature of the host storage is enabled.
      • If a faulty host uses local disks, the host is replaced only after all instances are removed from the host.
    • Manual Host Replacement: You must manually replace faulty hosts.
    Resource Allocation Policy The policy that is used by default to schedule resources in the dedicated cluster.
    • Balanced Allocation: New database instances are preferentially created on hosts that have the most available resources to maximize cluster stability.
    • Compact Allocation: New database instances are preferentially created on hosts where existing instances are created. This maximizes resource utilization.
    CPU Overcommit Ratio The CPU overcommitment ratio of the dedicated cluster. For example, if the CPU overcommitment ratio is 200%, the CPU resources that can be allocated are twice as many as the CPU resources that are provided. This maximizes CPU utilization.
    Storage Overcommit Ratio The storage overcommitment ratio of the dedicated cluster. For example, if the storage overcommitment ratio is 200%, the storage resources that can be allocated are twice as many as the storage resources that are provided. This maximizes storage utilization.
    Maximum Memory Usage The maximum memory utilization of each host in the dedicated cluster.
    Creation Time The time when the dedicated cluster was created.

Modify an ApsaraDB for MyBase dedicated cluster

  1. Log on to the ApsaraDB for MyBase console.
  2. In the upper-left corner of the page, select the region where you want to deploy the dedicated cluster.
    Select a region
  3. On the Dedicated Clusters page, find the dedicated cluster that you want to modify, and click Edit in the Actions column.
    Modify a dedicated cluster
  4. Configure the following parameters.
    Modify the parameters of a dedicated cluster
    Parameter Description
    Dedicated Cluster ID/Name The name of the dedicated cluster. You can customize the name for easy identification.
    CPU Overcommit Ratio The CPU overcommitment ratio of the dedicated cluster. The CPU overcommitment ratio ranges from 100% to 300%. The default ratio is 200%. If you keep the default setting, the CPU resources that can be allocated are twice as many as the CPU resources that are provided. This maximizes CPU utilization.
    Storage Overcommit Ratio The storage overcommitment ratio of the dedicated cluster. The storage overcommitment ratio ranges from 100% to 200%. The default ratio is 200%. If you keep the default setting, the storage resources that can be allocated are twice as many as the storage resources that are provided. This maximizes storage utilization.
    Maximum Memory Usage The maximum memory utilization of each host in the dedicated cluster. The maximum memory utilization ranges from 0% to 90%. The default value is 90%.
    Resource Allocation Policy The policy that is used by default to schedule resources in the dedicated cluster.
    • Balanced Allocation: New database instances are preferentially created on hosts that have the most available resources to maximize cluster stability.
    • Compact Allocation: New database instances are preferentially created on hosts where existing instances are created. This maximizes resource utilization.
    Host Troubleshooting Policy The policy that is used to handle host failures in the dedicated cluster.
    • Automatic Host Replacement: The system automatically replaces faulty hosts.
      Note
      • If a faulty host uses disks, the host is replaced only after the auto snapshot feature of the host storage is enabled.
      • If a faulty host uses local disks, the host is replaced only after all instances are removed from the host.
    • Manual Host Replacement: You must manually replace faulty hosts.
    Note After you create a dedicated cluster, you cannot change the VPC to which the dedicated cluster is connected. To connect to another VPC, you must delete the dedicated cluster and create another dedicated cluster. For information about how to create a dedicated cluster, see Create a cluster.
  5. Click OK.

Delete an ApsaraDB for MyBase dedicated cluster

  1. Log on to the ApsaraDB for MyBase console.
  2. In the upper-left corner of the page, select the region where you want to deploy the dedicated cluster.
    Select a region
  3. On the RDS Dedicated Clusters page, find the dedicated cluster that you want to delete, and click Delete in the Actions column.
    Delete a dedicated cluster
  4. In the message that appears, click OK.