Help Center/ MapReduce Service/ Developer Guide (Normal_Earlier Than 3.x)/ Flink Development Guide/ FAQs About Flink Application Development/ What Should I Do If yarn-session Failed to Be Started When blob.storage.directory Is Set to /home?
Updated on 2024-08-16 GMT+08:00
View PDF
Share

What Should I Do If yarn-session Failed to Be Started When blob.storage.directory Is Set to /home?

Issue

When blob.storage.directory is set to /home, a user has no permission to create the blobStore-UUID file in /home, causing yarn-session start failure.

Answer

  1. It is recommended that blob.storage.directory be set to /tmp or /opt/Bigdata/tmp.
  2. If you set blob.storage.directory to a customized directory, you need to manually assign the owner permission on the directory to the user. The following uses user admin of MRS as an example.
    1. Modify the Flink client configuration file conf/flink-conf.yaml and configure blob.storage.directory to /home/testdir/testdirdir/xxx.
    2. Create the /home/testdir directory (level-1 directory is enough) and assign the directory to user admin.

      The testdirdir/xxx directory in /home/testdir/ is automatically created on each node when the Flink cluster is started.

    3. Go to the client path and run ./bin/yarn-session.sh -n 3 -jm 2048 -tm 3072 to check whether yarn-session is normally started and the directory is created.