[
https://issues.apache.org/jira/browse/AMBARI-16735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15289164#comment-15289164
]
Hadoop QA commented on AMBARI-16735:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12804681/AMBARI-16735.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/6880//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/6880//console
This message is automatically generated.
> 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)
