spark的使用

clouldManager 地址：http://10.1.12.104:7180/cmf/home

hue的地址管理job以及hdfs，可以在这里查看job的执行情况以及在hdfs上面的路径

上传文件到hdfs上面：

bin/hdfs dfs -mkdir testdata/，在hdfs上创建testdata文件夹(实际是在hdfs集群的/user/root/testdata)

在集群中提交运行：

spark2-submit --class dong.spark.SimpleApp  --master yarn --deploy-mode cluster --executor-memory 512m --num-executors 3 --driver-java-options "-XX:PermSize=512M -XX:MaxPermSize=1
024m" /usr/testdata/SimpleApp.jar 

执行的具体代码如下：

package dong.spark
import org.apache.hadoop.hive.ql.exec.spark.session.SparkSession
import org.apache.spark.SparkContext
import org.apache.spark.SparkContext
import org.apache.spark.SparkConf

object SimpleApp {
  def main(args: Array[String]) {

    //val conf = new SparkConf().setAppName("Simple Application")//.setMaster("local[2]")此种写法应该是spark1的写法，而且是local模式
    //.setMaster("spark://10.1.12.114:7077")此为standlone模式下的写法
    implicit val spark = org.apache.spark.sql.SparkSession.builder().appName("Simple Application").master("yarn-cluster").getOrCreate()
    //此为集群写法，yarn模式

    val logFile = "hdfs://nameservice1/user/root/testdata/file.txt"//此处指明文件所在的hdfs地址  nameservice1为dfs.nameservices的命名空间hdfs-site.xml
    //<property>      <name>dfs.nameservices</name>      <value>nameservice1</value>    </property>

    val logData = spark.sparkContext.textFile(logFile,2)
    val numAs = logData.flatMap(x=>x.split(" ")).filter(_.contains("a")).count()
    println("Words with a: %s".format(numAs))//此输出需要到log文件中才能看到
    spark.close()
  }
}

参考自：https://spark.apache.org/docs/latest/submitting-applications.html

常见的语法：

./bin/spark-submit \
  --class <main-class>
  --master <master-url> \
  --deploy-mode <deploy-mode> \
  --conf <key>=<value> \
  ... # other options
  <application-jar> \
  [application-arguments]

举几个常用的用法例子：

# Run application locally on 8 cores
./bin/spark-submit \
  --class org.apache.spark.examples.SparkPi \
  --master local[8] \
  /path/to/examples.jar \
  100

# Run on a Spark Standalone cluster in client deploy mode
./bin/spark-submit \
  --class org.apache.spark.examples.SparkPi \
  --master spark://207.184.161.138:7077 \
  --executor-memory 20G \
  --total-executor-cores 100 \
  /path/to/examples.jar \
  1000

# Run on a Spark Standalone cluster in cluster deploy mode with supervise
./bin/spark-submit \
  --class org.apache.spark.examples.SparkPi \
  --master spark://207.184.161.138:7077 \
  --deploy-mode cluster
  --supervise
  --executor-memory 20G \
  --total-executor-cores 100 \
  /path/to/examples.jar \
  1000

# Run on a YARN cluster
export HADOOP_CONF_DIR=XXX
./bin/spark-submit \
  --class org.apache.spark.examples.SparkPi \
  --master yarn-cluster \  # can also be `yarn-client` for client mode
  --executor-memory 20G \
  --num-executors 50 \
  /path/to/examples.jar \
  1000

# Run a Python application on a Spark Standalone cluster
./bin/spark-submit \
  --master spark://207.184.161.138:7077 \
  examples/src/main/python/pi.py \
  1000

1、一引起重要的参数说明

（1）—-class： 主类，即main函数所有的类

（2）—- master : master的URL，见下面的详细说明。

（3）—-deploy-mode:client和cluster2种模式

（4）—-conf:指定key=value形式的配置

2、关于jar包

hadoop和spark的配置会被自动加载到SparkContext,因此，提交application时只需要提交用户的代码以及其它依赖包，这有2种做法：

（1）将用户代码打包成jar，然后在提交application时使用—-jar来添加依赖jar包

（2）将用户代码与依赖一起打包成一个大包 assembly jar (or “uber” jar)

关于依赖关系更详细的说明：

When using spark-submit, the application jar along with any jars included with the --jars option will be automatically transferred to the cluster. Spark uses the following URL scheme to allow different strategies for disseminating jars:

• file: - Absolute paths and file:/ URIs are served by the driver’s HTTP file server, and every executor pulls the file from the driver HTTP server.

• hdfs:, http:, https:, ftp: - these pull down files and JARs from the URI as expected

• local: - a URI starting with local:/ is expected to exist as a local file on each worker node. This means that no network IO will be incurred, and works well for large files/JARs that are pushed to each worker, or shared via NFS, GlusterFS, etc.

Note that JARs and files are copied to the working directory for each SparkContext on the executor nodes. This can use up a significant amount of space over time and will need to be cleaned up. With YARN, cleanup is handled automatically, and with Spark standalone, automatic cleanup can be configured with the spark.worker.cleanup.appDataTtl property.

Users may also include any other dependencies by supplying a comma-delimited list of maven coordinates with --packages. All transitive dependencies will be handled when using this command. Additional repositories (or resolvers in SBT) can be added in a comma-delimited fashion with the flag --repositories. These commands can be used with pyspark, spark-shell, and spark-submit to include Spark Packages.

For Python, the equivalent --py-files option can be used to distribute .egg, .zip and .py libraries to executors.

3、关于master的值

（1）对于standalone模式，是spark://ip:port/的形式

（2）对于yarn，有yarn-cluster与yarn-cluster2种

（3）对于mesos，目前只有client选项

（4）除此之外，还有local[N]这种用于本地调试的选项

4、关于client与cluster模式

A common deployment strategy is to submit your application from a gateway machine that is physically co-located with your worker machines (e.g. Master node in a standalone EC2 cluster). In this setup, client mode is appropriate. In client mode, the driver is launched directly within the spark-submit process which acts as a client to the cluster. The input and output of the application is attached to the console. Thus, this mode is especially suitable for applications that involve the REPL (e.g. Spark shell).

Alternatively, if your application is submitted from a machine far from the worker machines (e.g. locally on your laptop), it is common to usecluster mode to minimize network latency between the drivers and the executors. Note that cluster mode is currently not supported for Mesos clusters. Currently only YARN supports cluster mode for Python applications.

5、加载本地的配置文件

The spark-submit script can load default Spark configuration values from a properties file and pass them on to your application. By default it will read options from conf/spark-defaults.conf in the Spark directory. For more detail, see the section on loading default configurations.

Loading default Spark configurations this way can obviate the need for certain flags to spark-submit. For instance, if the 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, you can print out fine-grained debugging information by running spark-submit with the --verbose option.

附spark-submit的完整命令：