After you purchase and configure an exclusive resource group, you can use the resource group to run tasks in a workspace. This topic describes how to change the resource groups used by tasks to another resource group and how to change the workspace with which a resource group is associated to another workspace.
Background information
If you want to change the workspace with which a resource group is associated, you must disassociate the resource group from the workspace and associate the resource group with another workspace. For information about how to disassociate a resource group from a workspace, see Disassociate a resource group from a workspace.
If you want to disassociate a resource group from a workspace but the resource group is being used by deployed tasks in the workspace, you must change the resource group used by the tasks and then disassociate the resource group from the workspace. For information about how to change the resource group used by a task, see the Change the resource groups for Data Integration used by tasks and Change the resource groups for scheduling used by tasks sections in this topic.
After you change the resource group used by a task in the development environment, you can deploy the task to the production environment to change the resource group used by the task in the production environment.
You can configure a default resource group for scheduling and a default resource group for Data Integration for tasks in a workspace on the Scheduling Settings tab of the Settings page in the DataWorks console. For more information, see Configure scheduling settings.
Precautions
You can change the resource group for scheduling used by an auto triggered task and the resource group for Data Integration used by a synchronization task. If you change the resource group for scheduling used by an auto triggered task on a day, instances generated for the task after the change on the day are run on the new resource group for scheduling. Instances generated for the task before the change on the day are still run on the original resource group for scheduling. If you want to run the instances generated for the auto triggered task before the change on the day on the new resource group for scheduling, use one of the following solutions:
Solution 1: Preferentially ensure the data output on the current day
You can freeze the instances generated for the auto triggered task before the change on the current day, and backfill data for the auto triggered task after the change. Then, the system generates data backfill instances for the auto triggered task based on the latest configurations.
Solution 2: Replace instances generated for the auto triggered task before the change on the current day
After you change the resource group for scheduling for the auto triggered task, you can configure the immediate instance generation feature for the auto triggered task. This way, the system immediately generates new instances for the auto triggered task based on the latest scheduling properties of the task, and uses the new instances to replace the instances that are generated for the task before the change on the current day but are not run. Then, the new instances will be run on the new resource group for scheduling.
Change the resource groups for Data Integration used by tasks
After an exclusive resource group for Data Integration is created, you can refer to the instructions provided in the following table to change the resource groups used by tasks to the newly created resource group.
Change the resource groups for scheduling used by tasks
Environment for the operation | Supported change operation | Entry point |
Production environment | Change the resource groups for scheduling for multiple tasks in the production environment at the same time |
Important You cannot change the resource groups for zero load nodes, workflow nodes, or Platform for AI (PAI) nodes. |
Development environment |
| Go to the DataStudio page.
|
DataStudio page | Change the resource group for scheduling for a single task on the DataStudio page | Go to the configuration tab of the task for which you want to change the resource group on the DataStudio page and click the icon in the top toolbar to change the resource group for scheduling that is used to test the task. |
Disassociate a resource group from a workspace
If an exclusive resource group is not being used by deployed tasks in a workspace, you can directly disassociate the resource group from the workspace on the Exclusive Resource Groups tab of the Resource Groups page in the DataWorks console. Then, you can associate the resource group with another workspace.
If a resource group is being used by deployed tasks in a workspace, you cannot directly disassociate the resource group from the workspace. In this case, you must change the resource group for the tasks and use another resource group to run the tasks. Then, you can disassociate the resource group from the workspace.
Log on to the DataWorks console.
In the left-side navigation pane, click Resource Groups. In the top navigation bar, select the region in which the desired resource group resides.
On the Resource Groups page, find the resource group and click Change Workspace in the Actions column. In the Modify home workspace dialog box, find the workspace from which you want to disassociate the resource group and click Unbind.