Help Center/ Data Lake Insight/ FAQs/ Flink Jobs/ Flink Jar Jobs/ Why Is Error Invalid OBS Bucket Name Reported After a Flink Job Submission Failed?
Updated on 2024-09-29 GMT+08:00
View PDF
Share

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.

Possible Causes

  1. Check that the OBS bucket name is correct.
  2. Check that the AK/SK has the required permission.
  3. Set the dependency to provided to prevent JAR file conflicts.
  4. Check that the esdk-obs-java-3.1.3.jar version is used.
  5. Confirm that the cluster configuration is faulty.

Procedure

  1. Set the dependency to provided.
  2. Restart the clusteragent cluster after an upgrade to make the configuration take effect.
  3. Remove the OBS dependency. Otherwise, the checkpoints cannot be written to OBS.
Parent topic: Flink Jar Jobs