Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id AE70520049E for ; Thu, 10 Aug 2017 15:09:04 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id AD0BA16B433; Thu, 10 Aug 2017 13:09:04 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id F1B7016B436 for ; Thu, 10 Aug 2017 15:09:03 +0200 (CEST) Received: (qmail 13960 invoked by uid 500); 10 Aug 2017 13:09:03 -0000 Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list issues@ambari.apache.org Received: (qmail 13950 invoked by uid 99); 10 Aug 2017 13:09:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Aug 2017 13:09:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 8EF1C1A0301 for ; Thu, 10 Aug 2017 13:09:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id EF2Bm5bnCWJH for ; Thu, 10 Aug 2017 13:09:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 760935F4A9 for ; Thu, 10 Aug 2017 13:09:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id E7645E0DEC for ; Thu, 10 Aug 2017 13:09:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 50CD42416D for ; Thu, 10 Aug 2017 13:09:00 +0000 (UTC) Date: Thu, 10 Aug 2017 13:09:00 +0000 (UTC) From: "Hadoop QA (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AMBARI-21692) dfs.include file is created on all datanode hosts when Ambari manages include/exclude files MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 10 Aug 2017 13:09:04 -0000 [ https://issues.apache.org/jira/browse/AMBARI-21692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16121583#comment-16121583 ] 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/11973//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)