Return-Path: X-Original-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C16A4115B8 for ; Tue, 1 Jul 2014 16:16:26 +0000 (UTC) Received: (qmail 58591 invoked by uid 500); 1 Jul 2014 16:16:26 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 58545 invoked by uid 500); 1 Jul 2014 16:16:26 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-issues@hadoop.apache.org Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 58530 invoked by uid 99); 1 Jul 2014 16:16:26 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Jul 2014 16:16:26 +0000 Date: Tue, 1 Jul 2014 16:16:26 +0000 (UTC) From: "Haohui Mai (JIRA)" To: common-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HADOOP-10623) Provide a utility to be able inspect the config as seen by a hadoop client / daemon MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HADOOP-10623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14049009#comment-14049009 ] Haohui Mai commented on HADOOP-10623: ------------------------------------- Thanks for the explanation. This should be a useful feature. Note that there is a {{GetConf}} tool in hdfs -- do you think that it might be cleaner if you can integrate this patch with it? > Provide a utility to be able inspect the config as seen by a hadoop client / daemon > ------------------------------------------------------------------------------------ > > Key: HADOOP-10623 > URL: https://issues.apache.org/jira/browse/HADOOP-10623 > Project: Hadoop Common > Issue Type: New Feature > Reporter: Gera Shegalov > Assignee: Gera Shegalov > Attachments: HADOOP-10623.v01.patch, HADOOP-10623.v02.patch, HADOOP-10623.v03.patch > > > To ease debugging of config issues it is convenient to be able to generate a config as seen by the job client or a hadoop daemon > {noformat} > ]$ hadoop org.apache.hadoop.util.ConfigTool -help > Usage: ConfigTool [ -xml | -json ] [ -loadDefaults ] [ resource1... ] > if resource contains '/', load from local filesystem > otherwise, load from the classpath > Generic options supported are > -conf specify an application configuration file > -D use value for given property > -fs specify a namenode > -jt specify a job tracker > -files specify comma separated files to be copied to the map reduce cluster > -libjars specify comma separated jar files to include in the classpath. > -archives specify comma separated archives to be unarchived on the compute machines. > The general command line syntax is > bin/hadoop command [genericOptions] [commandOptions] > {noformat} > {noformat} > $ hadoop org.apache.hadoop.util.ConfigTool -Dmy.test.conf=val mapred-site.xml ./hadoop-dist/target/hadoop-3.0.0-SNAPSHOT/etc/hadoop/core-site.xml | python -mjson.tool > { > "properties": [ > { > "isFinal": false, > "key": "mapreduce.framework.name", > "resource": "mapred-site.xml", > "value": "yarn" > }, > { > "isFinal": false, > "key": "mapreduce.client.genericoptionsparser.used", > "resource": "programatically", > "value": "true" > }, > { > "isFinal": false, > "key": "my.test.conf", > "resource": "from command line", > "value": "val" > }, > { > "isFinal": false, > "key": "from.file.key", > "resource": "hadoop-dist/target/hadoop-3.0.0-SNAPSHOT/etc/hadoop/core-site.xml", > "value": "from.file.val" > }, > { > "isFinal": false, > "key": "mapreduce.shuffle.port", > "resource": "mapred-site.xml", > "value": "${my.mapreduce.shuffle.port}" > } > ] > } > {noformat} -- This message was sent by Atlassian JIRA (v6.2#6252)