hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zhijie Shen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-2390) Investigating whehther generic history service needs to support queue-acls
Date Thu, 14 Aug 2014 19:02:12 GMT

    [ https://issues.apache.org/jira/browse/YARN-2390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14097385#comment-14097385

Zhijie Shen commented on YARN-2390:

bq. but completed apps can be there in RM for some more time (10000 is default number of completed
apps in RM). and ACL's will be applicable for these completed apps still. 

[~sunilg], that's a good point. I agree it would be nice if RM and GHS have consistent access
control for finished application. However, if it's reasonable that the queue admin shouldn't
have the access to the complete app which is removed from the queue, is the right fix to be
correcting the ACLs on RM side?

One related issue is that while CLI will check the user's ACLs properly, neither GET APIs
nor web UI honor the ACLs completely at RM side (therefore, I filed YARN-2310 and YARN-2311

> Investigating whehther generic history service needs to support queue-acls
> --------------------------------------------------------------------------
>                 Key: YARN-2390
>                 URL: https://issues.apache.org/jira/browse/YARN-2390
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Zhijie Shen
> According YARN-1250,  it's arguable whether queue-acls should be applied to the generic
history service as well, because the queue admin may not need the access to the completed
application that is removed from the queue. Create this ticket to tackle the discussion around.

This message was sent by Atlassian JIRA

View raw message