diff options
| author | zsxwing <zsxwing@gmail.com> | 2014-12-23 11:18:06 -0800 |
|---|---|---|
| committer | Josh Rosen <joshrosen@databricks.com> | 2014-12-23 11:18:06 -0800 |
| commit | 2d215aebaad4b4596354f1543d997d06ef340bd5 (patch) | |
| tree | 9679098c09413425db968b9739e46da20144d51d /docs/running-on-yarn.md | |
| parent | 2823c7f021efd775a14049d6cd0a1f1789a31b6c (diff) | |
| download | spark-2d215aebaad4b4596354f1543d997d06ef340bd5.tar.gz spark-2d215aebaad4b4596354f1543d997d06ef340bd5.tar.bz2 spark-2d215aebaad4b4596354f1543d997d06ef340bd5.zip | |
[SPARK-4931][Yarn][Docs] Fix the format of running-on-yarn.md
Currently, the format about log4j in running-on-yarn.md is a bit messy.
Author: zsxwing <zsxwing@gmail.com>
Closes #3774 from zsxwing/SPARK-4931 and squashes the following commits:
4a5f853 [zsxwing] Fix the format of running-on-yarn.md
Diffstat (limited to 'docs/running-on-yarn.md')
| -rw-r--r-- | docs/running-on-yarn.md | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/docs/running-on-yarn.md b/docs/running-on-yarn.md index 86276b1aa9..da1c8e8aa8 100644 --- a/docs/running-on-yarn.md +++ b/docs/running-on-yarn.md @@ -211,18 +211,18 @@ settings and a restart of all node managers. Thus, this is not applicable to hos To use a custom log4j configuration for the application master or executors, there are two options: -- upload a custom log4j.properties using spark-submit, by adding it to the "--files" list of files +- upload a custom `log4j.properties` using `spark-submit`, by adding it to the `--files` list of files to be uploaded with the application. -- add "-Dlog4j.configuration=<location of configuration file>" to "spark.driver.extraJavaOptions" - (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 +- add `-Dlog4j.configuration=<location of configuration file>` to `spark.driver.extraJavaOptions` + (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. 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 to the same log file). -If you need a reference to the proper location to put log files in the YARN so that YARN can properly display and aggregate them, use "${spark.yarn.app.container.log.dir}" in your log4j.properties. For example, log4j.appender.file_appender.File=${spark.yarn.app.container.log.dir}/spark.log. For streaming application, configuring RollingFileAppender and setting file location to YARN's log directory will avoid disk overflow caused by large log file, and logs can be accessed using YARN's log utility. +If you need a reference to the proper location to put log files in the YARN so that YARN can properly display and aggregate them, use `spark.yarn.app.container.log.dir` in your log4j.properties. For example, `log4j.appender.file_appender.File=${spark.yarn.app.container.log.dir}/spark.log`. For streaming application, configuring `RollingFileAppender` and setting file location to YARN's log directory will avoid disk overflow caused by large log file, and logs can be accessed using YARN's log utility. # Important notes |