[
https://issues.apache.org/jira/browse/AMBARI-16735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15289570#comment-15289570
]
Hudson commented on AMBARI-16735:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #4867 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/4867/])
AMBARI-16735. HDFS data disk mount point permissions (aonishuk) (aonishuk:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=3f080663a4b84ddf8cae52fcbf05599114503e1b])
* ambari-agent/src/test/python/resource_management/TestDatanodeHelper.py
*
ambari-common/src/main/python/resource_management/libraries/functions/dfs_datanode_helper.py
> HDFS data disk mount point permissions
> --------------------------------------
>
> Key: AMBARI-16735
> URL: https://issues.apache.org/jira/browse/AMBARI-16735
> Project: Ambari
> Issue Type: Bug
> Reporter: Andrew Onischuk
> Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-16735.patch
>
>
> You can't change the ownership of the datanode data mount points to
> hdfs:hadoop before beginning the installation as the user and group won't
> exist, they're created by the rpm's deployed by ambari.
> You could create the user/group yourself and then set the ownership but that
> kind of defeats the purpose of having ambari and the agents to perform that
> task for you.
> Would be nice if Ambari could chmod dfs.datanode.data.dir during install.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
