When multiple teams or workloads share a Realtime Compute for Apache Flink workspace, resource contention can cause job failures or unpredictable performance. You can create multiple namespaces within a workspace and assign each namespace its own resource quota — isolating compute units (CUs) so workloads never compete for the same capacity. This page explains how to increase or decrease CU quotas at the workspace, namespace, and queue level.
Prerequisites
Before you begin, make sure you have:
-
Access to the Realtime Compute for Apache Flink console
-
(If using a RAM user or RAM role) The permissions to view and reconfigure resources for the target workspace or namespace. For details, see Management console permissions for workspace-level access and Development console permissions for namespace-level access
How resources flow between levels
Resources flow through three levels: workspace → namespace → queue. The direction of a resource change determines where you start:
-
Scale up (top-down): Raise the workspace quota first, then allocate resources to namespaces, then assign resources to queues.
-
Scale down (bottom-up): Reduce queue allocations first, then reduce namespace allocations, then lower the workspace quota.
Each namespace has a default queue where deployments run. To improve resource isolation between workloads, create additional queues with separate quotas. See Manage resource queues.
Change the resource quota of a subscription workspace
Increase the resource quota
Scale up follows a top-down order: workspace → namespace.
-
Log on to the Realtime Compute for Apache Flink console.
-
(Optional) Increase the workspace quota. Skip this step if the workspace already has unallocated CUs available for the namespace.
-
Find the target workspace. In the Actions column, choose
> Reconfigure Workspace Resources. -
In the Reconfiguration section, enter the target value in the Target CU column. > Note: For a workspace with cross-zone high availability enabled, specify quotas for both single-zone and cross-zone CU types.
-
Read the Alibaba Cloud International Website Realtime Compute Service Level Agreement, select the Terms of Service checkbox, and click OK. Complete the payment to finalize the change. The updated quota appears in the Consumed/Purchased CUs column.
-
-
Allocate resources to the namespace.
-
Click the
icon to the left of the target workspace ID. -
In the Actions column of the target namespace, select Reconfigure Resources.
-
In the dialog box, enter the new resource quota and click OK. Resources added to the namespace go into its default queue by default. The dialog also shows the total resources available to allocate.
-
Reduce the resource quota
Scale down follows a bottom-up order: queue → namespace → workspace.
-
Log on to the Realtime Compute for Apache Flink console.
-
Click the
icon to the left of the target workspace ID. -
Click the name of the target namespace to open the development console.
-
Reduce resources allocated to a queue.
-
In the left-side navigation pane, choose O&M > Queue Management.
-
Find the target queue and click Edit in the Actions column.
-
In the Edit Queue dialog box, enter the new value in the Resources (CU) field. For example, to reduce the namespace quota from 20 CUs to 12 CUs, enter
12in the Resources (CU) field.
-
-
Reduce resources allocated to the namespace.
-
Return to the management console.
-
Click the
icon to the left of the target workspace ID. -
In the Actions column of the target namespace, select Reconfigure Resources.
-
In the dialog box, enter the new resource quota. > Note: > - The minimum adjustment unit is 1 CU. > - The namespace quota cannot be reduced below the total CUs assigned to its queues.
-
Click OK. After this step, you can either reduce the workspace quota (step 6) or assign the freed-up CUs to a new or existing namespace.
-
-
Reduce the workspace resource quota.
-
In the Actions column of the target workspace, choose
> Reconfigure Workspace Resources. -
In the Reconfiguration section, enter the target value in the Target CU column. For a workspace with cross-zone high availability enabled, specify quotas for both single-zone and cross-zone CU types.
-
Read the Alibaba Cloud International Website Realtime Compute Service Level Agreement, select the Terms of Service checkbox, and click OK. The updated quota appears in the Consumed/Purchased CUs column. To request a refund for the reduced quota, see Refunds.
-
Change the resource quota of a pay-as-you-go workspace
Workspaces created before the December 2023 release have a default quota of 9,999,999 CUs. Workspaces created after the December 2023 release have a default quota of 1,000 CUs, which can be increased up to 9,999,999 CUs.
In a pay-as-you-go workspace, you are charged for the CUs your jobs consume. See Billable items.
Increase the resource quota
-
Log on to the Realtime Compute for Apache Flink console.
-
Check the current workspace quota and namespace allocations. If the total CUs allocated across all namespaces is below the workspace quota, you can create a new namespace or assign the unallocated resources to an existing one. If the total CUs allocated across all namespaces equals the workspace quota, increase the workspace quota before allocating more resources to namespaces.
-
To view the workspace quota: in the Actions column, choose More > Editing of quota ceilings.
-
To view CU allocations per namespace: click the
icon to the left of the workspace ID.
-
-
Increase the workspace quota.
-
In the Actions column of the target workspace, choose More > Editing of quota ceilings.
-
In the dialog box, enter the new quota value.
-
-
Increase the namespace quota.
-
Click the
icon to the left of the target workspace ID. -
In the Actions column of the target namespace, select Reconfigure Resources.
-
In the dialog box, enter the new namespace quota.
-
Reduce the resource quota
Scale down follows a bottom-up order: queue → namespace → workspace.
-
Log on to the Realtime Compute for Apache Flink console.
-
Find the target workspace and click the
icon to the left of its ID. -
Click the name of the target namespace to open the development console.
-
Reduce resources allocated to a queue.
-
In the left-side navigation pane, choose O&M > Queue Management.
-
Find the target queue and click Edit in the Actions column.
-
In the Edit Queue dialog box, enter the new value in the Resources (CU) field. For example, to reduce the namespace quota from 20 CUs to 12 CUs, enter
12in the Resources (CU) field.
-
-
Reduce resources allocated to the namespace.
-
Return to the management console.
-
Find the target namespace and click Reconfigure Resources in the Actions column.
-
In the dialog box, enter the new value in the Quota Ceiling (CU) field. > Note: > - The minimum adjustment unit is 1 CU. > - The namespace quota cannot be reduced below the total CUs assigned to its queues.
-
-
Reduce the workspace quota.
-
In the Actions column of the target workspace, choose
> Editing of quota ceilings. -
In the Edit Workspace Quota Limit dialog box, enter the new quota value. > Note: The workspace quota must be equal to or greater than the total CUs allocated across all its namespaces.
-
Reconfigure resources for a hybrid-billed workspace
A hybrid-billed workspace has two resource types with separate quotas:
-
Fixed resources: Follow the same process as a subscription workspace. See Change the resource quota of a subscription workspace.
-
Elastic resources: Follow the same process as a pay-as-you-go workspace. See Change the resource quota of a pay-as-you-go workspace.
Elastic resource limits:
| Limit | Value |
|---|---|
| Maximum elastic resource quota | 1,000 CUs |
| Minimum elastic resource quota | Must be greater than or equal to allocated elastic resources |
What's next
-
To run a deployment in a specific queue, see Deploy a job.
-
To review workspace usage and billing, see View bills.
-
If you see an error about the
describevvpinstancespermission when logging on to the console, see Storage management and operations.