Skip to content

How To Run A Spark Job#

Introduction#

All members of a project in Hopsworks can launch the following types of applications through a project's Jobs service:

  • Python
  • Apache Spark

Launching a job of any type is very similar process, what mostly differs between job types is the various configuration parameters each job type comes with. Hopsworks support scheduling to run jobs on a regular basis, e.g backfilling a Feature Group by running your feature engineering pipeline nightly. Scheduling can be done both through the UI and the python API, checkout our Scheduling guide.

UI#

Step 1: Jobs overview#

The image below shows the Jobs overview page in Hopsworks and is accessed by clicking Jobs in the sidebar.

Jobs overview
Jobs overview

Step 2: Create new job dialog#

Click New Job and the following dialog will appear.

Create new job dialog
Create new job dialog

Step 3: Set the job type#

By default, the dialog will create a Spark job. Make sure SPARK is chosen.

Step 4: Set the jar#

Next step is to select the program to run. You can either select From project, if the file was previously uploaded to Hopsworks, or Upload new file which lets you select a file from your local filesystem as demonstrated below. After that set the name for the job. By default, the job name is the same as the file name, but you can customize it here.

Configure program
Configure program

Step 5: Set the main class#

Next step is to set the main class for the application. Then specify advanced configuration or click Create New Job to create the job.

Set the main class
Set the main class

Then click Create job to create the job.

Step 6 (optional): Set the Spark script arguments#

In the job settings, you can specify arguments for your Spark script. Remember to handle the arguments inside your Spark script.

Configure Spark script arguments
Configure Spark script arguments

Step 7 (optional): Advanced configuration#

Resource allocation for the Spark driver and executors can be configured, also the number of executors and whether dynamic execution should be enabled.

  • Environment: The environment to use, must be based on spark-feature-pipeline

  • Driver memory: Number of cores to allocate for the Spark driver

  • Driver virtual cores: Number of MBs to allocate for the Spark driver

  • Executor memory: Number of cores to allocate for each Spark executor

  • Executor virtual cores: Number of MBs to allocate for each Spark executor

  • Dynamic/Static: Run the Spark application in static or dynamic allocation mode (see spark docs for details).

Resource configuration for the Spark job
Resource configuration for the Spark job

Additional files or dependencies required for the Spark job can be configured.

  • Additional archives: List of archives to be extracted into the working directory of each executor.

  • Additional jars: List of jars to be placed in the working directory of each executor.

  • Additional python dependencies: List of python files and archives to be placed on each executor and added to PATH.

  • Additional files: List of files to be placed in the working directory of each executor.

File configuration for the Spark job
File configuration for the Spark job

Line-separates properties to be set for the Spark application. For example, changing the configuration variables for the Kryo Serializer or setting environment variables for the driver, you can set the properties as shown below.

File configuration for the Spark job
Additional Spark configuration

Step 8: Execute the job#

Now click the Run button to start the execution of the job, and then click on Executions to see the list of all executions.

Start job execution
Start job execution

Step 9: Application logs#

To monitor logs while the execution is running, click Spark UI to open the Spark UI in a separate tab.

Once the execution is finished, you can click on Logs to see the full logs for execution.

Access Spark logs
Access Spark logs

Code#

Step 1: Upload the Spark jar#

This snippet assumes the Spark program is in the current working directory and named sparkpi.jar.

It will upload the jar to the Resources dataset in your project.

import hopsworks

project = hopsworks.login()

dataset_api = project.get_dataset_api()

uploaded_file_path = dataset_api.upload("sparkpi.jar", "Resources")

Step 2: Create Spark job#

In this snippet we get the JobsApi object to get the default job configuration for a SPARK job, set the python script to run and create the Job object.

jobs_api = project.get_job_api()

spark_config = jobs_api.get_configuration("SPARK")

spark_config['appPath'] = uploaded_file_path
spark_config['mainClass'] = 'org.apache.spark.examples.SparkPi'

job = jobs_api.create_job("pyspark_job", spark_config)

Step 3: Execute the job#

In this snippet we execute the job synchronously, that is wait until it reaches a terminal state, and then download and print the logs.

execution = job.run(await_termination=True)

out, err = execution.download_logs()

f_out = open(out, "r")
print(f_out.read())

f_err = open(err, "r")
print(f_err.read())

Configuration#

The following table describes the JSON payload returned by jobs_api.get_configuration("SPARK")

Field Type Description Default
type string Type of the job configuration "sparkJobConfiguration"
appPath string Project path to spark program (e.g Resources/foo.jar) null
mainClass string Name of the main class to run (e.g org.company.Main) null
environmentName string Name of the project spark environment "spark-feature-pipeline"
spark.driver.cores number (float) Number of CPU cores allocated for the driver 1.0
spark.driver.memory number (int) Memory allocated for the driver (in MB) 2048
spark.executor.instances number (int) Number of executor instances 1
spark.executor.cores number (float) Number of CPU cores per executor 1.0
spark.executor.memory number (int) Memory allocated per executor (in MB) 4096
spark.dynamicAllocation.enabled boolean Enable dynamic allocation of executors true
spark.dynamicAllocation.minExecutors number (int) Minimum number of executors with dynamic allocation 1
spark.dynamicAllocation.maxExecutors number (int) Maximum number of executors with dynamic allocation 2
spark.dynamicAllocation.initialExecutors number (int) Initial number of executors with dynamic allocation 1
spark.blacklist.enabled boolean Whether executor/node blacklisting is enabled false

Accessing project data#

To read a dataset in your project using Spark, use the full filesystem path where the data is stored. For example, to read a CSV file named data.csv located in the Resources dataset of a project called my_project:

Dataset<Row> df = spark.read()
    .option("header", "true")       // CSV has header
    .option("inferSchema", "true")  // Infer data types
    .csv("/Projects/my_project/Resources/data.csv");

df.show();

Additional files#

Different file types can be attached to the spark job and made available in the /srv/hops/artifacts folder when the Spark job is started. This configuration is mainly useful when you need to add additional configuration such as jars that needs to be added to the CLASSPATH.

When reading data in your Spark job it is recommended to use the Spark read API as previously demonstrated, since this reads from the filesystem directly, whereas Additional files configuration options will download the files in its entirety and is not a scalable option.

API Reference#

Jobs

Executions