Updated on 2025-09-15 GMT+08:00

Checking Basic Information

After creating an elastic resource pool, you can check and manage it on the management console.

This section describes how to check basic information about an elastic resource pool on the management console, including the VPC CIDR block, IPv6 CIDR block, and creation time.

Procedure

  1. Log in to the DLI management console.
  2. In the navigation pane on the left, choose Resources > Resource Pool.
  3. On the displayed page, select the elastic resource pool you want to check.
    • In the upper right corner of the list page, click to customize the columns to display and set the rules for displaying the table content and the Operation column.
    • In the search box above the list, you can filter the required elastic resource pool by name or tag.
  4. Click to expand the basic information card of the elastic resource pool and view detailed information about the pool.

    These details include the name of the pool, the user who created it, the date it was created, whether IPv6 is enabled, and the VPC CIDR block. If IPv6 is enabled, the subnet's IPv6 CIDR block will also be displayed.

    For the definitions of actual CUs, used CUs, CU range, and specifications (yearly/monthly CUs) of the elastic resource pool, refer to Basic Concepts Related to Elastic Resource Pools.

    Figure 1 Basic information about an elastic resource pool

Basic Concepts Related to Elastic Resource Pools

The following introduces the basic concepts of actual CUs, used CUs, CU range, and specifications of an elastic resource pool.

Actual CUs

  • Actual CUs: actual size of resources currently allocated to the elastic resource pool (in CUs).
    • When there is no queue in the resource pool, the actual CUs are equal to the minimum CUs when the elastic resource pool is created.
    • When there are queues in the resource pool, the formula for calculating actual CUs is:
      • Actual CUs = max{(min[sum(maximum CUs of queues), maximum CUs of the elastic resource pool]), minimum CUs of the elastic resource pool}.

        For details about the calculation formula, see Actual CUs Calculation Formula.

      • The calculation result must be a multiple of 16 CUs. If it cannot be exactly divided by 16 CUs, round up to the nearest multiple.
    • Scaling out or in an elastic resource pool means adjusting the actual CUs of the resource pool. Refer to Scaling Out or In an Elastic Resource Pool.
    • The actual CUs used by an elastic resource pool are billed as follows:
      • If pay-per-use billing is used, you are billed based on the number of actual CUs. Refer to Elastic Resource Pool Billing Modes.
      • If yearly/monthly billing is used, the specifications are billed on a yearly/monthly basis, and the difference between the actual CUs and the specifications (actual CUs – specifications) is billed on a pay-per-use basis. To achieve more cost-effective billing, you can change the specifications of the elastic resource pool to match the actual CUs. This ensures that all actual CUs are billed on a yearly/monthly basis, resulting in overall cost savings compared to the original method. Detailed instructions can be found in Modifying Elastic Resource Pool Specifications.
    • Example of actual CU allocation:

      In Table 1, the calculation process for the actual allocation of CUs in an elastic resource pool is as follows:

      1. Calculate the sum of maximum CUs of the queues: sum(maximum CUs) = 32 + 56 = 88 CUs.
      2. Compare the sum of maximum CUs of the queues with the maximum CUs of the elastic resource pool and take the smaller value: min{88 CUs, 112 CUs} = 88 CUs.
      3. Compare the value with the minimum CUs of the elastic resource pool and take the larger value: max(88 CUs, 64 CUs) = 88 CUs.
      4. Check if 88 CUs is a multiple of 16 CUs. Since 88 is not divisible by 16, round up to 96 CUs.
        Table 1 Example of actual CU allocation of an elastic resource pool

        Scenario

        Resource Type

        CU Range

        New elastic resource pool: 64–112 CUs

        Queues A and B are created within the elastic resource pool. The CU ranges of the two queues are:

        • CU range of queue A: 16–32 CUs
        • CU range of queue B: 16–56 CUs

        Elastic resource pool

        64–112 CUs

        Queue A

        16–32 CUs

        Queue B

        16–56 CUs

Used CUs

CUs that have been used by jobs or tasks. These resources may be executing computing tasks.

The CUs used by HetuEngine match the actual CUs.

CU Range

CU settings mainly control the maximum and minimum CU ranges for elastic resource pool scaling to avoid unlimited resource expansion risks.
  • The total minimum CUs of all queues in an elastic resource pool must be no more than the minimum CUs of the pool.
  • The maximum CUs of any queue in an elastic resource pool must be no more than the maximum CUs of the pool.
  • An elastic resource pool should at least ensure that all queues in it can run with the minimum CUs and should try to ensure that all queues in it can run with the maximum CUs.
  • When expanding the specifications of an elastic resource pool, the minimum value of the CU range is linked to the specifications (yearly/monthly CUs) of the elastic resource pool. After changing the specifications of the elastic resource pool, the minimum value of the CU range is modified to match the specifications (yearly/monthly CUs).

Specifications (Yearly/Monthly CUs)

The minimum value of the CU range selected during elastic resource pool purchase is the elastic resource pool specifications. Specifications are unique to yearly/monthly elastic resource pools. The specification part is billed on a yearly/monthly basis, while parts beyond the specifications are billed on a pay-per-use basis.