"evalue": "Jupyter cannot be started. Error attempting to locate jupyter: Data Science libraries jupyter and notebook are not installed in interpreter Python 3.7.7 64-bit ('jupyter': conda).",
"traceback": [
"Error: Jupyter cannot be started. Error attempting to locate jupyter: Data Science libraries jupyter and notebook are not installed in interpreter Python 3.7.7 64-bit ('jupyter': conda).",
@@ -5,7 +5,8 @@ This page provides details about features specific to one or more images.
...
@@ -5,7 +5,8 @@ This page provides details about features specific to one or more images.
## Apache Spark
## Apache Spark
**Specific Docker Image Options**
**Specific Docker Image Options**
*`-p 4040:4040` - The `jupyter/pyspark-notebook` and `jupyter/all-spark-notebook` images open [SparkUI (Spark Monitoring and Instrumentation UI)](http://spark.apache.org/docs/latest/monitoring.html) at default port `4040`, this option map `4040` port inside docker container to `4040` port on host machine . Note every new spark context that is created is put onto an incrementing port (ie. 4040, 4041, 4042, etc.), and it might be necessary to open multiple ports. For example: `docker run -d -p 8888:8888 -p 4040:4040 -p 4041:4041 jupyter/pyspark-notebook`
*`-p 4040:4040` - The `jupyter/pyspark-notebook` and `jupyter/all-spark-notebook` images open [SparkUI (Spark Monitoring and Instrumentation UI)](http://spark.apache.org/docs/latest/monitoring.html) at default port `4040`, this option map `4040` port inside docker container to `4040` port on host machine . Note every new spark context that is created is put onto an incrementing port (ie. 4040, 4041, 4042, etc.), and it might be necessary to open multiple ports. For example: `docker run -d -p 8888:8888 -p 4040:4040 -p 4041:4041 jupyter/pyspark-notebook`.
**Usage Examples**
**Usage Examples**
...
@@ -13,30 +14,66 @@ The `jupyter/pyspark-notebook` and `jupyter/all-spark-notebook` images support t
...
@@ -13,30 +14,66 @@ The `jupyter/pyspark-notebook` and `jupyter/all-spark-notebook` images support t
### Using Spark Local Mode
### Using Spark Local Mode
Spark local mode is useful for experimentation on small data when you do not have a Spark cluster available.
Spark **local mode** is useful for experimentation on small data when you do not have a Spark cluster available.
Spylon kernel instantiates a `SparkContext` for you in variable `sc` after you configure Spark
Spylon kernel instantiates a `SparkContext` for you in variable `sc` after you configure Spark
options in a `%%init_spark` magic cell.
options in a `%%init_spark` magic cell.
...
@@ -44,27 +81,30 @@ options in a `%%init_spark` magic cell.
...
@@ -44,27 +81,30 @@ options in a `%%init_spark` magic cell.
```python
```python
%%init_spark
%%init_spark
# Configure Spark to use a local master
# Configure Spark to use a local master
launcher.master="local[*]"
launcher.master="local"
```
```
```scala
```scala
// Now run Scala code that uses the initialized SparkContext in sc
// Sum of the first 100 whole numbers
valrdd=sc.parallelize(0to999)
valrdd=sc.parallelize(0to100)
rdd.takeSample(false,5)
rdd.sum()
// 5050
```
```
#### In an Apache Toree Scala Notebook
##### In an Apache Toree Kernel
Apache Toree instantiates a local `SparkContext` for you in variable `sc` when the kernel starts.
Apache Toree instantiates a local `SparkContext` for you in variable `sc` when the kernel starts.
```scala
```scala
valrdd=sc.parallelize(0to999)
// Sum of the first 100 whole numbers
rdd.takeSample(false,5)
valrdd=sc.parallelize(0to100)
rdd.sum()
// 5050
```
```
### Connecting to a Spark Cluster in Standalone Mode
### Connecting to a Spark Cluster in Standalone Mode
Connection to Spark Cluster on Standalone Mode requires the following set of steps:
Connection to Spark Cluster on **[Standalone Mode](https://spark.apache.org/docs/latest/spark-standalone.html)** requires the following set of steps:
0. Verify that the docker image (check the Dockerfile) and the Spark Cluster which is being
0. Verify that the docker image (check the Dockerfile) and the Spark Cluster which is being
deployed, run the same version of Spark.
deployed, run the same version of Spark.
...
@@ -75,97 +115,104 @@ Connection to Spark Cluster on Standalone Mode requires the following set of ste
...
@@ -75,97 +115,104 @@ Connection to Spark Cluster on Standalone Mode requires the following set of ste
* NOTE: When using `--net=host`, you must also use the flags `--pid=host -e
* NOTE: When using `--net=host`, you must also use the flags `--pid=host -e
TINI_SUBREAPER=true`. See https://github.com/jupyter/docker-stacks/issues/64 for details.
TINI_SUBREAPER=true`. See https://github.com/jupyter/docker-stacks/issues/64 for details.
#### In a Python Notebook
**Note**: In the following examples we are using the Spark master URL `spark://master:7077` that shall be replaced by the URL of the Spark master.
#### In Python
The **same Python version** need to be used on the notebook (where the driver is located) and on the Spark workers.
The python version used at driver and worker side can be adjusted by setting the environment variables `PYSPARK_PYTHON` and / or `PYSPARK_DRIVER_PYTHON`, see [Spark Configuration][spark-conf] for more information.
```python
```python
importos
frompyspark.sqlimportSparkSession
# make sure pyspark tells workers to use python3 not 2 if both are installed
// Now run Scala code that uses the initialized SparkContext in sc
// Sum of the first 100 whole numbers
valrdd=sc.parallelize(0to999)
valrdd=sc.parallelize(0to100)
rdd.takeSample(false,5)
rdd.sum()
// 5050
```
```
#### In an Apache Toree Scala Notebook
##### In an Apache Toree Scala Notebook
The Apache Toree kernel automatically creates a `SparkContext` when it starts based on configuration
The Apache Toree kernel automatically creates a `SparkContext` when it starts based on configuration information from its command line arguments and environment variables. You can pass information about your cluster via the `SPARK_OPTS` environment variable when you spawn a container.
information from its command line arguments and environment variables. You can pass information
about your cluster via the `SPARK_OPTS` environment variable when you spawn a container.
For instance, to pass information about a standalone Spark master, Spark binary location in HDFS,
For instance, to pass information about a standalone Spark master, you could start the container like so:
and an executor options, you could start the container like so:
```bash
```bash
docker run -d-p 8888:8888 -eSPARK_OPTS='--master=spark://10.10.10.10:7070 \
docker run -d-p 8888:8888 -eSPARK_OPTS='--master=spark://master:7077'\
Note that this is the same information expressed in a notebook in the Python case above. Once the
Note that this is the same information expressed in a notebook in the Python case above. Once the kernel spec has your cluster information, you can test your cluster in an Apache Toree notebook like so:
kernel spec has your cluster information, you can test your cluster in an Apache Toree notebook like
so:
```scala
```scala
// should print the value of --master in the kernel spec
// should print the value of --master in the kernel spec