Viewing Basic Information

Updated on 2025-01-22 GMT+08:00

View PDF

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

Log in to the DLI management console.
In the navigation pane on the left, choose Resources > Resource Pool.
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.
Click to expand the basic information card of the elastic resource pool and view detailed information about the pool.
These details will include the name of the pool, the user who created it, the date it was created, the VPC CIDR block, and whether IPv6 is enabled. 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 Actual CUs, Used CUs, CU Range, and Specifications (Yearly/Monthly CUs) of an Elastic Resource Pool.

Figure 1 Basic information about an elastic resource pool

Actual CUs, Used CUs, CU Range, and Specifications (Yearly/Monthly CUs) of an Elastic Resource Pool

Actual CUs: number of CUs that can be allocated in the elastic resource pool.

Formula for calculating actual CUs:
- Actual CUs = min{sum(maximum CUs of the queue), maximum CUs of the elastic resource pool}.
- The calculation result must be a multiple of 16 CUs. If it is not exactly divisible by 16, round up to the nearest multiple.

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:

Calculate the sum of maximum CUs of the queues: sum(maximum CUs) = 32 + 56 = 88 CUs.
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.

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	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 CU resources may be currently engaged in computing tasks and therefore temporarily unavailable.
NOTE:

The CUs used by HetuEngine match the actual CUs.
CU range: CU settings are used to control the maximum and minimum CU ranges for elastic resource pools to avoid unlimited resource scaling.
- 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.
Specifications (Yearly/Monthly CUs): The minimum CUs selected during elastic resource pool purchase are elastic resource pool specifications. Specifications are exclusive to yearly/monthly elastic resource pools. Billing for these specifications is yearly/monthly, while any usage exceeding the specifications is billed on a pay-per-use basis.

Parent topic: Managing Elastic Resource Pools

Previous topic: Managing Elastic Resource Pools

Next topic: Managing Permissions

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.

Chatbot