[
https://issues.apache.org/jira/browse/YARN-6842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16105280#comment-16105280
]
Sunil G commented on YARN-6842:
-------------------------------
Is this issue in similar line with YARN-6890?
With out jumping into much details, existing UI could be accessed securely with
kerberos and user authentication is done via kerberos or any similar way. YARN
has static user, which could be disabled if you use a secure cluster. In other
cases, this static user will help to do user specific operation. But kiiling
other users app is an issue in kerberized cluster and YARN-6890 is trying to
look into that. Pls check once.
> Implement a new access type for queue
> -------------------------------------
>
> Key: YARN-6842
> URL: https://issues.apache.org/jira/browse/YARN-6842
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: scheduler
> Affects Versions: 2.8.2
> Reporter: YunFan Zhou
> Assignee: YunFan Zhou
> Attachments: YARN-6842.001.patch, YARN-6842.002.patch,
> YARN-6842.003.patch
>
>
> When we want to access applications of a queue, only we can do is become the
> administer of the queue at present.
> But sometimes we only want authorize someone view applications of a queue
> but not modify operation.
> In our current mechanism there isn't any way to meet it, so I will implement
> a new access type for queue to solve
> this problem.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
