All Products
Search

This Product

    Realtime Compute for Apache Flink:FAQ about activation and billing

    Document Center

    Realtime Compute for Apache Flink:FAQ about activation and billing

    Last Updated:Jul 09, 2024

    This topic provides answers to some frequently asked questions about the activation and billing of Realtime Compute for Apache Flink.

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

    • Description

      After I click Purchase in the management console of Realtime Compute for Apache Flink and click Authorize in RAM on the Authorization Request page, I am not redirected to the Resource Access Management (RAM) console. Manual authorization also fails.

    • Cause

      The AliyunStreamAsiDefaultRole role was manually added to your account before you perform the operation. As a result, the system skips the authorization process in which the role is automatically created and assigned.

    • Solution

      Log on to the RAM console and delete the existing AliyunStreamAsiDefaultRole role. Then, go back to the management console of Realtime Compute for Apache Flink and click Authorize in RAM to complete the authorization.RAM

    What do I do if an access denied error message appears due to insufficient resources?

    • Error details

      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) purchased for the workspace are exhausted.

    • Solution

      Increase the number of available CUs or reduce the resource consumption of deployments in the workspace. For more information, see Reconfigure resources.

    Can I change the billing method of a workspace from subscription to pay-as-you-go and vice versa?

    Yes, you can change the billing method of a workspace from subscription to pay-as-you-go and vice versa. To change the billing method of a workspace, perform the following steps: Log on to the management console of Realtime Compute for Apache Flink, find the workspace whose billing method you want to change, and then click More in the Actions column to choose a billing method. For example, you can choose More > Convert To Subscription Billing Method to use the subscription billing method.

    What are the default billable items when I renew the subscription for a workspace?

    Billable item

    Description

    Management resources

    Management resources are used to deploy a development console for each workspace. Each development console and its components require approximately 2 CUs of management resources.

    Computing resources

    Computing resources are used to run deployments. You are charged based on the subscription or pay-as-you-go billing method. The billing unit is CU.

    Important

    The renewed subscription does not include fees related to supporting 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 the subscription for a workspace?

    Manual renewal and auto-renewal are supported. For more information, see Renewal policy.

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

    If you use a pay-as-you-go workspace, you cannot apply for a refund because you are charged only after you use the workspace. If you no longer need to use the workspace, make sure that the data is backed up or migrated and your business is not affected. Then, find the workspace on the management console of Realtime Compute for Apache Flink and choose More > Release Resources in the Actions column.

    If you use a subscription workspace, you can apply for a refund because you make an upfront payment based on the subscription duration. For information about the refund rules and operations, see Refund policy.

    Am I charged when a workspace fails to be created?

    No, you are not charged when a workspace fails to be created. You can view all deducted fees in your bills. For more information, see View your bills.

    Am I charged when I create a pay-as-you-go workspace but do not run a deployment in the workspace?

    Yes, you are still charged for the management resources (2 CUs) even if you do not run any deployments in the workspace.