[
https://issues.apache.org/jira/browse/MAPREDUCE-3903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13217360#comment-13217360
]
Thomas Graves commented on MAPREDUCE-3903:
------------------------------------------
So it actually appears we are inconsistent about acls. If you are going
through the web ui for AM or historyserver you get one behavior where it only
checks the job acls, but if you go through the mapred cli which goes through
the RM, it uses yarn acls and application acls. The application acls include
the job acls. Note that when going through the RM it doesn't seem to look at
mapreduce.cluster.acls.enabled at all even through it appends the job acls to
application acls.
> no admin override to view jobs on mr app master and job history server
> ----------------------------------------------------------------------
>
> Key: MAPREDUCE-3903
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3903
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Reporter: Thomas Graves
> Assignee: Thomas Graves
> Priority: Critical
> Fix For: 0.23.0
>
>
> in 1.0 there was a config mapreduce.cluster.administrators that allowed
> administrators to view anyones job. That no longer works on yarn.
> yarn has the new config yarn.admin.acl but it appears the mr app master and
> job history server don't use that.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
