@Anurag Mishra, Run your script as below sh myscript.sh > output.txt 2>&1 Thanks, Aditya ... View more

@Anurag Mishra Can you please share the complete error that you are getting? Also little detail about what your script is doing? It might be the HDFS directory where the user "yarn" is trying to write and does not have write permission. If that is the case then you might want to give write permission to the "yarn" user to that HDFS directory. # su - hdfs -c "hdfs dfs -chmod 777 /PATH/WHERE/YARN/USER/IS/WRITING (OR) # su - hdfs -c "hdfs dfs -chown -R yarn:hadoop /PATH/WHERE/YARN/USER/IS/WRITING . ... View more

@Anurag Mishra - You will need to pass all the previous user privilege details as well along with the new user when you want to edit the list using API call: Example if you already have users privilleges for "123jay", "jay". Now you want to add another user "jayyarn" in the privilleges list then you should PUT the whole list again. Example: curl -i -u $Ambariadmin:$ambaripass -H "X-Requested-By: ambari" -X PUT -d '[{"PrivilegeInfo":{"permission_name":"VIEW.USER","principal_name":"123jay","principal_type":"USER"}},{"PrivilegeInfo":{"permission_name":"VIEW.USER","principal_name":"jay","principal_type":"USER"}},{"PrivilegeInfo":{"permission_name":"VIEW.USER","principal_name":"jayyarn","principal_type":"USER"}},{"PrivilegeInfo":{"permission_name":"VIEW.USER","principal_name":"CLUSTER.ADMINISTRATOR","principal_type":"ROLE"}},{"PrivilegeInfo":{"permission_name":"VIEW.USER","principal_name":"CLUSTER.OPERATOR","principal_type":"ROLE"}},{"PrivilegeInfo":{"permission_name":"VIEW.USER","principal_name":"SERVICE.OPERATOR","principal_type":"ROLE"}},{"PrivilegeInfo":{"permission_name":"VIEW.USER","principal_name":"SERVICE.ADMINISTRATOR","principal_type":"ROLE"}},{"PrivilegeInfo":{"permission_name":"VIEW.USER","principal_name":"CLUSTER.USER","principal_type":"ROLE"}}]' http://localhost:8080/api/v1/views/$viewname/versions/$version/instances/$instance/privileges . ... View more

@Anurag Mishra You should use extra single quotes as "'${password}'" and "'${username}'" Notice: "'${password}'" And "'${username}'" Example: # export username=test112233 # export password=test112233_password # export Ambariuser=admin # export ambaripass=admin # curl -iv -u $Ambariuser:$ambaripass -H "X-Requested-By: ambari" -X POST -d '{"Users/user_name":"'${username}'","Users/password":"'${password}'","Users/active":"true","Users/admin":"false"}' http://localhost:8080/api/v1/users . Output: . ... View more

@Anurag Mishra Hi You can use the following properties: Note: These settings can be accessed from Ambari > YARN > Configs > Scheduler or in conf/capacity-scheduler.xml. --1. For adding users who can submit jobs <property> <name>yarn.scheduler.capacity.root.test.acl_submit_applications</name> <value>user1 group1, user2, user3 group 2</value> <description> The ACL of who can submit jobs to the test queue. </description> </property> --2. For administering a queue <property> <name>yarn.scheduler.capacity.root.test.acl_administer_queue</name> <value>user5 group5</value> <description> The ACL of who can administer jobs on the test queue.</description> </property> ... View more

Hi @Anurag Mishra, If you want to change yarn-site.xml in the server, then it is also fine. But you need to restart the services on your own instead of using ambari .(if you use ambari to restart services, then as mentioned by Jay, your changes will get wiped off) WARNING : It so happens, that for some properties in yarn-site.xml, it requires restart of more than one service , in which case, you need to copy the change in all service nodes and restart them. ADVANTAGE OF AMABRI - In case of ambari, its just one point change, it will figure out which services require that change and suggest restart of all the services required. ... View more