DataWorks no longer recommends exclusive resource groups for scheduling. Use Serverless resource groups instead. Serverless resource groups consolidate the capabilities of exclusive resource groups for scheduling, exclusive resource groups for Data Integration, exclusive resource groups for DataService Studio, and shared resource groups for scheduling into a single resource group type. You can use a single Serverless resource group to synchronize data, schedule and run tasks, and call and manage API services.
Exclusive resource groups for scheduling provide dedicated Elastic Compute Service (ECS) instances for running DataWorks tasks. Unlike shared resource groups, these groups give your tasks isolated computing capacity — preventing resource contention from affecting task timeliness.
Use cases
Exclusive resource groups for scheduling are suited for the following scenarios:
Time-sensitive tasks: Your tasks have strict scheduling deadlines and cannot tolerate delays caused by resource contention in shared resource groups.
Flexible capacity: You need to scale the resource group up or down based on workload changes.
Network access: Your tasks need to reach the Internet, Virtual Private Clouds (VPCs), or Internet Data Centers (IDCs).
Access control: You need IP address whitelists to restrict which resources can connect to your data sources.
Task type requirements: Some DataWorks task types — including E-MapReduce (EMR), CDH, and ADB tasks — support only exclusive resource groups.
Limitations
Purchase and release constraints (affect your buying decision):
The billing method is subscription. You cannot delete or release a resource group before it expires. After expiry, the 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, a resource group in the China (Shanghai) region can only be used by workspaces in China (Shanghai).
Operational constraint (affects day-to-day use):
You cannot run the
yumcommand inside an exclusive resource group for scheduling.
Specifications and concurrency
| Specifications | Maximum concurrent 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 |
Cost estimation
You can use the DataWorks exclusive resource group calculator to estimate the required specifications and costs. To help you with your estimation, you can view the number of running instances and concurrency information on the page in the DataWorks Operation Center. For more information about how to view the O&M Dashboard, see View the O&M Dashboard.
Billing
Task runtime costs on an exclusive resource group are included in the resource group subscription fee and are not charged separately to shared resource groups.
The billing method is subscription. Pricing varies by region and specification:
Region | Specifications | Unit price (CNY/month) |
China (Hangzhou) | 4 vCPU 8 GiB | 492.50 |
8 vCPU 16 GiB | 985.00 | |
12 vCPU 24 GiB | 1477.50 | |
16 vCPU 32 GiB | 1970.00 | |
24 vCPU 48 GiB | 2955.00 | |
China (Shanghai) | 4 vCPU 8 GiB | 492.50 |
8 vCPU 16 GiB | 985.00 | |
12 vCPU 24 GiB | 1477.50 | |
16 vCPU 32 GiB | 1970.00 | |
24 vCPU 48 GiB | 2955.00 | |
China (Shenzhen) | 4 vCPU 8 GiB | 492.50 |
8 vCPU 16 GiB | 985.00 | |
12 vCPU 24 GiB | 1477.50 | |
16 vCPU 32 GiB | 1970.00 | |
24 vCPU 48 GiB | 2955.00 | |
China (Beijing) | 4 vCPU 8 GiB | 492.50 |
8 vCPU 16 GiB | 985.00 | |
12 vCPU 24 GiB | 1477.50 | |
16 vCPU 32 GiB | 1970.00 | |
24 vCPU 48 GiB | 2955.00 | |
China (Zhangjiakou) | 4 vCPU 8 GiB | 370.00 |
8 vCPU 16 GiB | 738.75 | |
12 vCPU 24 GiB | 1108.75 | |
16 vCPU 32 GiB | 1477.50 | |
24 vCPU 48 GiB | 2216.25 | |
China (Ulanqab) | 4 vCPU 8 GiB | 443.25 |
8 vCPU 16 GiB | 886.50 | |
12 vCPU 24 GiB | 1,329.75 | |
16 vCPU 32 GiB | 1,773.00 | |
24 vCPU 48 GiB | 2,659.50 | |
China (Chengdu) | 4 vCPU 8 GiB | 403.75 |
8 vCPU 16 GiB | 806.25 | |
12 vCPU 24 GiB | 1208.75 | |
16 vCPU 32 GiB | 1611.25 | |
24 vCPU 48 GiB | 2417.50 | |
US (Silicon Valley) | 4 vCPU 8 GiB | 964.38 |
8 vCPU 16 GiB | 1928.78 | |
12 vCPU 24 GiB | 2893.05 | |
16 vCPU 32 GiB | 3857.58 | |
24 vCPU 48 GiB | 5786.10 | |
US (Virginia) | 4 vCPU 8 GiB | 714.79 |
8 vCPU 16 GiB | 1429.58 | |
12 vCPU 24 GiB | 2144.33 | |
16 vCPU 32 GiB | 2859.15 | |
24 vCPU 48 GiB | 4288.65 | |
China (Hong Kong) | 4 vCPU 8 GiB | 896.31 |
8 vCPU 16 GiB | 1786.96 | |
12 vCPU 24 GiB | 2688.90 | |
16 vCPU 32 GiB | 3573.94 | |
24 vCPU 48 GiB | 5377.80 | |
Singapore | 4 vCPU 8 GiB | 896.31 |
8 vCPU 16 GiB | 1786.96 | |
12 vCPU 24 GiB | 2688.90 | |
16 vCPU 32 GiB | 3573.94 | |
24 vCPU 48 GiB | 5377.80 | |
Germany (Frankfurt) | 4 vCPU 8 GiB | 896.31 |
8 vCPU 16 GiB | 1786.96 | |
12 vCPU 24 GiB | 2642.25 | |
16 vCPU 32 GiB | 3573.94 | |
24 vCPU 48 GiB | 5284.50 | |
Malaysia (Kuala Lumpur) | 4 vCPU 8 GiB | 840.00 |
8 vCPU 16 GiB | 1673.75 | |
12 vCPU 24 GiB | 2520.00 | |
16 vCPU 32 GiB | 3346.25 | |
24 vCPU 48 GiB | 5040.00 | |
Indonesia (Jakarta) | 4 vCPU 8 GiB | 896.31 |
8 vCPU 16 GiB | 1786.96 | |
12 vCPU 24 GiB | 2688.90 | |
16 vCPU 32 GiB | 3573.94 | |
24 vCPU 48 GiB | 5377.80 | |
Japan (Tokyo) | 4 vCPU 8 GiB | 1026.79 |
8 vCPU 16 GiB | 2047.91 | |
12 vCPU 24 GiB | 3063.38 | |
16 vCPU 32 GiB | 4095.84 | |
24 vCPU 48 GiB | 6126.75 | |
UK (London) | 4 vCPU 8 GiB | 676.25 |
8 vCPU 16 GiB | 1352.50 | |
12 vCPU 24 GiB | 2028.75 | |
16 vCPU 32 GiB | 2705.00 | |
24 vCPU 48 GiB | 4057.50 | |
UAE (Dubai) | 4 vCPU 8 GiB | 1075.00 |
8 vCPU 16 GiB | 2143.75 | |
12 vCPU 24 GiB | 3220.00 | |
16 vCPU 32 GiB | 4288.75 | |
24 vCPU 48 GiB | 6440.00 | |
Alibaba Gov Cloud | 4 vCPU 8 GiB | 1020.00 |
8 vCPU 16 GiB | 2005.00 | |
12 vCPU 24 GiB | 2990.00 | |
16 vCPU 32 GiB | 3975.00 | |
24 vCPU 48 GiB | 5945.00 | |
China (Shanghai) Finance Cloud and China (Shenzhen) Finance Cloud | 4 vCPU 8 GiB | 935.75 |
8 vCPU 16 GiB | 1871.50 | |
12 vCPU 24 GiB | 2807.25 | |
16 vCPU 32 GiB | 3743.00 | |
24 vCPU 48 GiB | 5614.50 |
Prices are in USD per month.
Scale-out and scale-in
When you purchase a resource group, specify the machine specifications and the number of nodes. After purchase, you can scale out (add nodes) or scale in (remove nodes) at any time. For the procedure and considerations, see Scale out or scale in a resource group.
Change specifications
If the current node specifications no longer fit your workload, you can upgrade or downgrade. Changing specifications applies to all nodes in the resource group simultaneously. For the procedure and considerations, see Change specifications.
Renewal and release
Renew the resource group before it expires, or let it expire and be released automatically. For renewal options, see Expiration and renewal.
After a resource group is released, all tasks that rely on it stop running.
Network connectivity
If your tasks do not interact with any data source, no network configuration is needed — the resource group is ready to use immediately after purchase.
After you purchase an exclusive resource group for scheduling, you must attach it to a VPC. Then, configure connectivity based on where the data source resides.
| Data source location | Connectivity solution |
|---|---|
| Internet | Connect the data source directly to the VPC attached to the resource group. |
| VPC in the same region | Attach the resource group to the same VPC as the data source. The system automatically adds the required route. |
| VPC in a different region | Connect the two VPCs using Express Connect or VPN, then add a route pointing to the destination database IP address. |
| On-premises data center | Connect the data center to the resource group VPC using Express Connect or VPN, then add a route pointing to the destination database IP address. |
| Classic network | Exclusive resource groups reside in a VPC and cannot connect to classic network resources. Migrate the data source to a VPC first. |
Whitelist configuration
If the data source restricts access by IP address whitelist, add the endpoint of the exclusive resource group to the data source's whitelist. For instructions, see Add a whitelist.
FAQ
For answers to common questions, see Exclusive resource groups FAQ.