Help Center>
Data Lake Insight>
FAQs>
Flink Jobs>
O&M Guide>
Why Is the OBS Bucket Selected for Job Not Authorized?
Updated on 2023-05-19 GMT+08:00
Why Is the OBS Bucket Selected for Job Not Authorized?
If the OBS bucket selected for a job is not authorized, perform the following steps:
- On the DLI management console, choose Global Configuration > Service Authorization and select the Tenant Administrator (Global service) permission. Update the permission settings.
- In the navigation pane, choose .
- In the row where the target job resides, click Edit under to switch to the page.
- Configure parameters under
on the page.
- Select Enable Checkpointing or Save Job Log.
- Specify .
- Select Authorize OBS.
Parent topic: O&M Guide
O&M Guide FAQs
- How Do I Locate a Flink Job Submission Error?
- How Do I Locate a Flink Job Running Error?
- How Do I Know Whether a Flink Job Can Be Restored from a Checkpoint After Being Restarted?
- Why Does DIS Stream Not Exist During Job Semantic Check?
- Why Is the OBS Bucket Selected for Job Not Authorized?
- Why Are Logs Not Written to the OBS Bucket After a DLI Flink Job Fails to Be Submitted for Running?
- How Do I Configure Connection Retries for Kafka Sink If it is Disconnected?
- Why Is Information Displayed on the FlinkUI/Spark UI Page Incomplete?
- Why Is the Flink Job Abnormal Due to Heartbeat Timeout Between JobManager and TaskManager?
- Why Is Error "Timeout expired while fetching topic metadata" Repeatedly Reported in Flink JobManager Logs?
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
The system is busy. Please try again later.
more