A job is a way of running a notebook or JAR either immediately or on a scheduled basis. You can create and run jobs using the UI, the CLI, and by invoking the Jobs API. Similarly, you can monitor job run results in the UI, using the CLI, by querying the API, and through email alerts. This topic focuses on performing job tasks using the UI. For the other methods, see Databricks CLI and Jobs API.
The number of jobs is limited to 1000.
This topic includes:
Click the Jobs icon in the sidebar. The Jobs list displays. The Jobs page lists all defined jobs, the cluster definition, the schedule if any, and the result of the last run.
In the Jobs list, you can filter jobs:
- Using key words.
- Selecting only jobs you own or jobs you have access to. Access to this filter depends on Job Access Control being enabled.
You can also click any column header to sort the list of jobs (either descending or ascending) by that column. By default, the page is sorted on job names in ascending order.
Click + Create Job. The job detail page displays.
Enter a name in the text field with the placeholder text
Specify the job properties:
Job task. Click Select notebook, Set JAR, or Configure spark-submit.
There are some significant differences between running notebook and JAR jobs. See JAR job tips for more information.
Job parameters. Click Edit next to Parameters. The type of the parameters depends on the task type:
Notebook - Key-value pairs or a JSON string representing key-value pairs. Such parameters set the value of widgets.
JAR job - Main class and arguments.
spark-submit - Main class, path to the library JAR, and arguments. For example:
Dependent libraries. Click Add next to Dependent Libraries. The dependent libraries are automatically attached to the cluster on launch. Follow the recommendations in Library dependencies for specifying dependencies.
The cluster the job will run on. Click Edit next to Cluster.
In the Cluster Type drop-down, choose New Cluster or Existing Cluster.
- There is a tradeoff between running on a new cluster and on an existing cluster. We recommend that you run on a new cluster for production-level jobs or jobs that are important to complete. Existing clusters work best for tasks such as updating dashboards at regular intervals.
- If you select a terminated cluster, and the job owner has Can Restart permission, the cluster is started when the job is scheduled to run.
Complete the cluster specification.
- New Cluster - complete the cluster configuration.
- Existing Cluster - select the cluster in the Select Cluster drop-down.
On the Jobs page, click a job name in the Name column. The job details page shows configuration parameters, active runs, and completed runs.
You can run a job on a schedule or immediately.
To define a schedule for the job, click Edit next to Schedule.
The Databricks job scheduler, like the Spark batch interface, is not intended for low latency jobs. Due to network or cloud issues, job runs may occasionally be delayed up to several minutes. In these situations, scheduled jobs will run immediately on service availability.
To run the job immediately, in the Active runs table click Run Now.
Click Run Now to do a test run of your notebook or JAR when you’ve finished configuring your job. If your notebook fails, you can edit it and the job will automatically run the new version of the notebook.
You can use Run Now with Different Parameters to re-run a job specifying different parameters or different values for existing parameters.
In the Active runs table, click Run Now with Different Parameters. The dialog varies depending on whether you are running a notebook job or a spark-submit job.
Notebook - A UI that lets you set key-value pairs or a JSON object displays. You can use this dialog to set the values of widgets:
spark-submit - A dialog containing the list of parameters displays. For example, you could run the SparkPi estimator described in Create a job with 100 instead of the default 10 partitions:
Specify the parameters. The provided parameters are merged with the default parameters for the triggered run. If you delete keys, the default parameters are used.
There are some caveats you need to be aware of when you run a JAR job.
JAR jobs are parameterized with an array of strings. In the UI, you input the parameters in the Arguments text box which are split into an array by applying POSIX shell parsing rules. For more information, reference the
In the API, you input the parameters as a standard JSON array. For more information, reference SparkJarTask. To access these parameters, inspect the
String array passed into your
Databricks maintains a history of your job runs for up to 60 days. If you need to preserve job runs, we recommend that you export job run results before they expire. For more information, see Export job run results.
To view job run information, in the Jobs page, click the job name in the Name column.
In the job run page, you can view the standard error, standard output, log4j output for the job run by clicking the Logs link in the Spark column.
In the job run page, click the run number in the Run column of the Completed in past 60 days table to see the relevant details and job output.
You can export notebook run results and job run logs for all job types.
To edit a job, click the job name link in the Jobs list.
To delete a job, click the x in the Action column in the Jobs list.
The Spark driver for Databricks has certain library dependencies that cannot be overridden. These libraries will take priority over any of your own libraries that conflict with them.
To get the full list of the driver library dependencies, run the following command inside a notebook attached to a cluster of the same Spark version (or the cluster with the driver you want to examine).
%sh ls /databricks/jars
A good rule of thumb when dealing with library dependencies while creating JARs for jobs is to list Spark and Hadoop as
provided dependencies. On Maven, add Spark and/or Hadoop as provided dependencies as shown below.
<dependency> <groupId>org.apache.spark</groupId> <artifactId>spark-core_2.10</artifactId> <version>1.5.0</version> <scope>provided</scope> </dependency> <dependency> <groupId>org.apache.hadoop</groupId> <artifactId>hadoop-core</artifactId> <version>1.2.1</version> <scope>provided</scope> </dependency>
sbt, add Spark and/or Hadoop as provided dependencies as shown below.
libraryDependencies += "org.apache.spark" %% "spark-core" % "1.6.0" % "provided" libraryDependencies += "org.apache.hadoop" %% "hadoop-core" % "1.2.1" % "provided"
Specify the correct Scala version for your dependencies based on the version you are running.
The other options that you can specify for a job include:
- Email alerts sent in case of job failure, success, or timeout. See Job alerts.
- The maximum completion time for a job. If the job does not complete in this time, Databricks sets its status to “Timed Out”.
Policy that determines when and how many times failed runs are retried.
- Maximum concurrent runs
- The maximum number of runs that can be run in parallel. On starting a new run, Databricks skips the run if the job has already reached its maximum number of active runs. Set this value higher than the default of 1 if you want to be able to perform multiple runs of the same job concurrently. This is useful for example if you trigger your job on a frequent schedule and want to allow consecutive runs to overlap with each other, or if you want to trigger multiple runs that differ by their input parameters.
You can set up email alerts for job runs. On the job detail page, click Advanced and click Edit next to Alerts. You can send alerts up job start, job success, and job failure (including skipped jobs), providing multiple comma-separated email addresses for each alert type. You can also opt out of alerts for skipped job runs.
Integrate these email alerts with your favorite notification tools, including:
Job access control enable job owners and administrators to grant fine grained permissions on their jobs. With job access controls, job owners can choose which other users or groups can view results of the job. Owners can also choose who can manage runs of their job (that is, invoke Run Now and Cancel.)
See Jobs Access Control for details.