Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/1200#discussion_r14318309
--- Diff: docs/submitting-applications.md ---
@@ -42,10 +42,20 @@ Some of the commonly used options are:
* `--class`: The entry point for your application (e.g.
`org.apache.spark.examples.SparkPi`)
* `--master`: The [master URL](#master-urls) for the cluster (e.g.
`spark://23.195.26.187:7077`)
-* `--deploy-mode`: Whether to deploy your driver program within the
cluster or run it locally as an external client (either `cluster` or `client`)
+* `--deploy-mode`: Whether to deploy your driver on the worker nodes
(`cluster`) or locally as an external client (`client`) (default: `client`)*
* `application-jar`: Path to a bundled jar including your application and
all dependencies. The URL must be globally visible inside of your cluster, for
instance, an `hdfs://` path or a `file://` path that is present on all nodes.
* `application-arguments`: Arguments passed to the main method of your
main class, if any
+*In general, if you are hosting your own cluster, `cluster` mode provides
little benefit over its
+alternative. The main use case for `cluster` mode is when the machine that
launches the application
+is far from the worker machines, in which case the communication between
the driver and the
+executors suffers from high network latency. Note that `cluster` mode is
currently not supported
+for standalone clusters, Mesos clusters, and python applications.
--- End diff --
should this be "or"?
---
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.
---
