Release Notes
Announcements
Security Announcements
Configuration Item | Description |
Product Edition | Clusters with decommissioned product editions cannot be cloned. |
Billing Mode | If the node billing mode of the existing cluster are inconsistent, the cluster will be cloned as a pay-as-you-go cluster by default. After the cluster is created, you can change its billing mode from pay-as-you-go to monthly subscription as needed. |
Node Configurations | 1. Only supports cloning Master, Core, Task, and Common node specifications. 2. If there are multiple resource specifications for the same node type in the same availability zone, the latest node's specifications will be used by default when cloning. |
Number of Nodes | The number of cloned nodes defaults to the minimum number of nodes, but you can adjust the quantity as needed. |
Component Configuration | 1. Hadoop cluster type supports cloning component configurations, while other cluster types do not support cloning component configurations. 2. It only supports cloning cluster-level custom component configurations, including component configurations created during cluster creation and modified in the console. 3. The custom configuration range that supports cloning: address, path, and username configurations. Newly added custom configuration files are not supported for cloning. If you need to modify the password-related configurations, you can manually import them through the software configurations on the purchase page. For more details, see Software Configurations. |
Security Group | If an existing cluster has multiple security groups or the security groups have been modified, the first active security group of the existing cluster will be used by default when cloning. |
Resource Tag | Only cluster-level tags are supported for cloning. Node-level tags cannot be cloned. |
Metadata Configurations | Existing clusters with MetaDB version 5.6 will be upgraded to 5.7 by default when cloning. |
피드백