Support Questions
Find answers, ask questions, and share your expertise
Announcements
Check out our newest addition to the community, the Cloudera Innovation Accelerator group hub.

HDP 3.1 managing ACL access not working in ambari

New Contributor

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?

1 ACCEPTED SOLUTION

Super Collaborator

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

View solution in original post

1 REPLY 1

Super Collaborator

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