All Products
Search
Document Center

Realtime Compute for Apache Flink:FAQ about job deployment and startup

Last Updated:Dec 10, 2025

This topic provides answers to some frequently asked questions about job deployment and startup.

What do I do if the error message "exceeded quota: resourcequota" appears?

  • Problem description

    The error message appears when a deployment is started.报错

  • Cause

    The deployment fails to be started because the resources of the current queue are insufficient.

  • Solutions

    Reconfigure the resources used for the queue. For more information, see Reconfigure the number of CUs that can be used in a queue. The number of compute units (CUs) that can be used in the queue. The maximum value of this parameter is determined based on the remaining available resources in the namespace. If the available resources in the namespace are insufficient, you can use one of the following methods to adjust the number of resources:

What do I do if the error message "Failed to create the job graph for the job" appears?

  • Problem description

    Failed to create the job graph for the job: 4b12318d861041ccb14d6e32bae9**** (message = 0:0-0:0, Translating the JobGraph for this deployment failed before. Please delete the JobGraph before requesting a new translation.
    Error message: org.apache.flink.table.sqlserver.api.utils.FlinkSQLException: Session '7beccb7bcc161704b285974e0ae93957' does not exist.
        at org.apache.flink.table.sqlserver.session.SessionManager.getSession(SessionManager.java:121)
        at org.apache.flink.table.sqlserver.FlinkSqlServiceImpl.configureSession(FlinkSqlServiceImpl.java:312)
        at org.apache.flink.table.sqlserver.FlinkSqlServiceImpl.configureSession(FlinkSqlServiceImpl.java:299)
        at org.apache.flink.table.sqlserver.proto.FlinkSqlServiceGrpc$MethodHandlers.invoke(FlinkSqlServiceGrpc.java:3187)
        at io.grpc.stub.ServerCalls$UnaryServerCallHandler$UnaryServerCallListener.onHalfClose(ServerCalls.java:172)
        at io.grpc.internal.ServerCallImpl$ServerStreamListenerImpl.halfClosed(ServerCallImpl.java:331)
        at io.grpc.internal.ServerImpl$JumpToApplicationThreadServerStreamListener$1HalfClosed.runInContext(ServerImpl.java:820)
        at io.grpc.internal.ContextRunnable.run(ContextRunnable.java:37)
        at io.grpc.internal.SerializingExecutor.run(SerializingExecutor.java:123)
  • Cause

    The custom connector is not uploaded to Object Storage Service (OSS).

  • Solution

    Upload the custom connector to OSS to make the deployment run as expected. For more information, see Manage custom connectors.

What do I do if the error message "Job was submitted in detached mode. Results of job execution, such as accumulators, runtime, etc. are not available." appears?

  • Problem description

    Caused by: org.apache.flink.api.common.InvalidProgramException: Job was submitted in detached mode. Results of job execution, such as accumulators, runtime, etc. are not available. Please make sure your program doesn't call an eager execution function [collect, print, printToErr, count].
  • Cause

    The Table API JAR deployment whose code ends with an operator, such as Collect, Print, PrintToErr, or Count, in detached mode.

  • Solutions

    • Create an SQL deployment that has the same configuration as the Table API JAR deployment.

    • Publish a Table API JAR deployment whose code does not end with an operator, such as Collect, Print, PrintToErr, or Count, in detached mode.

What do I do if the error message "Http failure response for https://vvp.console.aliyun.com/xxxx/artifacts:download?filename=xxxx.jar: 500 OK" appears?

  • Problem description

    The JAR deployment fails to be started.

    When I start a deployment, the service fails to respond and the error message "Http failure response for https://vvp.console.aliyun.com/artifacts/v1/namespaces/xxxx/artifacts:download?filename=xxxxxxxx.jar: 500 OK" appears.

  • Cause

    Objects in OSS are in the frozen state or have compliance issues.

  • Solution

    Locate the error in the Message Center console and perform the operations that are described in Solutions in the OSS console to troubleshoot this issue.