本文为您介绍作业部署与启动有关的常见问题。
报错:exceeded quota: resourcequota
报错:Failed to create the job graph for the job
报错详情
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)
报错原因
自定义的连接器没有上传到OSS上。
解决方案
将自定义连接器上传到OSS,使作业正常运行,详情请参见管理自定义连接器。
报错:Job was submitted in detached mode. Results of job execution, such as accumulators, runtime, etc. are not available.
报错详情
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].
报错原因
TableAPI JAR作业以Collect、Print、PrintToErr或Count等Operator作结尾了。
解决方案
使用SQL作业运行。
TableAPI JAR作业不要以Collect、Print、PrintToErr或Count等Operator作结尾。
报错:Http failure response for https://vvp.console.aliyun.com/xxxx/artifacts:download?filename=xxxx.jar: 500 OK
报错详情
JAR任务启动失败,详情如下。
报错原因
OSS文件冻结或文件存在违法违规情况导致JAR任务启动失败。
解决方案
对冻结状态进行排查处理,具体操作请参见解决方案。
文档内容是否对您有帮助?