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 top navigation bar, select the region where you want to create a 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 machine.
    • By default, the Dedicated Cluster ID, VPC, and Hosts columns are displayed in the list. You can click Custom Columns icon in the upper-right corner to select the columns that you want to view. Specify the columns that you want to view for each dedicated cluster
    • You can click the Export Resources icon icon in the upper-right corner to download the information about the dedicated clusters to an on-premises machine.
  4. Find the MyBase for PostgreSQL dedicated cluster that you want to view, and click Details in the Actions column.
  5. On the Basic Information tab, view the parameter settings of the 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 the faulty hosts.
      Note
      • If a faulty host uses enhanced SSDs (ESSDs), the host is replaced after the computing resources on the host are migrated.
      • If a faulty host uses local SSDs, the host is replaced only after all instances are removed from the host.
    • Manual Host Replacement: You must manually replace the faulty hosts.
    Resource Allocation Policy The default policy that is used 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 that have been created earlier and have more resources allocated. This maximizes resource usage.
    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 use the default setting, the CPU resources that can be allocated are twice as many as the CPU resources that are provided.
    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 use the default setting, the storage that can be allocated is twice as much as the storage that is provided. This maximizes storage usage.
    Maximum Memory Usage The maximum memory usage of each host in the dedicated cluster. Valid values: 0% to 100%. Default value: 100%.
    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 top navigation bar, select the region where you want to create a dedicated cluster.
    Select a region
  3. On the Dedicated Clusters page, find the MyBase for PostgreSQL dedicated cluster that you want to modify, and click Edit in the Actions column.
  4. In the panel that appears, configure the following parameters.
    Parameter Description
    Dedicated Cluster 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 use the default setting, the CPU resources that can be allocated are twice as many as the CPU resources that are provided.
    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% and cannot be changed. If you use the default setting, the storage that can be allocated is twice as much as the storage that is provided. This maximizes storage usage.
    Maximum Memory Usage The maximum memory usage of each host in the dedicated cluster. Valid values: 0% to 100%. Default value: 100%.
    Resource Allocation Policy The default policy that is used 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 that have been created earlier and have more resources allocated. This maximizes resource usage.
    Host Troubleshooting Policy
    • Automatic Host Replacement: The system automatically replaces the faulty hosts.
      Note
      • If a faulty host uses enhanced SSDs (ESSDs), the host is replaced after the computing resources on the host are migrated.
      • If a faulty host uses local SSDs, the host is replaced only after all instances are removed from the host.
    • Manual Host Replacement: You must manually replace the faulty hosts.
    Grant OS Permissions After you create a dedicated cluster, you cannot change the setting of Grant OS Permissions.
    Note When you create a dedicated cluster, make sure that you select the desired option for Grant OS Permissions.
  5. Click OK.

Delete an ApsaraDB for MyBase dedicated cluster

  1. Log on to the ApsaraDB for MyBase console.
  2. In the top navigation bar, select the region where you want to create a dedicated cluster.
    Select a region
  3. On the Dedicated Clusters page, find the MyBase for PostgreSQL dedicated cluster that you want to delete, and click Delete in the Actions column.
    Note You can delete a dedicated cluster only after all the hosts and instances in the dedicated cluster are deleted.
  4. In the message that appears, click OK.