Creating a Non-Elastic Resource Pool Queue (Discarded and Not Recommended)

Notes and Constraints

• A queue named default is preset in DLI for you to experience. Resources are allocated on demand. You are billed based on the amount of data scanned in each job (unit: GB).
• Queue types:
  • For SQL: Spark SQL jobs can be submitted to SQL queues.
  • For general purpose: The queue is used to run Spark programs, Flink SQL jobs, and Flink Jar jobs.

  The queue type cannot be changed. If you want to use another queue type, purchase a new queue.

• The billing mode of a queue cannot be changed.
• The region of a queue cannot be changed.
• Queues with 16 CUs do not support scale-out or scale-in.
• Queues with 64 CUs do not support scale-in.
• When creating a queue, you can only select cross-AZ active-active for yearly/monthly queues and pay-per-use dedicated queues. The price of a cross-AZ queue is twice that of a single-AZ queue.
• Newly created queues need to run jobs before they can be scaled in or out.
• DLI queues cannot access the Internet.

Procedure

1. You can create a queue on the Overview, SQL Editor, or Queue Management page.
   • In the upper right corner of the Overview page, click Purchase Queue.
   • To create a queue on the Queue Management page:
     1. In the navigation pane on the left of the DLI management console, choose Resources > Queue Management.
     2. In the upper right corner of the Queue Management page, click Buy Queue to create a queue.
   • To create a queue on the SQL Editor page:
     1. In the navigation pane of the DLI management console, click SQL Editor.
     2. Click Queues. On the tab page displayed, click on the right to create a queue.
2. On the Buy Queue page displayed, set the parameters according to Table 1.

   Table 1 Parameters

   Parameter	Description
   Billing Mode	Pay-per-use Billing for CUH used = Number of CUs x Usage duration x Unit price. You are billed for used CUs on an hourly basis (rounded up to the nearest hour). The pay-per-use billing mode is adopted. You are advised to purchase the CUH package to enjoy preferential price.
   Region	Select a region. Select a region near you to ensure the lowest latency possible.
   Project	Each region corresponds to a project.
   Name	Queue name Only numbers, letters, and underscores (_) are allowed. The value cannot contain only numbers, start with an underscore (_), or be left unspecified. The value can contain a maximum of 128 characters. NOTE: The queue name is case-insensitive. Uppercase letters will be automatically converted to lowercase letters.
   Type	For SQL: compute resources used for SQL jobs. For general purpose: compute resources used for Spark and Flink jobs. NOTE: When a dedicated queue is not in use, its resources are still reserved and not released. This means that resources are constantly being held, regardless of whether the queue is being utilized. By using a dedicated queue, resources can be guaranteed to be available whenever jobs are submitted. You can create enhanced datasource connections for a dedicated queue. When buying a pay-per-use queue, you have the option to choose a dedicated queue. Dedicated queues are billed 24/7 regardless of whether they are used.
   AZ Mode	Available only when Dedicated Resource Mode is selected for Type. The deployment mode for the DLI queue. Select dual-AZ if you require high availability. NOTE: Currently, only SQL queues in dedicated resource mode support the dual-AZ policy. Dual-AZ improves data availability by creating a duplicate queue in the second AZ, but at an increased cost (twice as much as that of single AZ mode). This is a one-time configuration and cannot be changed later.
   Specifications	The compute nodes' total number of CUs. One CU equals one vCPU and 4 GB of memory. DLI automatically assigns CPU and memory resources to each compute node, and the client does not need to know how many compute nodes are being used.
   Enterprise Project	If the created queue belongs to an enterprise project, you can select the corresponding enterprise project. Enterprise projects let you manage cloud resources and users by project. For how to set an enterprise project, see the Enterprise Management User Guide. NOTE: This parameter is displayed only for users who have enabled the Enterprise Management Service.
   Description	Description of the queue to be created. The value can contain a maximum of 128 characters.
   Advanced Settings	In the Queue Type area, select Dedicated Resource Mode and then click Advanced Settings. Default: The system automatically configures the parameter. Custom CIDR Block: Enter a CIDR block range. If DLI enhanced datasource connection is used, the CIDR block of the DLI queue cannot overlap with that of the data source. Recommended CIDR block: 10.0.0.0–10.255.0.0/8–24 172.16.0.0–172.31.0.0/12–24 192.168.0.0–192.168.0.0/16–24 Queue Type: When running an AI-related SQL job, select AI-enhanced. When running other jobs, select Basic.
   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, numbers, 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, numbers, spaces, and special characters (_.:=+-@) are allowed. The value cannot start or end with a space.

3. Click Buy to confirm the configuration.
   

   When creating a queue for the first time, select Agree to the above privacy agreements and click OK.

4. Confirm the configuration and click Submit.

   If the queue name already exists, the system displays a message indicating that the queue name already exists when you click Submit. In this case, click Previous to go back to modify the queue name.

5. Once created, you can check and use it on the Queue Management page.

   

   It takes 6 to 10 minutes for a job running on a new queue for the first time.