[
https://issues.apache.org/jira/browse/YARN-673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13656348#comment-13656348
]
Hitesh Shah commented on YARN-673:
----------------------------------
How about:
{code}
---
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/conf/YarnConfiguration.java
+++
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/conf/YarnConfiguration.java
@@ -38,7 +38,6 @@
private static final String YARN_SITE_XML_FILE = "yarn-site.xml";
static {
- Configuration.addDefaultResource(YARN_DEFAULT_XML_FILE);
Configuration.addDefaultResource(YARN_SITE_XML_FILE);
}
{code}
And optionally also, move yarn-default.xml out of the jar and make it part of
the tar/rpm under a conf.default/ directory.
> Remove yarn-default.xml
> -----------------------
>
> Key: YARN-673
> URL: https://issues.apache.org/jira/browse/YARN-673
> Project: Hadoop YARN
> Issue Type: Improvement
> Reporter: Siddharth Seth
>
> The default configuration files serve 2 purposes
> 1. Documenting available config parameters, and their default values.
> 2. Specifying default values for these parameters.
> An xml file hidden inside a jar is not necessarily the best way to document
> parameters. This could be moved into the documentation itself.
> Default values already exist in code for most parameters. There's no need to
> specify them in two places. We need to make sure defaults exist for all
> parameters before attempting this.
> Having default configuration files just bloats job conf files; over 450
> parameters, out of which <20 are likely job specific params. JobConf files
> end up being rather big, and the memory footprint of the conf object is large
> (>300KB last I checked).
--
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
