diff options
| author | vundela <vsr@cloudera.com> | 2015-10-20 11:12:28 -0700 |
|---|---|---|
| committer | Marcelo Vanzin <vanzin@cloudera.com> | 2015-10-20 11:12:28 -0700 |
| commit | 2f6dd634c169a34811738a3c230cce4462612748 (patch) | |
| tree | 32749f98c4df0f5970ba7d0cb2e3e3b11684593d /docs/running-on-yarn.md | |
| parent | e18b571c3374ecbfc0b20a5064cb58d57a2a7d21 (diff) | |
| download | spark-2f6dd634c169a34811738a3c230cce4462612748.tar.gz spark-2f6dd634c169a34811738a3c230cce4462612748.tar.bz2 spark-2f6dd634c169a34811738a3c230cce4462612748.zip | |
[SPARK-11105] [YARN] Distribute log4j.properties to executors
Currently log4j.properties file is not uploaded to executor's which is leading them to use the default values. This fix will make sure that file is always uploaded to distributed cache so that executor will use the latest settings.
If user specifies log configurations through --files then executors will be picking configs from --files instead of $SPARK_CONF_DIR/log4j.properties
Author: vundela <vsr@cloudera.com>
Author: Srinivasa Reddy Vundela <vsr@cloudera.com>
Closes #9118 from vundela/master.
Diffstat (limited to 'docs/running-on-yarn.md')
| -rw-r--r-- | docs/running-on-yarn.md | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/docs/running-on-yarn.md b/docs/running-on-yarn.md index 677c000044..db6bfa69ee 100644 --- a/docs/running-on-yarn.md +++ b/docs/running-on-yarn.md @@ -81,7 +81,7 @@ all environment variables used for launching each container. This process is use classpath problems in particular. (Note that enabling this requires admin privileges on cluster settings and a restart of all node managers. Thus, this is not applicable to hosted clusters). -To use a custom log4j configuration for the application master or executors, there are two options: +To use a custom log4j configuration for the application master or executors, here are the options: - upload a custom `log4j.properties` using `spark-submit`, by adding it to the `--files` list of files to be uploaded with the application. @@ -89,6 +89,9 @@ To use a custom log4j configuration for the application master or executors, the (for the driver) or `spark.executor.extraJavaOptions` (for executors). Note that if using a file, the `file:` protocol should be explicitly provided, and the file needs to exist locally on all the nodes. +- update the `$SPARK_CONF_DIR/log4j.properties` file and it will be automatically uploaded along + with the other configurations. Note that other 2 options has higher priority than this option if + multiple options are specified. Note that for the first option, both executors and the application master will share the same log4j configuration, which may cause issues when they run on the same node (e.g. trying to write |