This topic provides answers to some frequently asked questions about SQL of fully managed Flink, including errors returned during job development and job O&M.
- Errors returned during job development
- Errors returned during job O&M
- What do I do if the error message "exceeded quota: resourcequota" appears?
- What do I do if the error message "Exceeded checkpoint tolerable failure threshold" appears?
- What do I do if the error message "Flink version null is not configured for sql" appears?
- What do I do if the error message "java.util.concurrent.CompletionException: java.lang.IllegalArgumentException" appears?
- What do I do if the error massage "The difference between the request time and the current time is too large" appears?
- What do I do if the error message "INFO: org.apache.flink.fs.osshadoop.shaded.com.aliyun.oss" appears?
What do I do if the error message "undefined" appears?
- Error details
- Cause
The size of your JAR package exceeds the allowed size.
- Solution
You can upload the JAR package in the OSS console. For more information, see How do I upload a JAR package in the Object Storage Service (OSS) console?.
What do I do if the error message "Object '****' not found" appears?
- Error details
After you click Run, the error message shown in the following figure appears.
- Cause
When you execute DDL and DML statements in the same text, you do not declare CREATE TEMPORARY TABLE in the DDL statement.
- Solution
When you execute DDL and DML statements in the same text, you must declare CREATE TEMPORARY TABLE instead of CREATE TABLE in the DDL statement.
What do I do if the error message "Only a single 'INSERT INTO' is supported" appears?
- Error details
After you click Run, the error message shown in the following figure appears.
- Cause
Multiple DML statements are not written between the key statements
BEGIN STATEMENT SET;
andEND;
. - Solution
Write the DML statements between
BEGIN STATEMENT SET;
andEND;
. For more information, see INSERT INTO statement.
What do I do if the error message "exceeded quota: resourcequota" appears?
- Error details
The error message appears when a job is started.
- Cause
The job fails to be started because the resources of the current project are insufficient.
- Solution
You must reconfigure the project resources. For more information, see Create and manage a project.
What do I do if the error message "Exceeded checkpoint tolerable failure threshold" appears?
- Error details
The error message appears when a job is running.
- Cause
The maximum number of checkpoint failures allowed in a task is not specified. By default, a failover is triggered each time a checkpoint fails.
- Solution
- On the right side of the Draft Editor page in the console of fully managed Flink, click the Advanced tab.
- In the Additional Configuration section, enter the following parameter:
You must replace num with the number of checkpoint failures that you allow in the task. This parameter must be set to 0 or a positive integer. If the parameter is set to 0, no checkpoint exceptions or failures are allowed.execution.checkpointing.tolerable-failed-checkpoints: num
What do I do if the error message "Flink version null is not configured for sql" appears?
- Error details
StatusRuntimeException: INTERNAL: Flink version null is not configured for sql.
- Cause
The system is updated to VVR 4.0.8. As a result, the version information about the Flink computing engine of the job cannot be obtained.
- Solution
On the right side of the Draft Editor page, click the Advanced tab and select the required version from the Engine Version drop-down list in the Configuration section.Note If you need to use the SQL preview feature, you must check whether the engine version that you selected on the Create Session Cluster page is correct.
What do I do if the error message "java.util.concurrent.CompletionException: java.lang.IllegalArgumentException" appears?
- Error details
Caused by: java.util.concurrent.CompletionException: java.lang.IllegalArgumentException: The bucket name "fakeBucket" is invalid. A bucket name must: 1) be comprised of lower-case characters, numbers or dash(-); 2) start with lower case or numbers; 3) be between 3-63 characters long.
- Cause
In the Additional Configuration section of the Advanced tab, the state.backend parameter is configured but the state.checkpoints.dir parameter is not configured.
- Solution
If you configure the state.backend parameter, you must configure the state.checkpoints.dir parameter.Note You can also delete the state.backend parameter.
What do I do if the error massage "The difference between the request time and the current time is too large" appears?
- Error details
Caused by: org.apache.flink.fs.osshadoop.shaded.com.aliyun.oss.OSSException: The difference between the request time and the current time is too large. [ErrorCode]: RequestTimeTooSkewed [RequestId]: 61691C47AF60CA3639812A28 [HostId]: oss-bucket-name.oss-cn-shanghai-internal.aliyuncs.com [ResponseError]: <?xml version="1.0" encoding="UTF-8"?> <Error> <Code>RequestTimeTooSkewed</Code> <Message>The difference between the request time and the current time is too large.</Message> <RequestId>61691C47AF60C******12A28</RequestId> <HostId>******.oss-cn-shanghai-internal.aliyuncs.com</HostId> <MaxAllowedSkewMilliseconds>900000</MaxAllowedSkewMilliseconds> <RequestTime>2021-10-15T05:57:31.000Z</RequestTime> <ServerTime>2021-10-15T06:14:31.000Z</ServerTime> </Error> at org.apache.flink.fs.osshadoop.shaded.com.aliyun.oss.common.utils.ExceptionFactory.createOSSException(ExceptionFactory.java:100) ~[?:?] at org.apache.flink.fs.osshadoop.shaded.com.aliyun.oss.internal.OSSErrorResponseHandler.handle(OSSErrorResponseHandler.java:70) ~[?:?] at org.apache.flink.fs.osshadoop.shaded.com.aliyun.oss.common.comm.ServiceClient.handleResponse(ServiceClient.java:257) ~[?:?] at org.apache.flink.fs.osshadoop.shaded.com.aliyun.oss.common.comm.ServiceClient.sendRequestImpl(ServiceClient.java:140) ~[?:?] at org.apache.flink.fs.osshadoop.shaded.com.aliyun.oss.common.comm.ServiceClient.sendRequest(ServiceClient.java:70) ~[?:?] at org.apache.flink.fs.osshadoop.shaded.com.aliyun.oss.internal.OSSOperation.send(OSSOperation.java:83) ~[?:?] at org.apache.flink.fs.osshadoop.shaded.com.aliyun.oss.internal.OSSOperation.doOperation(OSSOperation.java:145) ~[?:?] at org.apache.flink.fs.osshadoop.shaded.com.aliyun.oss.internal.OSSOperation.doOperation(OSSOperation.java:102) ~[?:?] at org.apache.flink.fs.osshadoop.shaded.com.aliyun.oss.internal.OSSBucketOperation.listObjects(OSSBucketOperation.java:411) ~[?:?] at org.apache.flink.fs.osshadoop.shaded.com.aliyun.oss.OSSClient.listObjects(OSSClient.java:443) ~[?:?] at org.apache.flink.fs.shaded.hadoop3.org.apache.hadoop.fs.aliyun.oss.AliyunOSSFileSystemStore.listObjects(AliyunOSSFileSystemStore.java:506) ~[?:?] at org.apache.flink.fs.shaded.hadoop3.org.apache.hadoop.fs.aliyun.oss.AliyunOSSFileSystem.getFileStatus(AliyunOSSFileSystem.java:264) ~[?:?] at org.apache.flink.fs.shaded.hadoop3.org.apache.hadoop.fs.aliyun.oss.AliyunOSSFileSystem.validatePath(AliyunOSSFileSystem.java:548) ~[?:?] at org.apache.flink.fs.shaded.hadoop3.org.apache.hadoop.fs.aliyun.oss.AliyunOSSFileSystem.mkdirs(AliyunOSSFileSystem.java:532) ~[?:?] at org.apache.flink.fs.shaded.hadoop3.org.apache.hadoop.fs.FileSystem.mkdirs(FileSystem.java:2326) ~[?:?] at org.apache.flink.fs.osshadoop.common.HadoopFileSystem.mkdirs(HadoopFileSystem.java:196) ~[?:?]
- Cause
The versioning feature is enabled for OSS buckets but the lifecycle rules are not configured to periodically remove the delete markers and unnecessary historical versions of objects. If a large number of delete markers exists, the LIST operation may slow down and the job may fail to start. For more information, see Usage notes.
- Solution
You can configure lifecycle rules for a bucket in the OSS console to periodically remove the delete markers and unnecessary historical versions of objects. For more information, see Configure lifecycle rules to manage object versions.
What do I do if the error message "INFO: org.apache.flink.fs.osshadoop.shaded.com.aliyun.oss" appears?
- Error details
- Cause
When OSS creates a directory, OSS checks whether the directory exists. If the directory does not exist, the error message "INFO: org.apache.flink.fs.osshadoop.shaded.com.aliyun.oss" appears. Flink jobs are not affected.
- Solution
Add
<Logger level="ERROR" name="org.apache.flink.fs.osshadoop.shaded.com.aliyun.oss"/>
to the log template. For more information, see Configure job logging.