hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xuan Gong (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-4842) "yarn logs" command should not require the appOwner argument
Date Sat, 07 May 2016 00:44:12 GMT

     [ https://issues.apache.org/jira/browse/YARN-4842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Xuan Gong updated YARN-4842:
----------------------------
    Attachment: YARN-4842.5.patch

> "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: Xuan Gong
>         Attachments: YARN-4842.1.patch, YARN-4842.2.patch, YARN-4842.3.patch, YARN-4842.4.patch,
YARN-4842.5.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)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org


Mime
View raw message