On the Resource Groups page, you can view the resource usage, resource usage trend, running nodes, and queuing nodes of your exclusive resource group in real time. Then, you can monitor the resource usage of specific nodes and adjust inefficient resource use at the earliest opportunity.

Procedure

  1. Log on to the DataWorks console.
  2. In the top navigation bar, select the region where your exclusive resource group resides. In the left-side navigation pane, click Resource Groups. On the Exclusive Resource Groups tab, you can view the values of Type and Resource Group Usage of each exclusive resource group.
    1
  3. On the Exclusive Resource Groups tab, find the exclusive resource group whose resource usage you want to view and click the value in the Resource Group Usage column. On the page that appears, view the resource usage of your exclusive resource group.
    The following figure shows the details and resource usage of an exclusive resource group. 1The following figure shows the nodes that are running on an exclusive resource group. Running nodesThe following table describes the details and resource usage of an exclusive resource group.
    No.ParameterDescription
    1Resource Group DetailsThe basic information about the exclusive resource group, including the name, description, type, and service status.
    2Running NodesThe number of nodes that are running on the exclusive resource group.
    Click Running Nodes. Then, you can view the details of the nodes in the Running Nodes dialog box. The details include the following parameters:
    • Nodes: the category of a node that is running on the exclusive resource group, such as the development node, manually triggered node, and auto triggered node.
      • For an instance such as an auto triggered node instance or a data backfill instance in a production environment, you can click Go to operations in the Actions column to go to Operation Center and view the instance details.
        Important For an auto triggered node instance, the Go to operations entry is available only after the related auto triggered node is deployed.
      • The following nodes are auto triggered nodes:
        • Nodes on the DataStudio page that use resources in exclusive resource groups
        • Real-time synchronization nodes on the Operation Center page that use resources in exclusive resource groups for Data Integration
        You can go to the related development pages to view the details of specific nodes.
    • Node Type: the type of a node, such as Data Integration and ODPS SQL.
    • Owner: the owner of a node.
    • Scheduled Time: the time when a node is scheduled to run. For a running node on the DataStudio page, the value of this parameter indicates the time when the node is triggered to run.
    • Start From: the time when a node starts to run.
    Note The number of nodes that can run on a resource group at the same time is limited. If a node runs for a long period of time, the resources used by the node cannot be released. This may block other nodes.
    Queuing NodesThe number of nodes that are waiting for resources in the exclusive resource group.
    Note The number of nodes that can run on a resource group at the same time depends on the specifications and number of resources in the resource group. For more information, see the following topics:
    3Resource UsageThe real-time usage of the resources in the exclusive resource group.
    4Trend for Resource UsageThe resource usage of the exclusive resource group over time. You can specify a time range to view the trend of resource usage within this time range.
    5Scale Out and Scale InThe entries for scaling out or in the exclusive resource group. After you click Scale Out or Scale in, you can specify the number of resources that you want to add or remove and click Buy Now on the page that appears.

    The specifications of the resources that are added to or removed from the resource group are the same as the resource specifications that you specified when you purchase the resource group.

What to do next

If you cannot resolve issues by following the instructions provided in this topic, you can refer to the instructions provided in Nodes that are not run to resolve the issues.