Engine |
The database engine of the dedicated cluster. MySQL and SQL Server are available.
Other database engines will be supported in later versions.
|
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 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 where existing instances
are created. This maximizes resource utilization.
|
Deployment Method |
- High-availability: You can deploy only instances of the High-availability Edition, which are HA instances
for short.
- Enterprise/Basic: You can deploy only the instances of the Enterprise Edition (three nodes) or the
Basic Edition (one node).
Note
- If you select High-availability, both local disks and disks are supported.
- If you select Enterprise/Basic, only disks are supported.
|
VPC |
The VPC to which the dedicated cluster is connected. To create a VPC, log on to the
VPC console.
Note After you create a dedicated cluster, you cannot change the VPC to which the dedicated
cluster is connected. To connect to another VPC, delete the dedicated cluster and
create another 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.
|
Grant OS Permissions |
If you enable this feature for a dedicated cluster that runs the MySQL database engine,
you can log on to the hosts in the dedicated cluster to perform operations such as
uploading, downloading, and installing software. This feature is unavailable for dedicated
clusters that run other database engines.
|