Spark Standalone Mode下的client mode和cluster mode

 1 . 有问题找百度,百度上搜索spark

2. 进入spark官网,找到对应的版本的文档.因为我的是spark2.1.2版本

3.进入spark的2.1.2文档后,看到Running the Examples and Shell和Launching on a Cluster

Launching on a Cluster The Spark cluster mode overview explains the key concepts in running on a cluster. Spark can run both by itself, or over several existing cluster managers. It currently provides several options for deployment: Standalone Deploy Mode: simplest way to deploy Spark on a private cluster Apache Mesos Hadoop YARN

4.进入文档的Spark Standalone Mode页面

5.Launching Spark Applications目录下讲了client mode和cluster mode

Launching Spark Applications The spark-submit script provides the most straightforward way to submit a compiled Spark application to the cluster. For standalone clusters, Spark currently supports two deploy modes. In client mode, the driver is launched in the same process as the client that submits the application(自己注释:client driver在同一个 process). In cluster mode, however, the driver is launched from one of the Worker processes inside the cluster, and the client process exits as soon as it fulfills its responsibility of submitting the application without waiting for the application to finish(自己注释:driver 由Worker 启动，client 很快退出). If your application is launched through Spark submit, then the application jar is automatically distributed to all worker nodes. For any additional jars that your application depends on, you should specify them through the --jars flag using comma as a delimiter (e.g. --jars jar1,jar2). To control the application’s configuration or execution environment, see Spark Configuration. Additionally, standalone cluster mode supports restarting your application automatically if it exited with non-zero exit code. To use this feature, you may pass in the --supervise flag to spark-submit when launching your application. Then, if you wish to kill an application that is failing repeatedly, you may do so through: ./bin/spark-class org.apache.spark.deploy.Client kill <master url> <driver ID> You can find the driver ID through the standalone Master web UI at http://<master url>:8080.