hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Siddharth Seth (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-673) Remove yarn-default.xml
Date Tue, 14 May 2013 02:09:17 GMT

    [ https://issues.apache.org/jira/browse/YARN-673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13656641#comment-13656641

Siddharth Seth commented on YARN-673:

[~hitesh] That works as well. We can then defer generating separate documentation.

bq. Currently the default.xml files are XSDed and avail in the docs http://hadoop.apache.org/docs/r2.0.4-alpha/index.html
, see the last section 'Configuration' in the side menu
Thanks for pointing that out. We could use what Hitesh mentioned - and continue to leave the
*-default.xml files for documentation. Later, these could be converted to match the rest of
the documentation if required.

> 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
> 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

View raw message