@Kshitij Badani - If the user's home directory is encrypted, the user will not be able to delete the file if its not inside its home folder, unless it uses the "-skipTrash" option. The user should be able to the delete file with "-skipTrash" option. The problem is that the trash directory for non-encrypted data resides in the user's home directory. Now if user's home is encrypted, un-encrypted data cannot be renamed to this directory, and therefore delete will fail unless used with "-skipTrash". The trash directory which is in user's home directory, is to ensure quota is correctly calculated and assigned for deleted data. And moving un-encrypted data to EZ is not allowed for security reasons. If user is encrypting it's home directory, they have to use "-skipTrash" to delete un-encrypted data. Another way to look at it is following: A user who has its home in an EZ should never be creating any important data that is un-encrypted. Please note that deleting encrypted data doesn't have this issue because for encrypted data the trash is within the EZ itself. Let me know if you have any more doubts. Thanks! ... View more

Hello @ssathish, Can you please share the value of hadoop.kms.blacklist.DECRYPT_EEK from /etc/ranger/kms/conf/dbks-site.xml Looks like the user 'hdfs' might be blacklisted. ... View more

@Raghav Kumar Gautam As from the logs you can see you need to set the dfs.namenode.accesstime.precision value to 3600000. The property dfs.access.time.precision is deprecated. Ambari sets the new one dfs.namenode.accesstime.precision to 0, which disables setting access time. So, setting the new property should resolve the issue. ... View more