If many tasks must run concurrently and cannot be scheduled at different times, dedicated compute resources can help ensure that tasks run at their scheduled times. In this case, we recommend an exclusive resource group for scheduling. This topic provides an overview of these resource groups.
DataWorks does not recommend exclusive resource groups for scheduling
DataWorks no longer recommends using exclusive resource groups for scheduling. We recommend Use serverless resource groups.Serverless resource groups provide the core capabilities of legacy resource groups, including exclusive resource groups for scheduling, exclusive resource groups for Data Integration, exclusive resource groups for DataService Studio, and public resource groups. One Serverless resource group can handle data synchronization, scheduled task runs, API service calls, and API management.
Use cases
Tasks have strict timeliness requirements, and you need to avoid delays caused by resource contention on public resource groups.
You need to adjust resource group capacity flexibly.
You need to access public network addresses, VPCs, or an Internet data center (IDC).
You need to control access through an IP allowlist.
Some DataWorks task types, including EMR, CDH, and ADB, support only exclusive resource groups.
Limits
Exclusive resource groups for scheduling are billed on a subscription basis. You cannot delete or release them before the subscription expires. After expiration, services stop and the resource groups are released at the specified times.
An exclusive resource group for scheduling cannot be used across regions. For example, one in China (Shanghai) can be used only by workspaces in China (Shanghai).
Exclusive resource groups for scheduling do not support yum commands.
Performance metrics
Specification | 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 |
Pricing
When a task runs on an exclusive resource group for scheduling, its execution cost is included in the cost of that resource group and is not charged to a public scheduling resource group.
An exclusive resource group for scheduling is billed on a subscription basis basis. Choose a specification that meets your needs.
Region | Specification | Unit 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 | |
Saudi Arabia (Riyadh) | 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
Purchase an exclusive resource group and choose the machine specification and number of machines based on your business needs. After purchase, you can scale the resource group out or in. For procedures and precautions, see Scaling.
Change the specification (upgrade or downgrade)
If the current specification does not meet your needs, change the resource group specification. This changes the specification of all machines in the group. For procedures and precautions, see Change specifications.
Renew, stop, or release a resource group
Renew an exclusive resource group before it expires, or let services stop and resources be released automatically after expiration. For details, see Expiration and renewal.
After the resource group is released, tasks that depend on it cannot run normally.
Network connectivity
Like other resource groups, an exclusive resource group for scheduling is essentially a set of Alibaba Cloud ECS instances. Before running data development tasks, make sure that the resource group can connect to the data source and that IP allowlists or other security settings do not block the connection.
If use of the exclusive resource group for scheduling does not involve interaction with a data source, connectivity to a data source is irrelevant. You can use the resource group directly after purchase.
After purchasing an exclusive resource group for scheduling, bind it to a VPC. Then choose a connectivity solution based on the data source network.
-
Network connectivity solutions
Data source network environment
Network connectivity solution
The data source is on the public network
The data source can be directly connected to the VPC associated with the exclusive resource group.
The data source is in a VPC and in the same region as the exclusive resource group
We recommend that you associate the exclusive resource group with the same VPC as the data source. After the association, the system automatically adds a route to the entire VPC. You can associate any vSwitch in the VPC to enable network connectivity between the exclusive resource group and the data source.
The data source is in a VPC and in a different region from the exclusive resource group
Use Express Connect or VPN Gateway to connect the data source network to the VPC associated with the exclusive resource group, and add a route to the IP address of the destination database to ensure network reachability between the two networks.
The data source is in an on-premises data center
Use Express Connect or VPN Gateway to connect the data source network to the VPC associated with the exclusive resource group, and add a route to the IP address of the destination database to ensure network reachability between the two networks.
The data source is in a classic network
Exclusive resource groups reside in Alibaba Cloud VPCs. If the data source is in a classic network, the network between the data source and the exclusive resource group cannot be connected. We recommend that you migrate the data source to a VPC.
-
Allowlist configuration
If the data source has an allowlist that restricts access, you must add the IP addresses of the exclusive resource group to the allowlist of the data source to prevent access restrictions. For more information, see Add the resource group to the data source allowlist.
FAQs
For FAQs about DataWorks exclusive resource groups, see Exclusive resource groups.