Using Cloudera Manager I can set property "yarn.log-aggregation-enable" to "true". I can then run "Deploy Client Configuration" from Cloudera Manager.   However, if I then run "hadoop classpath" or "yarn classpath", the Hadoop configuration directory, which is typically the first entry in the classpath, does not include an updated yarn-site.xml with "yarn.log-aggregation-enable" set to "true". Instead, it has the original yarn-site.xml which has no "yarn.log-aggregation-enable" property in it.   Typically the first entry in the classpath is "/etc/hadoop/conf" from "hadoop classpath" or "yarn classpath".   In contrast, if I run a YARN application which starts a Java task, I can print system property "java.class.path" and the first entry is a directory that does contain an updated yarn-site.xml with the property set with the value "true". For example, instead of "/etc/hadoop/conf" I see in one task the first directory is  "/var/run/cloudera-scm-agent/process/840-yarn-NODEMANAGER". And in fact there is an environment variable,  HADOOP_CONF_DIR, which points to the correct Hadoop config dir.   But this directory, the one in /var/run/cloudera-scm-agent, is not included in "hadoop classpath" or "yarn classpath".   In our application, we need to get the correct Hadoop config dir without running an YARN task. Even if I create a small Java program that prints environment variable HADOOP_CONF_DIR, or system property "java.class.path" and run it with "hadoop jar", I do not get the correct results.   How do I get the correct Hadoop configuration directory without running a YARN job?   Thanks     ... View more