Creating an Elastic Resource Pool

Notes and Constraints

• The billing mode of an elastic resource pool cannot be changed.
• The region of an elastic resource pool cannot be changed.
• For a pay-per-use resource pool, the dedicated resource mode is selected by default. The resource pool is billed by calendar hour since it is created.
• Jobs of Flink 1.10 or later can run in elastic resource pools.
• The network segment of an elastic resource pool cannot be changed after being set.
• Associating an elastic resource pool with a queue:
  • Only pay-per-use queues (including dedicated queues) can be associated with elastic resource pools.
  • No resources are frozen.
• Currently, only yearly/monthly elastic resource pools can be scaled.
• You can only view the scaling history of resource pools in the last 30 days.
• Elastic resource pools cannot access the Internet.

  For how to access the Internet from an elastic resource pool, see Configuring the Connection Between a DLI Queue and a Data Source on the Internet.

• Changes to elastic resource pool CUs can occur when setting the CU, adding or deleting queues in an elastic resource pool, or modifying the scaling policies of queues in an elastic resource pool, or when the system automatically triggers elastic resource pool scaling. However, in some cases, the system cannot guarantee that the scaling will reach the target CUs as planned.
  • If there are not enough physical resources, an elastic resource pool may not be able to scale out to the desired target size.
  • The system does not guarantee that an elastic resource pool will be scaled in to the desired target size.

    The system checks the resource usage before scaling in the elastic resource pool to determine if there is enough space for scaling in. If the existing resources cannot be scaled in according to the minimum scaling step, the pool may not be scaled in successfully or only partially.

    The scaling step may vary depending on the resource specifications, usually 16 CUs, 32 CUs, 48 CUs, 64 CUs, etc.

    For example, if the elastic resource pool has a capacity of 192 CUs and the queues in the pool are using 68 CUs due to running jobs, the plan is to scale in to 64 CUs.

    When executing a scaling in task, the system determines that there are 124 CUs remaining and scales in by the minimum step of 64 CUs. However, the remaining 60 CUs cannot be scaled in any further. Therefore, after the elastic resource pool executes the scaling in task, its capacity is reduced to 128 CUs.

Creating an Elastic Resource Pool

1. In the navigation pane on the left, choose Resources > Resource Pool.
2. On the Resource Pool page, click Buy Resource Pool in the upper right corner.
3. On the displayed page, set the following parameters:

   Table 1 Parameters

   Parameter	Description
   Region	Select a region. Select a region near you to ensure the lowest latency possible.
   Project	Each region corresponds to a project.
   Name	Name of the elastic resource pool. The name can contain only digits, letters, and underscores (_), but cannot contain only digits or start with an underscore (_) or digit. The description can contain a maximum of 128 characters. NOTE: The elastic resource pool name is case-insensitive. Uppercase letters will be automatically converted to lowercase letters.
   Specifications	Basic: 16 to 64 CUs This edition is suitable for testing scenarios with low resource consumption and low requirements for resource reliability and availability. High reliability and availability are not supported. Queue properties and job priorities cannot be set. Notebook instances cannot be interconnected with. Standard: 64 CUs or higher This edition offers powerful computing capabilities, high availability, and flexible resource management. It is suitable for large-scale computing tasks and business scenarios with long-term resource planning needs.
   CU Range	The maximum and minimum CUs allowed for the elastic resource pool.
   Description	Description of the elastic resource pool
   CIDR Block	The CIDR block to which the elastic resource pool belongs. If you use an enhanced datasource connection, the CIDR block of the elastic resource pool cannot overlap that of the data source. The CIDR block of an elastic resource pool cannot be modified after being set. Recommended CIDR block: 10.0.0.0~10.255.0.0/16~19 172.16.0.0~172.31.0.0/16~19 192.168.0.0~192.168.0.0/16~19
   Enterprise Project	If the created elastic resource pool belongs to an enterprise project, select the enterprise project. An enterprise project facilitates project-level management and grouping of cloud resources and users. For details about how to set enterprise projects, see Enterprise Management User Guide. NOTE: This parameter is displayed only for users who have enabled the Enterprise Management Service.
   Tags	Tags used to identify cloud resources. A tag includes the tag key and tag value. If you want to use the same tag to identify multiple cloud resources, that is, to select the same tag from the drop-down list box for all services, you are advised to create predefined tags on the Tag Management Service (TMS). If your organization has configured tag policies for DLI, add tags to resources based on the policies. If a tag does not comply with the tag policies, resource creation may fail. Contact your organization administrator to learn more about tag policies. For details, see Tag Management Service User Guide. NOTE: A maximum of 20 tags can be added. Only one tag value can be added to a tag key. The key name in each resource must be unique. Tag key: Enter a tag key name in the text box. NOTE: A tag key can contain a maximum of 128 characters. Only letters, digits, spaces, and special characters (_.:=+-@) are allowed, but the value cannot start or end with a space or start with _sys_. Tag value: Enter a tag value in the text box. NOTE: A tag value can contain a maximum of 255 characters. Only letters, digits, spaces, and special characters (_.:=+-@) are allowed. The value cannot start or end with a space.

4. Click Buy and confirm the configurations.
5. Click Pay. Wait until the status of the elastic resource pool changes to Available. The elastic resource pool is successfully created.
6. Refer to Example Use Case: Creating an Elastic Resource Pool and Running Jobs and Example Use Case: Configuring Scaling Policies for Queues in an Elastic Resource Pool to perform subsequent operations as needed.