[
https://issues.apache.org/jira/browse/HADOOP-10623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14307981#comment-14307981
]
Hadoop QA commented on HADOOP-10623:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12654156/HADOOP-10623.v04.patch
against trunk revision 276485e.
{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 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager:
org.apache.hadoop.yarn.server.resourcemanager.TestRMRestart
Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/5607//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/5607//console
This message is automatically generated.
> 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, HADOOP-10623.v04.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 <configuration file> specify an application configuration file
> -D <property=value> use value for given property
> -fs <local|namenode:port> specify a namenode
> -jt <local|jobtracker:port> specify a job tracker
> -files <comma separated list of files> specify comma separated files to be
> copied to the map reduce cluster
> -libjars <comma separated list of jars> specify comma separated jar files
> to include in the classpath.
> -archives <comma separated list of 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.3.4#6332)
