Apache Spark On Docker: 1. Pull The Image From Docker Repository
Apache Spark On Docker: 1. Pull The Image From Docker Repository
This repository contains a Docker file to build a Docker image with Apache Spark. This Docker
image depends on our previous Hadoop Docker image, available at the SequenceIQ GitHub page.
The base Hadoop Docker image is also available as an official Docker image.
ERROR –
if using boot2docker make sure your VM has more than 2GB memory
in your /etc/hosts file add $(boot2docker ip) as host 'sandbox' to make it easier to access
your sandbox UI
open yarn UI ports when running container
Versions
Hadoop 2.6.0 and Apache Spark v1.6.0 on Centos
Testing
There are two deploy modes that can be used to launch Spark applications on YARN.
YARN-client mode
In yarn-client mode, the driver runs in the client process, and the application master is only used
for requesting resources from YARN.
YARN-cluster mode
In yarn-cluster mode, the Spark driver runs inside an application master process which is managed
by YARN on the cluster, and the client can go away after initiating the application.
# execute the the following command which should write the "Pi is roughly 3.1418" into the logs
# note you must specify --files argument in cluster mode to enable metrics
spark-submit \
--class org.apache.spark.examples.SparkPi \
--files $SPARK_HOME/conf/metrics.properties \
--master yarn-cluster \
--driver-memory 1g \
--executor-memory 1g \
--executor-cores 1 \
$SPARK_HOME/lib/spark-examples-1.6.0-hadoop2.6.0.jar
Estimating Pi (yarn-client mode):
# execute the the following command which should print the "Pi is roughly 3.1418" to the screen
spark-submit \
--class org.apache.spark.examples.SparkPi \
--master yarn-client \
--driver-memory 1g \
--executor-memory 1g \
--executor-cores 1 \
$SPARK_HOME/lib/spark-examples-1.6.0-hadoop2.6.0.jar
export YARN_CONF_DIR="`pwd`/yarn-remote-client"
Docker's HDFS can be accessed only by root. When submitting Spark applications from outside of
the cluster, and from a user different than root, it is necessary to configure the
HADOOP_USER_NAME variable so that root user is used.
export HADOOP_USER_NAME=root