Overview

Queue

Queues in DLI are computing resources, which are the basis for using DLI. All executed jobs require computing resources.

Currently, DLI provides two types of queues: For SQL and For general purpose.

  • For SQL: The queue is used to run SQL jobs.

  • For general purpose: The queue is used to run Spark programs, Flink SQL jobs, and Flink Jar jobs.

Constraints

  • A queue named default is preset in DLI for you to experience. Resources are allocated on demand.

  • 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 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.

  • A newly created queue can be scaled in or out only after a job is executed on the queue.

  • DLI queues cannot access the Internet.

Difference Between Computing and Storage Resources

Table 1 Difference between computing and storage resources

Resource

How to Obtain

Function

Compute resource

Create queue on the DLI management console.

Used for executing queries.

Storage resource

DLI has a 5 GB quota.

Used for storing data in the database and DLI tables.

Note

  • Storage resources are internal storage resources of DLI for storing database and DLI tables and represent the amount of data stored in DLI.

  • By default, DLI provides a 5 GB quota for storage resources.

  • A queue named default is preset in DLI. If you are uncertain about the required queue capacity or have no available queue capacity to run queries, you can execute jobs using this queue.

  • The default queue is used only for user experience. It may be occupied by multiple users at a time. Therefore, it is possible that you fail to obtain the resource for related operations. You are advised to use a self-built queue to execute jobs.

Dedicated Queue

Resources of a dedicated queue are not released when the queue is idle. That is, resources are reserved regardless of whether the queue is used. Dedicated queues ensure that resources exist when jobs are submitted.

Elastic Scaling

DLI allows you to flexibly scale in or out queues on demand. After a queue with specified specifications is created, you can scale it in and out as required.

To change the queue specifications, see Elastic Scaling.

Note

Scaling can be performed for a newly created queue only when jobs are running on this queue.

Scheduled Elastic Scaling

DLI allows you to schedule tasks for periodic queue scaling. After creating a queue, the scheduled scaling tasks can be executed.

You can schedule an automatic scale-out/scale-in based on service requirements. The system periodically triggers queue scaling. For details, see Scheduling CU Changes.

Note

Scaling can be performed for a newly created queue only when jobs are running on this queue.

Automatic Queue Scaling

Flink jobs use queues. DLI can automatically trigger scaling for jobs based on the job size.

Note

Scaling can be performed for a newly created queue only when there are jobs running on this queue.

Queue Management Page

Queue Management provides the following functions:

Note

To receive notifications when a DLI job fails, SMN Administrator permissions are required.

The queue list displays all queues created by you and the default queue. Queues are listed in chronological order by default in the queue list, with the most recently created queues displayed at the top.

Table 2 Parameter description

Parameter

Description

Name

Name of a queue.

Type

Queue type.

  • For SQL

  • For general purpose

  • Spark queue (compatible with earlier versions)

Specifications

Queue size. Unit: CU

CU is the pricing unit of queues. A CU consists of 1 vCPU and 4-GB memory. The computing capabilities of queues vary with queue specifications. The higher the specifications, the stronger the computing capability.

Actual CUs

Actual size of the current queue.

Elastic Scaling

Target CU value for scheduled scaling, or the maximum and minimum CU values of the current specifications.

Username

Queue owner

Description

Description of a queue specified during queue creation. If no description is provided, -- is displayed.

Operation

  • Delete: Allow you to delete the selected queue. You cannot delete a queue where there are running jobs or jobs are being submitted.

  • Manage Permissions: You can view the user permissions corresponding to the queue and grant permissions to other users.

  • More

    • Restart: Forcibly restart a queue.

      Note

      Only the SQL queue has the Restart operation.

    • Elastic Scaling: You can select Scale-out or Scale-in as required. The number of CUs after modification must be an integer multiple of 16.

    • Schedule CU Changes: You can set different queue sizes at different time or in different periods based on the service period or usage. The system automatically performs scale-out or scale-in as scheduled. The After Modification value must be an integer multiple of 16.

    • Modifying CIDR Block: When DLI enhanced datasource connection is used, the CIDR block of the DLI queue cannot overlap with that of the data source. You can modify the CIDR block as required.

    • Test Address Connectivity: Test whether the queue is reachable to the specified address. The domain name and IP address are supported. The port can be specified.

last updated: 2024-05-18 00:03