Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

HDP 3.1 managing ACL access not working in ambari

Solved Go to solution

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

Accepted Solutions
Highlighted

Re: HDP 3.1 managing ACL access not working in ambari

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

1 REPLY 1
Highlighted

Re: HDP 3.1 managing ACL access not working in ambari

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

Don't have an account?
Coming from Hortonworks? Activate your account here