[jira] [Commented] (YARN-4842) yarn logs command should not require the appOwner argument

["Xuan Gong (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/YARN-4842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15256815#comment-15256815 ] 

Xuan Gong commented on YARN-4842:
---------------------------------

Thanks for the review. Vinod.
The patch addressed all the latest comments.

I have added more testcases:
1. The previous testcases can verify that we can get app logs if the appowner is not specified.
2. Added a new testcase to verify that we can not get app logs if we specify an invalid appOwner
3. Added a new testcase to verify that we can get app logs if we can not get appReport

> yarn logs command should not require the appOwner argument
> ----------------------------------------------------------
>
>                 Key: YARN-4842
>                 URL: https://issues.apache.org/jira/browse/YARN-4842
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Ram Venkatesh
>            Assignee: Ram Venkatesh
>         Attachments: YARN-4842.1.patch, YARN-4842.2.patch, YARN-4842.3.patch
>
>
> 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?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)