[
https://issues.apache.org/jira/browse/YARN-4842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15206429#comment-15206429
]
Junping Du commented on YARN-4842:
----------------------------------
Agree that appOwner is not necessary in most cases. [~xgong], what do you think?
v2 patch looks good in overall. Test failures seems to be unrelated:
TestYarnClient run successfully in local with this patch. TestGetGroups failed
also without applying this patch (first time I saw this, will file issue if we
didn't filed it before). Other failures have been seen many times and I am sure
we have JIRAs to track them.
> 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: Bug
> Reporter: Ram Venkatesh
> Assignee: Ram Venkatesh
> Attachments: YARN-4842.1.patch, YARN-4842.2.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)
