All Products
Search

This Product

    Realtime Compute for Apache Flink:FAQ about the activation and billing of fully managed Flink

    Document Center

    Realtime Compute for Apache Flink:FAQ about the activation and billing of fully managed Flink

    Last Updated:Dec 21, 2023

    This topic provides answers to some frequently asked questions about the activation and billing of fully managed Flink.

    Why am I unable to go to the RAM console after I click Authorize in RAM?

    • Problem description

      After I click Purchase in the Realtime Compute for Apache Flink console, the Authorization Request page appears. After I click Authorize in RAM, I am redirected to the Realtime Compute for Apache Flink console and cannot go to the Resource Access Management (RAM) console. As a result, manual authorization fails.

    • Cause

      The AliyunStreamAsiDefaultRole role is manually added before you perform the authorization. As a result, the system skips the authorization process when this role is automatically assigned.

    • Solution

      Log on to the RAM console and delete the AliyunStreamAsiDefaultRole role that is manually added. This way, you can click Authorize in RAM on the buy page of fully managed Flink to perform the authorization.RAM

    What do I do if the error message "Message: Forbidden!Configured service account doesn't have access. Service account may have been revoked. pods "job-*-taskmanager-2-5" is forbidden: exceeded quota: resourcequota, requested: limits.memory=5Gi, used: limits.memory=39424Mi, limited: limits.memory=40Gi." appears?

    • Problem description

      Caused by: io.fabric8.kubernetes.client.KubernetesClientException: Failure executing: POST at: https://kubernetes.default:6443/api/v1/namespaces/vvp-workload/pods. Message: Forbidden!Configured service account doesn't have access. Service account may have been revoked. pods "job-8c99342c-8ac5-43df-8c60-b43f1db5****-taskmanager-2-5" is forbidden: exceeded quota: resourcequota, requested: limits.memory=5Gi, used: limits.memory=39424Mi, limited: limits.memory=40Gi.
    at io.fabric8.kubernetes.client.dsl.base.OperationSupport.requestFailure(OperationSupport.java:694) ~[flink-dist_2.11-1.13-vvr-4.0.14-2-SNAPSHOT.jar:1.13-vvr-4.0.14-2-SNAPSHOT]
    at io.fabric8.kubernetes.client.dsl.base.OperationSupport.requestFailure(OperationSupport.java:673) ~[flink-dist_2.11-1.13-vvr-4.0.14-2-SNAPSHOT.jar:1.13-vvr-4.0.14-2-SNAPSHOT]
    at io.fabric8.kubernetes.client.dsl.base.OperationSupport.assertResponseCode(OperationSupport.java:624) ~[flink-dist_2.11-1.13-vvr-4.0.14-2-SNAPSHOT.jar:1.13-vvr-4.0.14-2-SNAPSHOT]
    at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:566) ~[flink-dist_2.11-1.13-vvr-4.0.14-2-SNAPSHOT.jar:1.13-vvr-4.0.14-2-SNAPSHOT]
    at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:527) ~[flink-dist_2.11-1.13-vvr-4.0.14-2-SNAPSHOT.jar:1.13-vvr-4.0.14-2-SNAPSHOT]
    at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleCreate(OperationSupport.java:315) ~[flink-dist_2.11-1.13-vvr-4.0.14-2-SNAPSHOT.jar:1.13-vvr-4.0.14-2-SNAPSHOT]
    at io.fabric8.kubernetes.client.dsl.base.BaseOperation.handleCreate(BaseOperation.java:734) ~[flink-dist_2.11-1.13-vvr-4.0.14-2-SNAPSHOT.jar:1.13-vvr-4.0.14-2-SNAPSHOT]
    at io.fabric8.kubernetes.client.dsl.base.BaseOperation.handleCreate(BaseOperation.java:87) ~[flink-dist_2.11-1.13-vvr-4.0.14-2-SNAPSHOT.jar:1.13-vvr-4.0.14-2-SNAPSHOT]
    at io.fabric8.kubernetes.client.dsl.base.CreateOnlyResourceOperation.create(CreateOnlyResourceOperation.java:61) ~[flink-dist_2.11-1.13-vvr-4.0.14-2-SNAPSHOT.jar:1.13-vvr-4.0.14-2-SNAPSHOT]
    at org.apache.flink.kubernetes.kubeclient.Fabric8FlinkKubeClient.lambda$createTaskManagerPod$0(Fabric8FlinkKubeClient.java:153) ~[flink-dist_2.11-1.13-vvr-4.0.14-2-SNAPSHOT.jar:1.13-vvr-4.0.14-2-SNAPSHOT]
    at java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1640) ~[?:1.8.0_302]
    ... 3 more

    • Cause

      The compute units (CUs) that are purchased for the workspace are exhausted.

    • Solution

      Increase the number of CUs for the workspace or decrease the number of resources requested by the deployment. For more information, see Reconfigure resources.

    Does a fully managed Flink workspace support the conversion between the subscription and pay-as-you-go billing methods?

    Yes, a fully managed Flink workspace supports the conversion between the subscription and pay-as-you-go billing methods. To change the billing method of a workspace, perform the following operations: Log on to the Realtime Compute for Apache Flink console. Find the workspace whose billing method you want to change and choose More > Convert To Subscription Billing Method or Convert To Metered Billing in the Actions column. For example, find the desired workspace and choose More > Convert To Subscription Billing Method.

    What are the default billable items for renewal?

    Billable item

    Description

    Management resource

    When you create a workspace, the system deploys a console for the workspace. The console and its components require approximately 2 CUs of management resources.

    Computing resource

    Computing resources are the resources that are used for computing. You are charged for the computing resources based on the subscription or pay-as-you-go billing method. The billing unit is CU.

    Important

    If you renew a fully managed Flink workspace, you are charged only for fully managed Flink and are not charged for other related cloud services, such as virtual private cloud (VPC), Object Storage Service (OSS), and Application Real-Time Monitoring Service (ARMS). For more information, see Billing rules for supporting services.

    How do I renew a fully managed Flink workspace?

    Fully managed Flink workspaces support manual renewal and auto-renewal. For more information, see Renewal policy.

    How do I apply for a refund when I no longer need to use a workspace?

    You are charged for pay-as-you-go workspaces only after you use the workspaces. Therefore, refunds are not supported for pay-as-you-go workspaces. If you no longer need to use a pay-as-you-go workspace, you can find the workspace on the Fully Managed Flink tab in the console of fully managed Flink and choose More > Release Resources in the Actions column to release the workspace after you ensure that data is backed up or migrated and your business is not affected.

    You make a payment based on the subscription duration when you purchase a subscription workspace. If you do not need to use the workspace, you can apply for a refund. For more information about refund rules and operations, see Refund policy.

    Is an amount of fee deducted from my account balance if a workspace fails to be created?

    No, no fee is deducted from your account balance if a workspace fails to be created. You can view the billing details for the deduction items. For more information, see View your bills.

    Am I still charged after I create a pay-as-you-go workspace but do not run a deployment on the workspace?

    Yes, you are charged for the workspace. If you create a pay-as-you-go fully managed Flink workspace, you are charged for the workspace based on the billing rules regardless of whether you run deployments on the workspace. If you do not run deployments on the workspace, you are still charged for 2 CUs that are used as management resources.