Create a dedicated cluster

Precautions

• Each dedicated cluster in ApsaraDB MyBase can be deployed only in one region.
• A dedicated cluster in ApsaraDB MyBase can be deployed only in one virtual private cloud (VPC).
• Dedicated clusters that run the SQL Server database engine cannot be created in the following regions: China (Zhangjiakou), China (Hohhot), Australia (Sydney), Malaysia (Kuala Lumpur), US (Virginia), and India (Mumbai).
• Overcommit metrics cannot be configured when you perform the Create Dedicated Cluster operation. You can modify the overcommit metrics after you create a dedicated cluster. For more information, see Configure resource overcommitment to reduce costs. By default, the following overcommit metrics are configured:
  • CPU Overcommit Ratio for MySQL, SQL Server, and PostgreSQL: 200%
  • Storage Overcommit Ratio for MySQL, SQL Server, and PostgreSQL: 100%
  • Maximum Memory Usage for MySQL, SQL Server, and PostgreSQL: 100%

Create a dedicated cluster in ApsaraDB MyBase

1. Log on to the ApsaraDB MyBase console.
2. In the upper-left corner of the page, select a region.
3. On the Clusters page, click Create Dedicated Cluster.
   
4. In the Create Dedicated Cluster panel, configure the following parameters.

   Parameter	Description
   Engine	The database engine of the dedicated cluster. The MySQL, SQL Server, and PostgreSQL database engines are supported. Notice After you create a dedicated cluster, you cannot change the database engine. Proceed with caution.
   Architecture	The edition of the dedicated cluster. This parameter appears only when you select the MySQL database engine. It is automatically set to High-availability/Master-replica Edition.
   Dedicated Cluster Name	The name of the dedicated cluster.
   VPC	The VPC in which the dedicated cluster is deployed. If you need to create a VPC, log on to the VPC console. Notice After a dedicated cluster is created, you cannot change the VPC. Proceed with caution.
   Resource Allocation Policy	The default policy that is used to schedule resources in the dedicated cluster. Balanced Allocation: The system preferentially creates database instances on the hosts that have the smallest load. This maximizes system stability. Compact Allocation: The system preferentially creates database instances on the hosts that are created earlier than the other hosts and have fewer resources than the other hosts in the dedicated cluster. This maximizes resource utilization.
   Host Troubleshooting Policy	The policy based on which the system handles host failures. Automatic Host Replacement: The system automatically replaces the faulty hosts. Note If a faulty host uses standard SSDs or enhanced SSDs (ESSDs), the host is automatically replaced after the computing resources that are stored on the standard SSDs or ESSDs are migrated to another host. 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. Note You can manually replace a faulty host only if the faulty host uses local SSDs. Only hosts that run the MySQL database engine support local SSDs. If you select the MySQL database engine, you can configure this parameter. If you select another database engine, this parameter is set to Automatic Host Replacement by default.
   Grant OS Permissions	Specifies whether to enable the feature that allows you to have permissions on the host operating system (OS). Note If you enable this feature for a dedicated cluster that runs the MySQL, SQL Server, or PostgreSQL database engine, you can log on to the hosts in the dedicated cluster to perform operations such as uploads, downloads, and installation of software. After you create a dedicated cluster, you cannot change Grant OS Permissions. Proceed with caution.

5. The first time you create a dedicated cluster in ApsaraDB MyBase, you must perform this step.

   The first time you create an ApsaraDB MyBase dedicated cluster, the following message appears in the lower part of the panel. You must grant permissions on elastic network interfaces (ENIs) and security groups of Elastic Compute Service (ECS). Click Authorize Now. On the Cloud Resource Access Authorization page, click Confirm Authorization Policy.

   

   Note After you grant permissions, the AliyunRDSDedicatedHostGroupRole role is displayed on the Roles page in the RAM console. If you want to use ApsaraDB MyBase dedicated clusters, retain this role. If this role is deleted, you must grant the permissions again to create a dedicated cluster.
6. Click OK.

Tutorial video

Learn more

You can join the DingTalk group 32484333 to obtain technical support from database experts, view success stories, and engage with experts on live streams that are provided on a regular basis.