After you purchase and configure an exclusive resource group or a custom resource group, you can use the resource group to run nodes in a workspace. This topic describes how to change the resource group used by nodes 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 the resource group is being used by deployed nodes in a workspace, you must change the resource group used by the nodes, and then disassociate the resource group from the workspace. For information about how to change the resource group used by nodes, see the Change the exclusive resource group for Data Integration used by nodes and Use the exclusive resource group for scheduling sections in this topic.
  • After you change the resource group used by nodes in the development environment, you can deploy the nodes to the production environment to change the resource group used by the nodes in the production environment.
  • You can configure a default resource group for scheduling and a default resource group for Data Integration for nodes 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 auto triggered nodes that are scheduled by minute or hour and the resource group for Data Integration used by data synchronization nodes. After you change the resource group for scheduling used by an auto triggered node that is scheduled by minute or hour, instances generated for the auto triggered node after the change on the current day are run on the new resource group for scheduling. Instances generated for the auto triggered node before the change on the current day are still run on the original resource group for scheduling. If you want to run the instances generated for the auto triggered node before the change on the current 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 node before the change on the current day, and backfill data for the auto triggered node after the change. Then, the system generates data backfill instances for the auto triggered node.

  • Solution 2: Replace instances generated for the auto triggered node before the change on the current day

    After you change the resource group for scheduling for the auto triggered node, you can configure the immediate instance generation feature for the auto triggered node. This way, the system immediately generates new instances for the auto triggered node based on the latest scheduling properties of the node, and uses the new instances to replace the instances that are generated for the node 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 exclusive resource group for Data Integration used by nodes

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 group used by nodes to the newly created resource group.
Environment for the operationSupported change operationEntry point
Production environmentChange the resource groups for Data Integration for multiple nodes in the production environment at the same timeGo to the Operation Center page and choose Cycle Task Maintenance > Cycle Task in the left-side navigation pane.
Select the nodes for which you want to change the resource groups, click More in the lower part of the Cycle Task page, and then select Modify Data Integration Resource Group. Change the resource groups for multiple nodes at the same time
Development environment
  • Change the resource group for Data Integration for a single node in the development environment
  • Change the resource groups for Data Integration for multiple nodes in the development environment at the same time
Go to the DataStudio page.
  • Change the resource group for a single node

    Go to the configuration tab of the node for which you want to change the resource group, click More in the Establish Network Connections step, select the type of the resource group that you want to use, and then select the resource group from the drop-down list.

  • Change the resource groups for multiple nodes at the same time

    Click the Batch Operation icon. On the Batch Operation-Data Development tab, select the nodes for which you want to change the resource groups, click More in the lower part of the tab, and then select Change Resource Group for Data Integration.

Note If you cannot find the entry point of changing the resource groups for nodes, you can select Offline synchronization from the Node Type drop-down list in the filter condition section to search for all batch synchronization nodes.

Use the exclusive resource group for scheduling

Environment for the operationSupported change operationEntry point
Production environmentChange the resource groups for scheduling for multiple nodes in the production environment at the same time
  1. In the left-side navigation pane of the Operation Center page, choose Cycle Task Maintenance > Cycle Task.
  2. Select the nodes for which you want to change the resource groups and click Modify Scheduling Resource Group in the lower part of the Cycle Task page.
Note You cannot change the resource groups for zero load nodes, workflow nodes, or Machine Learning nodes.
Development environment
  • Change the resource group for scheduling for a single node in the development environment
  • Change the resource groups for scheduling for multiple nodes in the development environment at the same time
Go to the DataStudio page.
  • Change the resource group for a single node

    Go to the configuration tab of the node for which you want to change the resource group and select the resource group for scheduling that you want to use for the node in the Configure Scheduling Settings step.

  • Change the resource groups for multiple nodes at the same time

    Click the Batch Operation icon. On the Batch Operation-Data Development tab, select the nodes for which you want to change the resource groups, click More in the lower part of the tab, and then select Change Resource Group for Scheduling.

DataStudio pageChange the resource group for scheduling for a single nodeGo to the configuration tab of the node for which you want to change the resource group and click the Change icon in the top toolbar to change the resource group for scheduling that is used to test the node.

Disassociate a resource group from a workspace

If an exclusive resource group or a custom resource group for scheduling is not being used by deployed nodes in a workspace, you can directly disassociate the resource group from the workspace on the Exclusive Resource Groups tab in the DataWorks console. Then, you can associate the resource group with another workspace.
Note If a resource group is being used by deployed nodes in a workspace, you cannot directly disassociate the resource group from the workspace. In this case, you must change the resource group for the nodes and use another resource group to run the nodes. Then, you can disassociate the resource group from the workspace.
  1. Log on to the DataWorks console.
  2. In the left-side navigation pane, click Resource Groups. In the top navigation bar, select the region in which the desired resource group resides.
  3. 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.