Github user andrewor14 commented on a diff in the pull request: https://github.com/apache/spark/pull/701#discussion_r12505293 --- Diff: docs/spark-standalone.md --- @@ -150,20 +162,30 @@ You can also pass an option `--cores <numCores>` to control the number of cores Spark supports two deploy modes. Spark applications may run with the driver inside the client process or entirely inside the cluster. -The spark-submit script described in the [cluster mode overview](cluster-overview.html) provides the most straightforward way to submit a compiled Spark application to the cluster in either deploy mode. For info on the lower-level invocations used to launch an app inside the cluster, read ahead. +The spark-submit script provides the most straightforward way to submit a compiled Spark application to the cluster in either deploy mode. For more detail, see the [cluster mode overview](cluster-overview.html). + + ./bin/spark-submit \ + --class <main-class> + --master <master-url> \ + --deploy-mode <deploy-mode> \ + ... // other options + <application-jar> + [application-arguments] -## Launching Applications Inside the Cluster + main-class: The entry point for your application (e.g. org.apache.spark.examples.SparkPi) + master-url: The URL of the master node (e.g. spark://23.195.26.187:7077) + deploy-mode: Whether to deploy this application within the cluster or from an external client (e.g. 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 <main-class> + +Behind the scenes, this invokes the standalone Client to launch your application, which is also the legacy way to launch your application before Spark 1.0. --- End diff -- should we still keep around using Client to kill the driver though? Spark submit doesn't provide that
--- 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 infrastruct...@apache.org or file a JIRA ticket with INFRA. ---