This also becomes an issue when we are running apps as different users as they will need permissions on /user/<username> dir.
I would suggest that in http://docs.cask.co/cdap/current/en/admin-manual/installation/packages.html#hdfs-permissions we add the command to give cdap user ownership of /user/cdap dir. In case of impersonation, every user who can be impersonated will need access to their /user/<username> dir, we should add this information in the impersonation section and add a link to that in the installation section.
John Jackson February 21, 2017 at 12:36 AM
See these pages for where this is specified in our documentation:
In a non-secure cluster with the property hdfs.user set to yarn, we are getting the following error when starting CDAP for the first time.
This happens when the property yarn.app.mapreduce.am.staging-dir is set to /user
We previously only required/documented the yarn user(/user/$hdfs.user).