Resolution
To resolve this issue, do one of the following:
-
OneFS 7.2.1.2
- Implement the workaround provided below
-
OneFS 7.2.1.1
- Apply patch-164059 first, and then implement the workaround provided below
Workaround
Implement the following workaround to manually create and use a YARN node label directory that resides on the OneFS cluster rather than the HDFS cluster. Note: If you have ran the isilon_hadoop_tools script on GitHub, you do not need to follow this workaround, as the script automatically creates and permissions the correct directory.
Step 1. Prepare OneFS to store node label information
Perform the following steps on the OneFS cluster.
Note: In the following procedure, HDFS_ROOT_DIR refers to your HDFS root directory on the OneFS cluster.
- Create the new directory on OneFS to host the node label store.
- mkdir -p HDFS_ROOT_DIR/system/yarn/node-labels
- Confirm that the user yarn exists.Note: If you have not already created a user called yarn , create one now. For information on creating users, see the Managing local users and groups section of the Isilon OneFS CLI Administration Guide.
- Make the user yarn the owner of the new directory.
- chown yarn HDFS_ROOT_DIR/system/yarn/node-labels
- Change the permission level of the directory to allow the owner to read, write, and execute.
- chmod 700 HDFS_ROOT_DIR/system/yarn/node-labels
(Optional) Step 2: Direct Apache Hadoop to store node label information on OneFS
Perform the following steps on the HDFS cluster.
- Using a browser, log on to Ambari Manager on your HDFS cluster.
- From the top banner of the Ambari Dashboard, click Services.
- From the left panel, Click YARN.
- Click the Configs tab.
- Click the Settings tab.
- Under YARN Features, confirm node labels are Enabled.
- Click Save.
- Click on the Advanced tab.
- Expand the Advanced yarn-site section.
- In the yarn.node-labels.fs-store.root-dir field, confirm that the default /system/yarn/node-labels is listed.
- Click Save.