[
https://issues.apache.org/jira/browse/YARN-1813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13977956#comment-13977956
]
Hadoop QA commented on YARN-1813:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12641421/YARN-1813.2.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/3608//console
This message is automatically generated.
> Better error message for "yarn logs" when permission denied
> -----------------------------------------------------------
>
> Key: YARN-1813
> URL: https://issues.apache.org/jira/browse/YARN-1813
> Project: Hadoop YARN
> Issue Type: Improvement
> Affects Versions: 2.3.0
> Reporter: Andrew Wang
> Assignee: Tsuyoshi OZAWA
> Priority: Minor
> Attachments: YARN-1813.1.patch, YARN-1813.2.patch, YARN-1813.2.patch
>
>
> I ran some MR jobs as the "hdfs" user, and then forgot to sudo -u when
> grabbing the logs. "yarn logs" prints an error message like the following:
> {noformat}
> [andrew.wang@a2402 ~]$ yarn logs -applicationId application_1394482121761_0010
> 14/03/10 16:05:10 INFO client.RMProxy: Connecting to ResourceManager at
> a2402.halxg.cloudera.com/10.20.212.10:8032
> Logs not available at
> /tmp/logs/andrew.wang/logs/application_1394482121761_0010
> Log aggregation has not completed or is not enabled.
> {noformat}
> It'd be nicer if it said "Permission denied" or "AccessControlException" or
> something like that instead, since that's the real issue.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
