This topic provides answers to frequently asked questions about nodes that are in the Pending (Resources) state.

Why does the Pending (Resources) state occur?

A node is committed and scheduled on the execution engine. During this process, the node may need to wait in a queue for resources in the following scenarios:
  • The node is waiting for resource groups for scheduling.
  • The node is waiting for resource groups for Data Integration.
  • A MaxCompute node is waiting for computing resources.
Note The resources contained in a resource group are limited. If the resources are occupied by a node for a long time, other nodes that have no available resources must wait for the resources to be released.

Why does a node keep waiting for gateway resources?

Cause: The maximum number of concurrent nodes is reached for the current resource group for scheduling.

Solution: The node can be run only after the resources are released by other nodes. You can also scale out your exclusive resource group for scheduling to resolve this issue.

  • If you use a shared resource group for scheduling, you can view the resource group usage on the Overview page.

    Nodes may need to wait for resources from 00:00:00 to 09:00:00 every day, which is the peak hours for nodes that require scheduling resources. You can run nodes at another time of the day or purchase exclusive resource groups for scheduling in the DataWorks console.

  • If you use exclusive resource groups for scheduling, you can view the nodes that are being executed and the resource group usage in the DataWorks console.

    The maximum number of concurrent nodes varies based on the exclusive resource groups for scheduling of different specifications. For more information, see Performance metrics and billing standards of exclusive resource groups for scheduling.

    Log on to the DataWorks console. In the left-side navigation pane, click Resource Groups. On the Exclusive Resource Groups tab, find the exclusive resource group of which you want to view the usage and click the displayed usage in the Resource Group Usage column.Resource Group UsageResource Group Usage
  • View the information about nodes that are being executed while other nodes are waiting for resources for scheduling.
    To view the nodes that are occupying the resources, right-click the node in the Pending (Resources) state in the directed acyclic graph (DAG) and choose Instance Diagnose > Resources. Instance Diagnose
    On the Intelligent Diagnosis page, you can view the information about the nodes that are being executed, nodes in the Pending (Resources) state, and nodes that are occupying the resources. The information about the resource group usage

Why does a data integration node keep waiting for resources?

Cause:

The node is committed and scheduled, but the value of the State parameter in the log indicates that the node is waiting for resources. This issue occurs because the number of concurrent nodes exceeds the upper limit for the resource group for Data Integration. Therefore, the data integration node keeps waiting for resources. Check whether the number of concurrent nodes exceeds the upper limit for the resource group for Data Integration.

Notice The maximum number of concurrent nodes varies based on the exclusive resource groups for Data Integration of different specifications. For more information, see Performance metrics and billing standards of exclusive resource groups for Data Integration
  • View the value of the Concurrent parameter in the log to check whether the value exceeds the upper limit for the resource group for Data Integration.
  • You may set the Concurrent parameter of a node to a value that exceeds the upper limit for the resource group for Data Integration. In this case, stop the node and change the value of the Concurrent parameter before you run the node.

Solution:

The node can be run only after the resources are released by other nodes. You can also scale out your exclusive resource group for Data Integration to resolve this issue.

View the concurrency for the data integration node that is run on the current resource group for Data Integration.
  • Choose Overview > Data Integration. On the Data Integration page, view Synchronization task execution details by scrolling to the bottom of this page.

View resource group usage in the DataWorks console

Log on to the DataWorks console. In the left-side navigation pane, click Resource Groups. On the Exclusive Resource Groups tab, find the exclusive resource group of which you want to view the usage and click the displayed usage in the Resource Group Usage column.

Notice
  • You must set the concurrency of a node based on the maximum number of concurrent nodes that are allowed by the resource group for Data Integration. For more information, see Performance metrics and billing standards of exclusive resource groups for Data Integration. In addition, you must also consider the number of nodes that run at the same time and the sum of the concurrency of all nodes to be run.
  • If multiple nodes must be run at the same time, we recommend that you scale out your exclusive resource group for Data Integration.