[YARN-5194] Avoid adding yarn-site to all Configuration instances created by the JVM

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Target Version/s: 3.5.0
• Assignee: Unassigned
• Reporter: Siddharth Seth
• Created: 02/Jun/16 06:46
• Updated: 04/Jan/24 08:58

Description

static {
    addDeprecatedKeys();
    Configuration.addDefaultResource(YARN_DEFAULT_CONFIGURATION_FILE);
    Configuration.addDefaultResource(YARN_SITE_CONFIGURATION_FILE);
  }

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.