Return-Path: X-Original-To: apmail-hadoop-hdfs-dev-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B36CFDBFC for ; Tue, 18 Sep 2012 00:23:08 +0000 (UTC) Received: (qmail 8311 invoked by uid 500); 18 Sep 2012 00:23:07 -0000 Delivered-To: apmail-hadoop-hdfs-dev-archive@hadoop.apache.org Received: (qmail 8227 invoked by uid 500); 18 Sep 2012 00:23:07 -0000 Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-dev@hadoop.apache.org Delivered-To: mailing list hdfs-dev@hadoop.apache.org Received: (qmail 8211 invoked by uid 99); 18 Sep 2012 00:23:07 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Sep 2012 00:23:07 +0000 Date: Tue, 18 Sep 2012 11:23:07 +1100 (NCT) From: "Eli Collins (JIRA)" To: hdfs-dev@hadoop.apache.org Message-ID: <1432542232.90485.1347927787445.JavaMail.jiratomcat@arcas> Subject: [jira] [Created] (HDFS-3945) HDFS conf is loading MR and YARN config files MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Eli Collins created HDFS-3945: --------------------------------- Summary: HDFS conf is loading MR and YARN config files Key: HDFS-3945 URL: https://issues.apache.org/jira/browse/HDFS-3945 Project: Hadoop HDFS Issue Type: Bug Affects Versions: 2.0.0-alpha Reporter: Eli Collins When running a recent trunk build and looking at the loaded NN conf (via /conf on the Web UI) I noticed that we're loading all the mapred* and yarn* configuration options, rather than just core* and hdfs* and the things they may load. We shouldn't load everything because it pollutes the config space and also because these config files may override an option already configured in the core or hdfs config files (which is how I noticed this). Marking this as an incompatible change since fixing this will break people who are currently setting HDFS options via non-HDFS site files. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira