All Products
Search

This Product

    Realtime Compute for Apache Flink:Manage queues

    Document Center

    Realtime Compute for Apache Flink:Manage queues

    Last Updated:Jun 17, 2026

    Resource queues isolate and allocate compute resources across deployments within a namespace. Each namespace includes a default queue named default-queue. You can create custom queues to prevent a single deployment or user from consuming all available resources.

    Usage notes

    • Queues run only in exclusive mode. Resources in a queue cannot be preempted by other queues.

    • After resources in a queue are released, they become available for new deployments.

    • If no custom queue exists, all deployments run in default-queue.

    Assign a queue to a workload

    Workload type Where to set Parameter Reference
    Deployment Deploy draft dialog box Deployment Target Create a deployment
    Session cluster Standard section of the Create Session Cluster page Deployment Target Create a session cluster
    Workflow Create Workflow panel Resource Queue Manage workflows

    Common console steps

    The following procedures all begin with the same navigation steps:

    1. Log on to the Realtime Compute for Apache Flink console.

    2. Find the target workspace and click Console in the Actions column.

    3. In the left-side navigation pane, choose O&M > Queue Management.

    Add a queue

    Queue name rules

    Rule Detail
    Uniqueness Must be unique within the namespace
    Length Maximum 32 characters
    Characters Lowercase letters, digits, and hyphens (-) only
    Mutability Cannot be changed after creation

    Procedure

    1. Complete the common console steps.

    2. In the upper-left corner of the Queue Management page, click Add queue.

    3. Configure the queue parameters. The parameters vary depending on whether elastic resources are allocated to the namespace.

      Namespaces without elastic resources

      Applies when the workspace billing method is pay-as-you-go, subscription, or Hybrid billing, and no elastic resources are allocated to the namespace.

      Parameter Description
      Queue Name Enter a name that follows the queue name rules.
      Resources (CU) Number of CUs available to the queue. The maximum value equals the remaining unallocated CUs in the namespace. If insufficient CUs are available, reconfigure CUs in other queues (see Edit a queue) or increase namespace resources (see Reconfigure resources).

      Namespaces with elastic resources

      Applies when the workspace billing method is Hybrid billing and elastic resources are allocated to the namespace.

      Parameter Description
      Queue Name Enter a name that follows the queue name rules.
      Fixed Resources (CUs) Number of fixed CUs available to the queue. If insufficient fixed CUs are available, adjust resources using the subscription workspace method. See Reconfigure resources.
      Elastic Resources (CUs) Number of elastic CUs available to the queue. The Queue Management page shows the maximum allocatable elastic CUs. If insufficient elastic CUs are available, adjust resources using the pay-as-you-go workspace method. See Reconfigure resources.

    4. Click OK.

    Edit a queue

    Adjust the CU allocation for an existing queue when resource needs change.

    1. Complete the common console steps.

    2. Find the target queue and click Edit in the Actions column.

    3. In the Edit Queue dialog box, update the resource values. For parameter descriptions, see Add a queue.

      Important

      The Resources (CU) value cannot be lower than the number of CUs currently in use by the queue.

    4. Click OK.

    Delete a queue

    Important

    • The default queue (default-queue) cannot be deleted.

    • A queue with running deployments cannot be deleted.

    • Deleting a queue that is referenced by a deployment causes an error when that deployment restarts.

    1. Complete the common console steps.

    2. Find the target queue, click Delete in the Actions column, and then click OK.

    Use cases

    • Isolate batch workloads: Assign batch deployments to dedicated queues to prevent them from starving other jobs of resources.

    • Prioritize critical jobs: Combine queues with the Workflows (public preview) feature to set scheduling priorities for batch drafts.

    References