[ https://issues.apache.org/jira/browse/YARN-673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13656343#comment-13656343 ]
Siddharth Seth commented on YARN-673: ------------------------------------- The documentation will be part of the source tree, so keeping it up to date should not be any tougher. Grepping through *-default.xml is really only for developers - and that should be possible on the documentation as well. Since these files sit insider jars - I don't see how they serve as documentation iac. > 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