- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Float this Question for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
HDP 3.1 managing ACL access not working in ambari
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
There is a really good article in IBM documentation about managing queue access with ACLs
(https://developer.ibm.com/hadoop/2017/06/30/managing-queue-access-acls/)
However when I change the ACL config and add specific group:
yarn.scheduler.capacity.root.default.acl_submit_applications=yarn,ambari-qa,clusterusers
And after I refresh queues with:
$mapred queue -showacls
I get the following output.
Queue acls for user : myuser
Queue Operations
=====================
root
default
My temporal solution was to set:
yarn.scheduler.capacity.root.default.acl_submit_applications=*
Which works (see the output):
Queue acls for user : myuser
Queue Operations
=====================
root
default SUBMIT_APPLICATIONS
Note: myuser is a part of a group clusterusers
I would like to know why this config does not work if I set some groups on my own. Any ideas?
Created ‎10-28-2019 10:03 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If clusterusers is a group then you should have a space separator between users and groups in acl config.
Something like
yarn.scheduler.capacity.root.default.acl_submit_applications=yarn,ambari-qa clusterusers
Created ‎10-28-2019 10:03 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If clusterusers is a group then you should have a space separator between users and groups in acl config.
Something like
yarn.scheduler.capacity.root.default.acl_submit_applications=yarn,ambari-qa clusterusers
