[YARN-7961] Improve status response when yarn application is destroyed

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.1.0
• Fix Version/s: 3.2.0, 3.1.1
• Component/s: yarn-native-services
• Target Version/s: 3.2.0, 3.1.1
• Assignee: Gour Saha
• Reporter: Yesha Vora
• Created: 22/Feb/18 18:13
• Updated: 03/May/18 17:51
• Resolved: 03/May/18 17:30

Description

Yarn should provide some way to figure out if yarn service is destroyed.

If yarn service application is stopped, "yarn app -status <appname>" shows that service is Stopped.

After destroying yarn service, "yarn app -status <appname>" returns 404

[hdpuser@cn005 sleeper]$ yarn app -status yesha-sleeper

WARNING: YARN_LOG_DIR has been replaced by HADOOP_LOG_DIR. Using value of YARN_LOG_DIR.

WARNING: YARN_LOGFILE has been replaced by HADOOP_LOGFILE. Using value of YARN_LOGFILE.

WARNING: YARN_PID_DIR has been replaced by HADOOP_PID_DIR. Using value of YARN_PID_DIR.

WARNING: YARN_OPTS has been replaced by HADOOP_OPTS. Using value of YARN_OPTS.

18/02/16 11:02:30 WARN util.NativeCodeLoader: Unable to load native-hadoop library for your platform... using builtin-java classes where applicable

18/02/16 11:02:31 INFO client.RMProxy: Connecting to ResourceManager at xxx/xx.xx.xx.xx:8050

18/02/16 11:02:31 INFO client.AHSProxy: Connecting to Application History server at xxx/xx.xx.xx.x:10200

18/02/16 11:02:31 INFO client.RMProxy: Connecting to ResourceManager at xxx/xx.xx.xx.x:8050

18/02/16 11:02:31 INFO client.AHSProxy: Connecting to Application History server at xxx/xx.xx.xx.x:10200

18/02/16 11:02:31 INFO util.log: Logging initialized @2075ms

yesha-sleeper Failed : HTTP error code : 404

Yarn should be able to notify user that whether a certain app is destroyed or never created. HTTP 404 error does not explicitly provide information.