Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/701#discussion_r12505246
--- Diff: docs/cluster-overview.md ---
@@ -105,23 +105,28 @@ HADOOP_CONF_DIR=XX /bin/spark-submit \
### Loading Configurations from a File
-The `spark-submit` script can load default `SparkConf` values from a
properties file and pass them
-onto your application. By default it will read configuration options from
-`conf/spark-defaults.conf`. Any values specified in the file will be
passed on to the
-application when run. They can obviate the need for certain flags to
`spark-submit`: for
-instance, if `spark.master` property is set, you can safely omit the
-`--master` flag from `spark-submit`. In general, configuration values
explicitly set on a
-`SparkConf` take the highest precedence, then flags passed to
`spark-submit`, then values
-in the defaults file.
+The `spark-submit` script can load default [Spark configuration
values](configuration.html) from
+a properties file and pass them on to your application. By default it will
read configuration
+options from `conf/spark-defaults.conf`, in which each line consists of a
key and a value separated
+by whitespace. For example,
+
+ spark.master spark://5.6.7.8:7077
+ spark.executor.memory 512m
+ spark.eventLog.enabled true
+
+Any values specified in the file will be passed on to the application.
Loading default Spark
+configurations this way can obviate the need for certain flags to
`spark-submit`. For instance,
+if `spark.master` property is set, you can safely omit the `--master` flag
from `spark-submit`.
+In general, configuration values explicitly set on a `SparkConf` take the
highest precedence,
+then flags passed to `spark-submit`, then values in the defaults file.
If you are ever unclear where configuration options are coming from.
fine-grained debugging
--- End diff --
there is a typo here (unrelated to your change)... period should be a
comma. I can fixup on merge.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
