###YARN ONLY: Container-executor Error Codes
The following table applies to the container-executor in YARN.
https://github.com/apache/hadoop/blob/b46cd315f7c81cfd89be40f1edacaf9a11282e15/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/native/container-executor/impl/container-executor.h

Numeric | Code Name  | Description
--------| ---------- | -----------
1 | INVALID_ARGUMENT_NUMBER | Incorrect number of arguments provided for the given task-controller command Failure to initialize the container localizer
2 | INVALID_USER_NAME | The user passed to the task-controller does not exist.
3 | INVALID_COMMAND_PROVIDED | The container-executor does not recognize the command it was asked to execute.
5 |INVALID_NM_ROOT |The passed NodeManager root does not match the configured NodeManager root (yarn.nodemanager.local-dirs), or does not exist.
6 |SETUID_OPER_FAILED| Either could not read the local groups database, or could not set UID or GID
7 | UNABLE_TO_EXECUTE_CONTAINER_SCRIPT | The container-executor could not execute the container launcher script.
8 | UNABLE_TO_SIGNAL_CONTAINER | The container-executor could not signal the container it was passed.
9| INVALID_CONTAINER_PID |The PID passed to the container-executor was negative or 0.
18 |OUT_OF_MEMORY |The container-executor couldn't allocate enough memory while reading the container-executor.cfg file, or while getting the paths for the container launcher script or credentials files.
20 |INITIALIZE_USER_FAILED |Couldn't get, stat, or secure the per-user node manager directory.
21 |UNABLE_TO_BUILD_PATH |The container-executor couldn't concatenate two paths, most likely because it ran out of memory.
22 |INVALID_CONTAINER_EXEC_PERMISSIONS |The container-executor binary does not have the correct permissions set. See Appendix B - Information about Other Hadoop Security Programs.
24 |INVALID_CONFIG_FILE |The container-executor.cfg file is missing, malformed, or has incorrect permissions.
25 |SETSID_OPER_FAILED |Could not set the session ID of the forked container.
26 |WRITE_PIDFILE_FAILED |Failed to write the value of the PID of the launched container to the PID file of the container.
27 | WRITE_CGROUP_FAILED | 
28 | TRAFFIC_CONTROL_EXECUTION_FAILED |
29 | DOCKER_RUN_FAILED |
30 | ERROR_OPENING_DOCKER_FILE |
31 | ERROR_READING_DOCKER_FILE |
32 | FEATURE_DISABLED |
33 | COULD_NOT_CREATE_SCRIPT_COPY |
34 | COULD_NOT_CREATE_CREDENTIALS_FILE |
35 | COULD_NOT_CREATE_WORK_DIRECTORIES |
36 | COULD_NOT_CREATE_APP_LOG_DIRECTORIES |
37 | COULD_NOT_CREATE_TMP_DIRECTORIES |
38 | ERROR_CREATE_CONTAINER_DIRECTORIES_ARGUMENTS |
39 | ERROR_SANITIZING_DOCKER_COMMAND |
255 |Unknown Error |There are several causes for this error. Some common causes are: There are user accounts on your cluster that have a user ID less than the value specified for the min.user.id property in the container-executor.cfg file. The default value is 1000 which is appropriate on Ubuntu systems, but may not be valid for your operating system. For information about setting min.user.id in the container-executor.cfg file, see this step. This error is often caused by previous errors; look earlier in the log file for possible causes.