[ 
https://issues.apache.org/jira/browse/AMBARI-21896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16161088#comment-16161088
 ] 

Hadoop QA commented on AMBARI-21896:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12886386/AMBARI-21896.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 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

    {color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

    {color:red}-1 core tests{color}.  The test build failed in 
[ambari-server|https://builds.apache.org/job/Ambari-trunk-test-patch/12171//artifact/patch-work/testrun_ambari-server.txt]
 

Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/12171//console

This message is automatically generated.

> Ambari should honor permissions specified for dfs.datanode.data.dir.perm when 
> creating datanode dir's
> -----------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-21896
>                 URL: https://issues.apache.org/jira/browse/AMBARI-21896
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.5.1
>         Environment: Ambari 2.5.1
>            Reporter: Sanjeev
>            Assignee: Andrew Onischuk
>            Priority: Minor
>             Fix For: 2.6.0
>
>         Attachments: AMBARI-21896.patch
>
>
> Give this:
> <property> 
> <name>dfs.datanode.data.dir.perm</name> 
> <value>750</value> 
> Ambari reports as changing permission from 750 to 755 on the data dirs: 
> 2017-09-01 16:39:28,877 - Forcefully ensuring existence and permissions of 
> the directory: /hadoop01/data 
> 2017-09-01 16:39:28,878 - Directory['/hadoop01/data'] {'group': 'hadoop', 
> 'cd_access': 'a', 'create_parents': True, 'ignore_failures': True, 'mode': 
> 0755, 'owner': 'hdfs'} 
> 2017-09-01 16:39:28,878 - Changing permission for /hadoop01/data from 750 to 
> 755 
> 2017-09-01 16:39:28,879 - Mount point for directory /hadoop02/data is 
> /hadoop02 
> 2017-09-01 16:39:28,880 - Forcefully ensuring existence and permissions of 
> the directory: /hadoop02/data 
> 2017-09-01 16:39:28,880 - Directory['/hadoop02/data'] {'group': 'hadoop', 
> 'cd_access': 'a', 'create_parents': True, 'ignore_failures': True, 'mode': 
> 0755, 'owner': 'hdfs'} 
> 2017-09-01 16:39:28,880 - Changing permission for /hadoop02/data from 750 to 
> 755 
> 2017-09-01 16:39:28,881 - Mount point for directory /hadoop03/data is 
> /hadoop03 
> 2017-09-01 16:39:28,881 - Forcefully ensuring existence and permissions of 
> the directory: /hadoop03/data 
> 2017-09-01 16:39:28,882 - Directory['/hadoop03/data'] {'group': 'hadoop', 
> 'cd_access': 'a', 'create_parents': True, 'ignore_failures': True, 'mode': 
> 0755, 'owner': 'hdfs'} 
> 2017-09-01 16:39:28,882 - Changing permission for /hadoop03/data from 750 to 
> 755 
> 2017-09-01 16:39:28,882 - Mount point for directory /hadoop04/data is 
> /hadoop04 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to