Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]
Created on 07-06-2015 04:38 AM - edited 09-16-2022 02:33 AM
Hi All ,
I am facing issue while enabling the acl, As per the CDH document for enabling the ACL we need to set acl enable to true.
<property>
<name>dfs.namenode.acls.enabled</name>
<value>true</value>
</property>
I have updated the same in below hdfs-site.xml files, post enabling the ACL, I restart the namenode service from CDH console.
/etc/hadoop/conf.cloudera.hdfs/hdfs-site.xml
/etc/hadoop/conf/hdfs-site.xml
While setting the ACL for a directory I am getting the below error.
" setfacl: The ACL operation has been rejected. Support for ACLs has been disabled by setting dfs.namenode.acls.enabled to false"
And please let me know in which hdfs-site.xml I should enable the acl in the below location I could see the hdfs-site.xml files.
/etc/hadoop/conf/hdfs-site.xml
/etc/hive/conf.cloudera.hive/hdfs-site.xml
/etc/hadoop/conf.cloudera.hdfs/hdfs-site.xml
/etc/hadoop/conf.cloudera.yarn/hdfs-site.xml
/var/run/cloudera-scm-agent/process/49-hdfs-NAMENODE/hdfs-site.xml
/var/run/cloudera-scm-agent/process/45-hdfs-SECONDARYNAMENODE/hdfs-site.xml
Please let know the appropriate file for enabling the ACL.
Thanks
Created 07-06-2015 05:15 AM
Created 07-06-2015 05:15 AM
Created 07-07-2015 06:36 AM
Gautham,
Thanks a lot,
Created 11-16-2015 11:05 PM
I changed hdfs-site.xml under /etc/hadoop/ and restarted name-node. However, I don't see the acl-edit RPC are accepted.
hdfs@qa-node109:/root$ hdfs dfs -setfacl -m user:priv:rw- /testfile
setfacl: The ACL operation has been rejected. Support for ACLs has been disabled by setting dfs.namenode.acls.enabled to false.
What did I miss here?
Created 11-16-2015 11:06 PM