Realtime Compute for Apache Flink:Workspace and namespace FAQ

Can I change the name of a workspace?

1. In the Realtime Compute for Apache Flink console, click Details in the Actions column of the target workspace.

2. Click the workspace name to edit it.

Can I change the VPC and vSwitch?

You cannot change the VPC, but you can change the vSwitch.

How do I view information such as the workspace ID?

In the Realtime Compute for Apache Flink console, click Details in the Actions column of the target workspace.

Resource allocation fails during a project scale-in

Cause: All resources are already allocated or in use.

Solution: Reduce the resources allocated to the resource queue first. For details, see Modify the resource amount. Then scale in the project.

A Flink compute resource upgrade has no effect

The behavior depends on your billing method.

• Subscription Resources must be scaled from the top down: workspace → projects → resource queues. For details, see Resource adjustment.

  

• Pay-as-you-go Pay-as-you-go is a postpaid billing method. The system settles your bill based on actual resource usage, so resource scaling is not required. To configure resource queues for isolation and management in batch job scenarios, go to the Actions column of the target workspace and click More > Quota Limit. For details, see Manage resource queues.

How do I view the AccessKey ID and AccessKey secret?

• AccessKey ID

  • For an Alibaba Cloud account: Log on to the Alibaba Cloud Management Console, move the pointer over your profile picture in the upper-right corner, and click AccessKey Management.

  • For a RAM user: See View the AccessKey information of a RAM user.

• AccessKey secret The AccessKey secret is displayed only when you create it and cannot be retrieved later. Store it in a secure location immediately after creation.

If you have lost your AccessKey information, see Create an AccessKey.

How do I upload a file to OSS for a Flink job to use?

If you selected OSS bucket as the storage class when creating the Flink workspace, upload the file to the OSS bucket attached to the workspace. You can also manage files directly on the File Management page of the Realtime Compute for Apache Flink development console. For details, see Manage files.

1. In the Realtime Compute for Apache Flink console, find the target workspace and choose More > Workspace Details in the Actions column to view the attached OSS bucket information.

   

2. Upload the resource file to the target OSS bucket.

   • Log in to the OSS console and upload the file to the /artifacts/namespaces directory in the bucket.

   • Alternatively, upload the file by calling the PutObject API operation.

3. In the navigation pane of the Realtime Compute for Apache Flink development console, click File Management to verify that the uploaded file appears.

   

What do I do if an activated Flink workspace is not displayed in the Realtime Compute for Apache Flink console?

Check the following items. If the issue persists, submit a ticket.

• Confirm that the workspace has finished initializing. This process typically takes 5 to 10 minutes.

• Make sure you have selected the correct region at the top of the console. A workspace is only visible in the region where it was created.

  

• If you are logged in as a RAM user, make sure the user has the required permissions for the Realtime Compute for Apache Flink console. For details, see Permission management.

Error: "Has not enough ip address: abnormal event detected from kubernetes"

Has not enough ip address:abnormal event detected from kubernetes (type:[Warning], reason:[CniError_CodeUnKnownErr], message:[CniAllocateError: allocateIP failed: ipamCreate failed: failed to create ENI: all vSwitches ([*****]) cannot be used: CreateNetworkInterface: RequestId: 67959AE5-EA20-5CB4-8560-5BD6752472FD, ErrorCode: InvalidVSwitchId.IpNotEnough, Message: The specified VSwitch "*****" has not enough IpAddress., elapsedTime: 245.03232ms])

Cause: The error code InvalidVSwitchId.IpNotEnough indicates that the vSwitch has no available IP addresses.

Solution: Add available IP addresses to the vSwitch. For details, see Modify a vSwitch.

Error: "Unknown Error: Http failure response for xxxxx"

File upload fails with the following error:

Cause: After the Alibaba Cloud International site domain name was updated, file upload requests to the new alibabacloud.com domain fail due to cross-origin restrictions if you have not configured a Cross-Origin Resource Sharing (CORS) rule in Object Storage Service (OSS).

Solution: Configure a CORS rule in the OSS console for the OSS bucket attached to your Flink workspace. For details, see Manage files.

How do I view the Flink version of the current job?

Two ways to check:

• On the ETL or Data Ingestion page, click More Configurations on the right side and find the version in the Engine Version field.

  

• On the Operation Center > Job O&M page, click the job name and view the version in the Basic Configuration area on the Deployment Details tab.

  

How do I change the engine version for a Realtime Compute for Apache Flink job?

The steps differ by job type.

• SQL or YAML jobs On the ETL or Data Ingestion page, click More Configurations on the right side and select the target version from the Engine Version field. For a deployed job, redeploy and start it for the change to take effect.

• JAR or Python jobs On the Job O&M page, click the job name. On the Deployment Details tab, click Edit in the upper-right corner of the Basic Configuration section. Select the target version in the Engine Version field, click Save, and then click Start.

How do I configure custom running parameters for a job?

1. Log on to the Realtime Compute for Apache Flink console.

2. Find the workspace and click Console in the Actions column.

3. On the Job O&M page, click the job name.

4. On the Deployment Details tab, click Edit to the right of the Running Parameter Settings section.

5. In the Other Configuration field, enter the parameters. A space must follow the colon (:) between the key and value. For example:

   task.cancellation.timeout: 180s

6. Click Save.

How do I persist common Flink configurations to improve efficiency?

Use the Job Template feature to save common parameters as a reusable template, so you do not need to reconfigure them for each new job.

How do I prevent sensitive information such as AccessKey secrets or passwords from being leaked?

Use variables to avoid exposing sensitive values in plaintext. Variables also reduce repetition and simplify configuration management. They work across SQL jobs, JAR or Python jobs, log configurations, and UI settings. For details, see Manage variables.

How can Flink jobs use compute resources more efficiently?

Two options are available.

• Manual adjustment: On the Smart Diagnosis tab, click Start Diagnosis, review the resource analysis results, and adjust as prompted.

  

• Automatic adjustment: Enable the automatic tuning feature, which supports intelligent tuning and scheduled tuning modes. For details on scenarios and configuration, see Configure automatic tuning.

Cron expression syntax

Job state set management uses Unix-style rules, while task orchestration uses Java-style (Quartz) rules. Use the correct syntax for your scenario.

Unix-style rules

1. Fields: minute hour day_of_month month day_of_week — five fields total.

2. OR relationship between day fields: When both the day_of_month field (third) and the day_of_week field (fifth) are set, they form an OR relationship. > 0 12 1 * 5 means the job runs at 12:00 on the first of each month or on every Friday — not only when the first falls on a Friday.

3. The question mark (`?`) is not supported: Use * to ignore a field instead. Using ? causes an error or unrecognized expression.

Java-style rules (Quartz)

1. Fields: second minute hour day_of_month month day_of_week — six fields commonly used.

2. Conflict between day fields:

   • The day_of_month and day_of_week fields cannot both be set to specific values or both set to *.

   • Use ? in one of the two fields to prevent logical conflicts. For example, specifying both "the 1st" and "Friday" creates a conflict when the 1st is not a Friday.

   • Rule: If you set a value for day_of_month, set day_of_week to ?. If you set a value for day_of_week, set day_of_month to ?.

3. Day-of-week numeric values: 1 represents Sunday, 2 represents Monday, and so on. To avoid ambiguity, use English abbreviations such as SUN, MON, and TUE.