Job deployment and startup

• Error: "exceeded quota: resourcequota"

• Error: "Failed to create the job graph for the job"

• Error: "Job was submitted in detached mode. Results of job execution, such as accumulators, runtime, etc. are not available."

• Error: "Http failure response for https://vvp.console.aliyun.com/xxxx/artifacts:download?filename=xxxx.jar: 500 OK"

Error: "exceeded quota: resourcequota"

• Problem

  A deployment fails to start. On the Running Events tab, the event list shows the following Kubernetes warning event: Abnormal event detected from kubernetes (type:[Warning], reason:[FailedCreate], message:[Error creating: pods "job-6xxx" is forbidden: exceeded quota: resourcequota, requested: limits.cpu=1, used: limits.cpu=15, limited: limits.cpu=15]). This error indicates that pod creation failed. The pod requested 1 CPU core, but the namespace had already reached its 15-core limit.

• Cause

  The deployment fails because the queue has insufficient resources.

• Solution

  Adjust the resources for the target queue. For more information, see Modify resource amount. The maximum configurable resources depend on the available resources in the namespace. If the namespace has insufficient resources, use one of the following methods:

  • Adjust the resources of other queues. For more information, see Modify resource amount.

  • Scale up the resources for the namespace. For more information, see Resource adjustment.

Error: "Failed to create the job graph for the job"

• Problem

  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 has not been uploaded to OSS.

• Solution

  Upload the custom connector to OSS. For more information, see Manage custom connectors.

Error: "Job was submitted in detached mode"

• Problem

  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 ends with a sink operator such as Collect, Print, PrintToErr, or Count.

• Solution

  • Use an SQL deployment.

  • Ensure that the Table API JAR deployment does not end with a sink operator such as Collect, Print, PrintToErr, or Count.

Error: "HTTP 500 error on artifact download"

• Problem

  A JAR deployment fails to start, and the service returns an HTTP 500 error.

• Cause

  The JAR deployment fails to start because the object in OSS is frozen or has compliance violations.

• Solution

  Troubleshoot the issue and unfreeze the object. For detailed instructions, see Solutions.