You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-dev@hadoop.apache.org by "Siddharth Seth (JIRA)" <ji...@apache.org> on 2016/06/02 06:47:59 UTC
[jira] [Created] (YARN-5194) Avoid adding yarn-site to all
Configuration instances created by the JVM
Siddharth Seth created YARN-5194:
------------------------------------
Summary: 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 etc).
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
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-dev-help@hadoop.apache.org