[YARN-4842] "yarn logs" command should not require the appOwner argument

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.9.0, 3.0.0-alpha1
• Hadoop Flags: Reviewed
• Assignee: Xuan Gong
• Reporter: Ram Venkatesh
• Created: 21/Mar/16 05:36
• Updated: 30/Aug/16 01:04
• Resolved: 10/May/16 05:51

Description

The yarn logs command is among the most common ways to troubleshoot yarn app failures, especially by an admin.

Currently if you run the command as a user different from the job owner, the command will fail with a subtle message that it could not find the app under the running user's name. This can be confusing especially to new admins.

We can figure out the job owner from the app report returned by the RM or the AHS, or, by looking for the app directory using a glob pattern, so in most cases this error can be avoided.

Question - are there scenarios where users will still need to specify the -appOwner option?

Issue Links

• depends upon: YARN-4905 Improve "yarn logs" command-line to optionally show log metadata also
• is depended upon by: YARN-4913 Yarn logs should take a -out option to write to a directory