hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allen Wittenauer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-5194) Avoid adding yarn-site to all Configuration instances created by the JVM
Date Sat, 04 Jun 2016 03:51:59 GMT

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

Allen Wittenauer commented on YARN-5194:

Until hdfs getconf is made into a generic utility callable from everywhere, this change will
break the universe.

> Avoid adding yarn-site to all Configuration instances created by the JVM
> ------------------------------------------------------------------------
>                 Key: YARN-5194
>                 URL: https://issues.apache.org/jira/browse/YARN-5194
>             Project: Hadoop YARN
>          Issue Type: Improvement
>            Reporter: Siddharth Seth
> {code}
> static {
>     addDeprecatedKeys();
>     Configuration.addDefaultResource(YARN_DEFAULT_CONFIGURATION_FILE);
>     Configuration.addDefaultResource(YARN_SITE_CONFIGURATION_FILE);
>   }
> {code}
> This puts the contents of yarn-default and yarn-site into every configuration instance
created in the VM after YarnConfiguration has been initialized.
> This should be changed to a local addResource for the specific YarnConfiguration instance,
instead of polluting every Configuration instance.
> Incompatible change. Have set the target version to 3.x. 
> The same applies to HdfsConfiguration (hdfs-site.xml), and Configuration (core-site.xml
> core-site may be worth including everywhere, however it would be better to expect users
to explicitly add the relevant resources.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org

View raw message