hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-1539) Queue admin ACLs should NOT be similar to submit-acls w.r.t hierarchy.
Date Fri, 27 Dec 2013 20:03:50 GMT

     [ https://issues.apache.org/jira/browse/YARN-1539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Vinod Kumar Vavilapalli updated YARN-1539:

    Priority: Major  (was: Critical)

Hm.. you are right. I check my notes again and cross-verified in code. The real bug my notes
had was about queue-admins needing acls across the hierarchy to be able to submit jobs.

Irrespective of the operation (submit/kill), if I am a queue-admin for a leaf-queue, I should
be able to simply perform the operation irrespective of my permissions on the parent queue.

Lowering priority given this. Can you please confirm FairScheduler's behaviour w.r.r this?
We should refactoring this to be non-scheduler specific.

> Queue admin ACLs should NOT be similar to submit-acls w.r.t hierarchy.
> ----------------------------------------------------------------------
>                 Key: YARN-1539
>                 URL: https://issues.apache.org/jira/browse/YARN-1539
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Vinod Kumar Vavilapalli
> Today, Queue admin ACLs are similar to submit-acls w.r.t hierarchy in that if one has
to be able to administer a queue, he/she should be an admin of all the queues in the ancestry
- an unnecessary burden.
> This was added in YARN-899 and I believe is wrong semantics as well as implementation.

This message was sent by Atlassian JIRA

View raw message