Resizing a Standard Dedicated Resource Pool

Billing

When you increase the number of instances, compute resources will be billed. For details, see ModelArts Pricing Details.

You can specify the billing mode of new nodes in a resource pool during scaling. For example, you can create pay-per-use nodes in a yearly/monthly resource pool. If you do not specify this parameter, the billing mode of the created nodes is the same as that of the resource pool. For details, see Table 1.

Prerequisites

You have created a standard dedicated resource pool.

Constraints

• Only dedicated resource pools in the Running status can be resized. A resource pool is suspended when it is being migrated from the old version to the new version. You cannot adjust the capacity of such a resource pool or unsubscribe from it.
• If there is only one instance node in the resource pool, scaling in cannot be performed. Therefore, keep at least one node.
• The scale-in operation may affect running tasks and cannot be rolled back. If the node has a local disk, the data on the local disk will be cleared and cannot be restored. Exercise caution when performing this operation. If the development environment is enabled for the resource pool, the created notebook that uses EVS storage may be unavailable after scale-in.

Changing the Number of Instances

1. Log in to the ModelArts console. In the navigation pane on the left, choose Standard Cluster under Resource Management.
2. For a yearly/monthly resource pool, only Scale Out is displayed. To scale in the resource pool, go to the details page and unsubscribe from the resources. For a yearly/monthly resource pool, only Scale Out is displayed. To scale in the resource pool, go to the details page and unsubscribe from the resources.

3. On the Scale In/Out Dedicated Resource Pool page, configure resources by referring to Table 2.

   Table 2 Parameters for resource configurations

   Parameter	Description
   Instance Specifications Type	Instance specifications type of the target Standard resource pool, which cannot be modified.
   Specifications	Specifications of the target Standard resource pool, which cannot be modified.
   Instances in Total	Number of instances in the target Standard resource pool, which cannot be modified.
   AZ Allocation	AZ allocation of nodes after scaling. You can select Automatic or Manual. If you select Automatic, nodes are randomly allocated to AZs after the scaling. If you select Manual, you can allocate nodes to specified AZs. By default, the value of Target Instances indicates how many instances there will be in the AZ. For example: If there are three instances, and Target Instances is set to 5, the instances in the AZ will be scaled up to 5. If there are three instances, and Target Instances is set to 2, the instances in the AZ will be scaled in to 2.
   Container Engine Space Limit	When you scale out a resource pool, and the value of Target Instances is greater than that of Instances in Total, you can set the container engine space size of the new node to a specified value or unlimited. This operation will cause inconsistencies in dockerBaseSize of nodes within the resource pool. As a result, some tasks may run differently on different nodes. The container engine space size cannot be changed for existing nodes.
   Container Engine Space Size	You can set a specified size by setting Container Engine Space Limit to Manual.
   Target Instances	You can set this parameter for scaling based on service requirements. Scale out: The value of Target Instances is greater than that of Instances in Total. Scale in: The value of Target Instances is smaller than that of Instances in Total. If AZ Allocation is set to Manual, you do not need to set this parameter. Target Instances indicates how many instances can there be in the target AZ. When you purchase a resource pool, the instances for certain specifications can be purchased by rack. When you resize the resource pool, the instances are also added or deleted by rack. You can choose to purchase nodes by rack when creating a resource pool, which cannot be modified when resizing a resource pool. You can configure the rack quantity to change the number of target instances.
   OS	Select an OS version from the OS drop-down list.

   Figure 1 Configuring resources on a single node
   

4. Configure the node billing mode. When adding instances, you can enable Node Billing Mode to set the billing mode and required duration for the new nodes, and enable the auto-renewal function. For example, you can create pay-per-use nodes in a yearly/monthly resource pool. If the billing mode is not specified, it will be the mode for charging resource pools.
5. Click Submit and then OK.

   On the Standard Cluster page, check whether the number of nodes in the resource pool is the value of Target Instances.

Related Operations

• Viewing Resource Pool Nodes: If there are abnormal or idle nodes that need to be removed from a resource pool, access the resource pool details page, and delete the target nodes (in batches).
• Upgrading the Standard Dedicated Resource Pool Driver: If there are GPU/Ascend resources in the dedicated resource pool, you can upgrade the GPU/Ascend driver based on service requirements.
• Rectifying a Faulty Node in a Standard Dedicated Resource Pool: Rectify the faulty nodes in a standard dedicated resource pool. Currently, you can reset and restart a node, as well as configuring an HA redundant node.
• Modifying the Job Types Supported by a Standard Dedicated Resource Pool: You can change job types supported by a dedicated resource pool after it is created to avoid resource waste.