If you have highly concurrent tasks that cannot run during off-peak hours, you need dedicated computing resources to ensure that your tasks are scheduled and run on time. In this case, you can use an exclusive resource group for scheduling in DataWorks. This topic describes the billing of exclusive resource groups for scheduling.
DataWorks no longer recommends exclusive resource groups for scheduling
DataWorks no longer recommends using exclusive resource groups for scheduling. Use serverless resource groups instead. Serverless resource groups provide the core features of earlier resource group types, such as exclusive resource groups for scheduling, exclusive resource groups for Data Integration, exclusive resource groups for DataService Studio, and public resource groups. A single serverless resource group lets you synchronize data, schedule and run tasks, and call and manage API services.
Scenarios
Your tasks are time-sensitive and you want to avoid delays caused by resource contention in public resource groups.
You need to flexibly adjust the size of your resource group.
You need to access the Internet, a Virtual Private Cloud (VPC), or an Internet Data Center (IDC).
You need to use an IP address whitelist for access control.
Some DataWorks task types, such as EMR, CDH, and ADB tasks, support only exclusive resource groups.
Limits
The billing method for exclusive resource groups for scheduling is subscription. You cannot delete or release a resource group before its subscription expires. After the subscription expires, the resource group service is suspended and the resource group is released after a specified period.
Exclusive resource groups for scheduling cannot be used across regions. For example, an exclusive resource group for scheduling in the China (Shanghai) region can be used only by workspaces in the China (Shanghai) region.
You cannot run yum commands in exclusive resource groups for scheduling.
Performance metrics
Specifications | Maximum number of concurrently running instances |
4 vCPU 8 GiB | 16 |
8 vCPU 16 GiB | 32 |
12 vCPU 24 GiB | 48 |
16 vCPU 32 GiB | 64 |
24 vCPU 48 GiB | 96 |
Billing standards
The billing method for exclusive resource groups for scheduling is subscription. You can purchase a resource group of a specific size as needed.
Region | Specifications | Price (USD/month) |
China (Hangzhou) | 4 vCPU 8 GiB | 76.23 |
8 vCPU 16 GiB | 152.45 | |
12 vCPU 24 GiB | 228.68 | |
16 vCPU 32 GiB | 304.91 | |
24 vCPU 48 GiB | 457.36 | |
32 vCPU 64 GiB | 609.82 | |
China (Shanghai) | 4 vCPU 8 GiB | 76.23 |
8 vCPU 16 GiB | 152.45 | |
12 vCPU 24 GiB | 228.68 | |
16 vCPU 32 GiB | 304.91 | |
24 vCPU 48 GiB | 457.36 | |
32 vCPU 64 GiB | 609.82 | |
China (Shenzhen) | 4 vCPU 8 GiB | 76.23 |
8 vCPU 16 GiB | 152.45 | |
12 vCPU 24 GiB | 228.68 | |
16 vCPU 32 GiB | 304.91 | |
24 vCPU 48 GiB | 457.36 | |
32 vCPU 64 GiB | 609.82 | |
China (Beijing) | 4 vCPU 8 GiB | 76.23 |
8 vCPU 16 GiB | 152.45 | |
12 vCPU 24 GiB | 228.68 | |
16 vCPU 32 GiB | 304.91 | |
24 vCPU 48 GiB | 457.36 | |
32 vCPU 64 GiB | 609.82 | |
China (Zhangjiakou) | 4 vCPU 8 GiB | 57.27 |
8 vCPU 16 GiB | 114.34 | |
12 vCPU 24 GiB | 171.61 | |
16 vCPU 32 GiB | 228.68 | |
24 vCPU 48 GiB | 343.02 | |
32 vCPU 64 GiB | 457.36 | |
China (Chengdu) | 4 vCPU 8 GiB | 62.49 |
8 vCPU 16 GiB | 124.79 | |
12 vCPU 24 GiB | 187.09 | |
16 vCPU 32 GiB | 249.38 | |
24 vCPU 48 GiB | 374.17 | |
32 vCPU 64 GiB | 498.77 | |
US (Silicon Valley) | 4 vCPU 8 GiB | 149.26 |
8 vCPU 16 GiB | 298.53 | |
12 vCPU 24 GiB | 447.77 | |
16 vCPU 32 GiB | 597.06 | |
24 vCPU 48 GiB | 895.55 | |
32 vCPU 64 GiB | 1,195.00 | |
US (Virginia) | 4 vCPU 8 GiB | 110.63 |
8 vCPU 16 GiB | 221.26 | |
12 vCPU 24 GiB | 331.89 | |
16 vCPU 32 GiB | 442.53 | |
24 vCPU 48 GiB | 663.78 | |
32 vCPU 64 GiB | 885.06 | |
China (Hong Kong) | 4 vCPU 8 GiB | 138.73 |
8 vCPU 16 GiB | 276.58 | |
12 vCPU 24 GiB | 416.18 | |
16 vCPU 32 GiB | 553.16 | |
24 vCPU 48 GiB | 832.35 | |
32 vCPU 64 GiB | 1,106.32 | |
Singapore | 4 vCPU 8 GiB | 138.73 |
8 vCPU 16 GiB | 276.58 | |
12 vCPU 24 GiB | 416.18 | |
16 vCPU 32 GiB | 553.16 | |
24 vCPU 48 GiB | 832.35 | |
32 vCPU 64 GiB | 1,106.32 | |
Germany (Frankfurt) | 4 vCPU 8 GiB | 138.73 |
8 vCPU 16 GiB | 276.58 | |
12 vCPU 24 GiB | 408.96 | |
16 vCPU 32 GiB | 553.16 | |
24 vCPU 48 GiB | 817.91 | |
32 vCPU 64 GiB | 1,106.32 | |
Malaysia (Kuala Lumpur) | 4 vCPU 8 GiB | 130.01 |
8 vCPU 16 GiB | 259.06 | |
12 vCPU 24 GiB | 390.05 | |
16 vCPU 32 GiB | 517.92 | |
24 vCPU 48 GiB | 780.07 | |
32 vCPU 64 GiB | 1,035.84 | |
Indonesia (Jakarta) | 4 vCPU 8 GiB | 138.73 |
8 vCPU 16 GiB | 276.58 | |
12 vCPU 24 GiB | 416.18 | |
16 vCPU 32 GiB | 553.16 | |
24 vCPU 48 GiB | 832.35 | |
32 vCPU 64 GiB | 1,106.32 | |
Japan (Tokyo) | 4 vCPU 8 GiB | 158.92 |
8 vCPU 16 GiB | 316.97 | |
12 vCPU 24 GiB | 474.14 | |
16 vCPU 32 GiB | 633.94 | |
24 vCPU 48 GiB | 948.27 | |
32 vCPU 64 GiB | 1,268.75 | |
UK (London) | 4 vCPU 8 GiB | 104.67 |
8 vCPU 16 GiB | 209.33 | |
12 vCPU 24 GiB | 314.00 | |
16 vCPU 32 GiB | 418.67 | |
24 vCPU 48 GiB | 628.00 | |
32 vCPU 64 GiB | 837.14 | |
UAE (Dubai) | 4 vCPU 8 GiB | 166.38 |
8 vCPU 16 GiB | 331.80 | |
12 vCPU 24 GiB | 498.38 | |
16 vCPU 32 GiB | 663.80 | |
24 vCPU 48 GiB | 996.76 | |
32 vCPU 64 GiB | 1,327.59 | |
SAU (Riyadh - Partner Region) | 4 vCPU 8 GiB | 166.48 |
8 vCPU 16 GiB | 331.90 | |
12 vCPU 24 GiB | 499.42 | |
16 vCPU 32 GiB | 663.79 | |
24 vCPU 48 GiB | 998.82 | |
32 vCPU 64 GiB | 1,327.58 |
Billing
Scale-out and scale-in
You can purchase an exclusive resource group and specify the instance type and number of instances for the resource group. After the purchase, you can scale the resource group out or in. For more information about the procedure and notes on scaling, see Scale out or scale in a resource group.
Change specifications (upgrade or downgrade)
If the current specifications of your exclusive resource group do not meet your business requirements, you can change the specifications. When you change the specifications of a resource group, the specifications of all instances in that resource group are also changed. For more information about the procedure and notes on changing specifications, see Change specifications.
Renew, suspend, and release a resource group
You can renew an exclusive resource group before it expires. You can also allow the resource group to expire. After a resource group expires, its service is suspended and the resource group is automatically released. For more information, see Expiration and renewal.
After a resource group is released, all tasks that depend on the resource group cannot run as expected.
Network connectivity solutions
An exclusive resource group for scheduling is similar to other types of resource groups. It is a group of Alibaba Cloud Elastic Compute Service (ECS) instances. When you run tasks, such as data development tasks, you must ensure that the resource group and the data source are connected. You must also ensure that the network connection is not blocked by special security settings, such as whitelists.
If the exclusive resource group for scheduling does not interact with a data source, you do not need to configure network connectivity. You can use the resource group immediately after you purchase it without any additional network configuration.
After you purchase an exclusive resource group for scheduling, you must attach it to a VPC. Then, you can select a network connectivity solution based on the network environment of your data source.
Network connectivity solutions
Network environment
Network connectivity solution
The data source is deployed on the Internet.
The exclusive resource group for Data Integration that is deployed in a VPC can directly access the data source.
The data source is deployed in a VPC and resides in the same region as the exclusive resource group for Data Integration.
We recommend that you associate the exclusive resource group for Data Integration with the VPC in which the data source is deployed and with a vSwitch that belongs to the VPC. Then, the system adds a route for the exclusive resource group for Data Integration. This way, the exclusive resource group for Data Integration can access the data source.
The data source is deployed in a VPC and resides in a different region from the exclusive resource group for Data Integration.
Use Express Connect circuits or VPN gateways to connect the data source to the VPC with which the exclusive resource group for Data Integration is associated, and add a route that points to the IP address of the database you want to access to ensure the network connection between the data source and resource group.
The data source is deployed in a data center.
Use Express Connect circuits or VPN gateways to connect the data source to the VPC with which the exclusive resource group for Data Integration is associated, and add a route that points to the IP address of the database you want to access to ensure the network connection between the data source and resource group.
The data source is deployed in the classic network.
Exclusive resource groups are deployed in VPCs of Alibaba Cloud. If your data source is deployed in the classic network of Alibaba Cloud, your exclusive resource group cannot access the data source. In this case, we recommend that you migrate the data source to the VPC in which your exclusive resource group is deployed.
Whitelist settings
If an IP address whitelist is configured for the data source that you want to access, you must add the EIP of your exclusive resource group for Data Integration or the CIDR block of the vSwitch with which the resource group is associated to the whitelist. For more information, see Configure an IP address whitelist.
FAQ
For frequently asked questions about DataWorks exclusive resource groups, see Exclusive resource groups.