Why Is Error Invalid OBS Bucket Name Reported After a Flink Job Submission Failed?
Symptom
The storage path of the Flink Jar job checkpoints was set to an OBS bucket. The job failed to be submitted, and an error message indicating an invalid OBS bucket name was displayed.
For details about how to save checkpoints to OBS, see How Do I Configure Checkpoints for Flink Jar Jobs and Save the Checkpoints to OBS?
Cause Analysis
- Check that the OBS bucket name is correct.
- Check that the AK/SK has the required permission.
- Set the dependency to provided to prevent JAR file conflicts.
- Check that the esdk-obs-java-3.1.3.jar version is used.
- Confirm that the cluster configuration is faulty.
Procedure
- Set the dependency to provided.
- Restart the clusteragent cluster after an upgrade to make the configuration take effect.
- Remove the OBS dependency. Otherwise, the checkpoints cannot be written to OBS.
Flink Jar Jobs FAQs
- How Do I Configure Checkpoints for Flink Jar Jobs and Save the Checkpoints to OBS?
- Can I Upload Configuration Files for Flink Jar Jobs?
- Why Does a Flink Jar Package Conflict Result in Submission Failure?
- Why Does a Flink Jar Job Fail to Access GaussDB(DWS) and a Message Is Displayed Indicating Too Many Client Connections?
- Why Is Error Message "Authentication failed" Displayed During Flink Jar Job Running?
- Why Is Error Invalid OBS Bucket Name Reported After a Flink Job Submission Failed?
- Why Does the Flink Submission Fail Due to Hadoop JAR File Conflict?
- How Do I Connect a Flink jar Job to SASL_SSL?
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbotmore