[
https://issues.apache.org/jira/browse/TEZ-2922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14987766#comment-14987766
]
Hitesh Shah edited comment on TEZ-2922 at 11/3/15 6:15 PM:
-----------------------------------------------------------
Also, for a long running session, this defines the yarn admins upfront when the
session is started. Even if the admin lists are refreshed on an RM restart, the
AM will continue ( or the new attempt will start) with old configs and
therefore follow different access rules. We can probably just document this but
in the long term, I think we will need a feedback loop from the RM on the
current admin list.
One option could be for YARN RM to send the admin list to the AM via the launch
env and on allocate calls if the admin list is refreshed.
was (Author: hitesh):
Also, for a long running session, this defines the yarn admins upfront when the
session is started. Even if the admin lists are refreshed on an RM restart, the
AM will continue ( or the new attempt will start) with old configs and
therefore follow different access rules. We can probably just document this but
in the long term, I think we will need a feedback loop from the RM on the
current admin list.
One option could be to send the admin list to the AM via the launch env.
> Tez Live UI gives access denied for admins
> ------------------------------------------
>
> Key: TEZ-2922
> URL: https://issues.apache.org/jira/browse/TEZ-2922
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Jonathan Eagles
> Assignee: Jonathan Eagles
> Attachments: TEZ-2292.1.patch, TEZ-2292.2.patch
>
>
> YARN's Timeline Store allow access to Tez DAG history via the yarn.admin.acl
> setting. While live Tez history from AMWebController, neither respects
> yarn.admin.acl nor implements its own like mapreduce via
> mapreduce.cluster.administrators.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
