/apps/app/spark-1.6.1-bin-hadoop2.6/bin/spark-submit
–class com.zdhy.zoc2.sparksql.core.JavaSparkSqlLogRegularApp
–files /apps/app/apache-hive-1.2.1-bin/conf/hive-site.xml
–driver-class-path /apps/app/apache-hive-1.2.1-bin/lib/mysql-connector-java-5.1.21.jar:/apps/app/spark-1.6.1-bin-hadoop2.6/lib/c3p0-0.9.1.2.jar:/apps/app/spark-1.6.1-bin-hadoop2.6/lib/commons-dbutils-1.3.jar
–master spark://master:7077 /root/sparkapps/zoc2-0.0.1-SNAPSHOT.jar /zoc2_test/syslog1 event “SELECT * FROM event” /zoc2/parquetfile/
–jars /apps/app/spark-1.6.1-bin-hadoop2.6/lib/c3p0-0.9.1.2.jar,/apps/app/spark-1.6.1-bin-hadoop2.6/lib/commons-dbutils-1.3.jar
1.submit提交命令;
2.对应jar文件的程序入口类;
3.配置文件路径,一般为hive的配置文件
4.driver所依赖的包,多个包之间用冒号(:)分割
5.master:spark集群提交路径、jar程序路径、jar程序参数(参数有空格用“”引起来)
6.driver和executor都需要的包,多个包之间用逗号(,)分割
—————————————————————————————–
附spark-submit的完整命令:
~/spark$ bin/spark-submit Usage: spark-submit [options] [app arguments] Usage: spark-submit –kill [submission ID] –master [spark://…] Usage: spark-submit –status [submission ID] –master [spark://…] Options:
–master MASTER_URL spark://host:port, mesos://host:port, yarn, or local.
–deploy-mode DEPLOY_MODE Whether to launch the driver program locally (“client”) or on one of the worker machines inside the cluster (“cluster”) (Default: client).
–class CLASS_NAME Your application’s main class (for Java / Scala apps).
–name NAME A name of your application.
–jars JARS Comma-separated list of local jars to include on the driver and executor classpaths.
–packages Comma-separated list of maven coordinates of jars to include on the driver and executor classpaths. Will search the local maven repo, then maven central and any additional remote repositories given by –repositories. The format for the coordinates should be groupId:artifactId:version.
–repositories Comma-separated list of additional remote repositories to search for the maven coordinates given with
–packages. –py-files PY_FILES Comma-separated list of .zip, .egg, or .py files to place on the PYTHONPATH for Python apps.
–files FILES Comma-separated list of files to be placed in the working directory of each executor.
–conf PROP=VALUE Arbitrary Spark configuration property.
–properties-file FILE Path to a file from which to load extra properties. If not specified, this will look for conf/spark-defaults.conf.
–driver-memory MEM Memory for driver (e.g. 1M, 2G) (Default: 512M).
–driver-java-options Extra Java options to pass to the driver. –
-driver-library-path Extra library path entries to pass to the driver.
–driver-class-path Extra class path entries to pass to the driver. Note that jars added with –jars are automatically included in the classpath. –executor-memory MEM Memory per executor (e.g. 1M, 2G) (Default: 1G).
–proxy-user NAME User to impersonate when submitting the application. –help, -h Show this help message and exit
–verbose, -v Print additional debug output
–version, Print the version of current Spark Spark standalone with cluster deploy mode only:
–driver-cores NUM Cores for driver (Default: 1). Spark standalone or Mesos with cluster deploy mode only:
–supervise If given, restarts the driver on failure.
–kill SUBMISSION_ID If given, kills the driver specified.
–status SUBMISSION_ID If given, requests the status of the driver specified. Spark standalone and Mesos only:
–total-executor-cores NUM Total cores for all executors. Spark standalone and YARN only:
–executor-cores NUM Number of cores per executor. (Default: 1 in YARN mode, or all available cores on the worker in standalone mode) YARN-only:
–driver-cores NUM Number of cores used by the driver, only in cluster mode (Default: 1).
–queue QUEUE_NAME The YARN queue to submit to (Default: “default”).
–num-executors NUM Number of executors to launch (Default: 2).
–archives ARCHIVES Comma separated list of archives to be extracted into the working directory of each executor.
–principal PRINCIPAL Principal to be used to login to KDC, while running on secure HDFS.
–keytab KEYTAB The full path to the file that contains the keytab for the principal specified above. This keytab will be copied to the node running the Application Master via the Secure Distributed Cache, for renewing the login tickets and the delegation tokens periodically.