Create a dedicated cluster

Usage notes

• In the Thailand (Bangkok) region, only the SQL Server engine is supported.
• The default overcommit metrics for a dedicated cluster are as follows:
  • The default CPU Overcommit Ratio is 200% for MySQL and SQL Server engines, and 300% for the Redis CPU Overcommit Ratio.
  • The default Storage Overcommit Ratio is 100% for MySQL, SQL Server, and Redis engines.
  • The default Maximum Memory Usage is 100% for MySQL, SQL Server, and Redis engines.

  After you create a dedicated cluster, you can modify the overcommit metrics based on your business requirements. For more information, see Configure resource overcommitment to reduce costs.

Create a dedicated cluster

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

   Parameter	Description
   Engine	Supported engines: MySQL, SQL Server, and Redis. Important When you create a cluster, you must select an engine. The engine you choose determines the system images available for adding hosts and the database types for creating instances. The engine cannot be changed after the cluster is created.
   Architecture	This parameter is available only when you set Engine to MySQL. The default is high availability.
   Dedicated Cluster Name	The name of the dedicated cluster.
   VPC	The Virtual Private Cloud (VPC) for the dedicated cluster. To create a new VPC, go to the VPC console. Important The VPC cannot be changed after the dedicated cluster is created.
   Resource Allocation Policy	The default resource allocation policy for the dedicated cluster. Valid values: Balanced Allocation: Maximizes system stability by allocating resources first from hosts with no allocated resources or few allocated resources. Compact Allocation: Maximizes resource utilization by allocating resources first from hosts that were created earlier and have more allocated resources.
   Host Troubleshooting Policy	The policy for handling host failures. Valid values: Automatic Host Replacement: The system automatically replaces a faulty host. Note If the faulty host is a host that uses cloud disks, the system automatically migrates compute resources to replace the host. If the faulty host is a host that uses local disks, the system first migrates the instances from the host and then replaces the host. Manual Host Replacement: You must manually replace a faulty host. Note This parameter is available only for the MySQL engine. For other engines, the default policy is automatic host replacement.
   Grant OS Permissions	Specifies whether to grant OS permissions for the hosts. Note ApsaraDB for MyBase provides OS permissions for hosts in dedicated clusters that run MySQL or SQL Server. You can log on to the hosts to perform operations such as uploading, downloading, and installing software. The Grant OS Permissions setting cannot be changed after the cluster is created. Select this option with caution.

5. (Optional) The first time you create an ApsaraDB for MyBase dedicated cluster, a message at the bottom of the page prompts you to authorize access to ECS elastic network interfaces (ENIs) and security groups. Click Authorize Now, and then click Agree to Authorize on the Cloud Resource Access Authorization page.
   Note After the authorization is complete, you can find the AliyunRDSDedicatedHostGroupRole role on the RAM Role Management page of the Resource Access Management (RAM) console. Do not delete this role when you use ApsaraDB for MyBase. If you delete the role, you must grant the permissions again to create a dedicated cluster.
6. Click OK.

Learn more

Join the DingTalk group (ID: 32484333) to get answers from database experts, learn from success stories, and attend regular expert live streams.