All Products
Search
Document Center

Realtime Compute for Apache Flink:Reconfigure resources

Last Updated:Mar 27, 2024

Realtime Compute for Apache Flink allows you to reconfigure resources for workspaces and namespaces. You can create multiple namespaces and assign separate resources and permissions to each namespace. This way, resources and permissions are isolated among namespaces. This topic describes how to reconfigure resources for workspaces and namespaces.

Precautions

If you use a RAM user, a RAM role, or another Alibaba Cloud account to reconfigure resources for a fully managed Flink workspace or namespace, make sure that the RAM user, RAM role, or Alibaba Cloud account has the permissions to view the workspace or namespace and reconfigure the resources for the workspace or namespace. For more information, see Grant permissions to a RAM user.

Description

To reconfigure resources for a subscription workspace, you can scale in or scale out the workspace. To reconfigure resources for a pay-as-you-go workspace, you can reconfigure the upper limit of quota for the workspace. Take note of the following points when you reconfigure resources:

  • You can add or reduce at least one compute unit (CU) each time you reconfigure resources.

  • The default value of the Quota Ceiling parameter that specifies the upper limit of quota for a pay-as-you-go workspace varies based on the time at which you purchase the workspace.

    • If you purchase a workspace before the new version is released in December 2023, the default value of Quota Ceiling is 9999999 (CUs).

    • If you purchase a workspace after the new version is released in December 2023, the default value of Quota Ceiling for the workspace is 1000 (CUs), and the maximum value of the parameter is 9999999 (CUs).

  • When you reconfigure resources for a workspace, the number of CUs that you configure for the workspace after modification cannot be less than the number of allocated CUs in the workspace.

  • When you reconfigure resources for a namespace, take note of the following points:

    • If you increase resources for a subscription namespace, the sum of quotas for the namespaces in the current workspace cannot be greater than the quota purchased for the workspace. If you increase resources for a pay-as-you-go namespace, the sum of the upper limits of quotas for the namespaces in the current workspace cannot be greater than the upper limit of quota configured for the workspace.

    • If you reduce resources for a namespace, the total number of CUs that are allocated to queues in the namespace cannot be greater than the number of CUs that are allocated to the namespace. The number of CUs that you configure for the namespace after modification cannot be less than the number of CUs that are used by the namespace.

    • By default, the CUs that are added are allocated to the default queue named default-queue. If you reduce resources for a namespace, the number of CUs allocated to the default queue named default-queue in the namespace does not change. You can manually adjust the number of CUs allocated to each queue.

Reconfigure resources for a subscription workspace or namespace

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

  2. (Optional) Reconfigure resources for a subscription workspace

    1. On the Fully Managed Flink tab, find the workspace that you want to manage and choose More > Reconfigure Workspace Resources in the Actions column.

    2. (Optional) In the Reconfigure Workspace Resources dialog box, click Add CU Type, specify a secondary zone, and then select a vSwitch for the secondary zone to enable cross-zone high availability.

    3. In the Reconfiguration section of the Reconfigure Workspace Resources dialog box, enter values in the Target CU column for the single-zone CU type and cross-zone CU type.

    4. Read the terms of service, and select I have read and agree to Alibaba Cloud International Website Realtime Compute Service Level Agreement.

    5. Click OK to complete the payment.

      After you complete the payment, you can view the new resource quota in the Consumed/Purchased CUs column that corresponds to the workspace.

  3. Reconfigure resources for a subscription namespace

    1. On the Fully Managed Flink tab, click the 展开按钮 icon on the left side of the ID of the workspace in which you want to reconfigure namespace resources.

    2. Find the desired namespace and click Reconfigure Resources in the Actions column.

    3. In the Reconfigure Resources dialog box, move the slider next to the namespace name to reconfigure resources and click OK.

Each fully managed Flink namespace has a default queue named default-queue to run deployments. If you want to isolate and manage resources, you can add queues to a namespace and configure resources for the queues. For more information, see Manage queues.

Configure the upper limit of quota for a pay-as-you-go workspace or namespace

In specific scenarios, such as the execution of a batch deployment, you can configure the upper limit of quota to increase the number of CUs that you can use when you need more resources. This ensures that resources increase within an acceptable scope.

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

  2. (Optional) Configure the upper limit of quota for a pay-as-you-go workspace

    1. On the Fully Managed Flink tab, find the workspace that you want to manage and choose More > Editing of quota ceilings in the Actions column.

    2. In the Edit Workspace Quota Limit dialog box, move the slider to reconfigure resources and click OK.

  3. Configure the upper limit of quota for a pay-as-you-go namespace

    1. On the Fully Managed Flink tab, click the 展开按钮 icon on the left side of the ID of the workspace in which you want to reconfigure namespace resources.

    2. Find the desired namespace and click Reconfigure Resources in the Actions column.

    3. In the Allocation of namespace quota ceilings dialog box, move the slider next to the namespace name to reconfigure resources and click OK.

Each fully managed Flink namespace has a default queue named default-queue to run deployments. If you want to isolate and manage resources, you can add queues to a namespace and configure resources for the queues. For more information, see Manage queues.

References