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

Hadoop QA commented on AMBARI-21692:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12881203/AMBARI-21692.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
                        Please justify why no new tests are needed for this 
patch.
                        Also please list what manual steps were performed to 
verify this patch.

    {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:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-server.

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

This message is automatically generated.

> dfs.include file is created on all datanode hosts when Ambari manages 
> include/exclude files
> -------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-21692
>                 URL: https://issues.apache.org/jira/browse/AMBARI-21692
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-admin
>    Affects Versions: 2.5.2
>            Reporter: Dhanya Balasundaran
>            Assignee: Dmytro Sen
>             Fix For: 2.5.2
>
>         Attachments: AMBARI-21692.patch
>
>
> - deploy cluster with default configs
> - Update manage.include.files to true in hdfs-site.xml
> - Add property dfs.hosts=/etc/hadoop/conf/dfs.include in cstm-hdfs-site.xml
> - Create /etc/hadoop/conf/dfs.include on Namenode host
> - Restart all required services
> - dfs.include gets created on all datanode hosts. 
> Tried the same with Yarn, yarn.include will be present only on 
> Resourcemanager node and doesnt get created on any other nodes(eg: one with 
> nodemanager)
> Ideally dfs.include should not be created on all datanode hosts



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

Reply via email to