cancel
Showing results for 
Search instead for 
Did you mean: 
Data Engineering
Join discussions on data engineering best practices, architectures, and optimization strategies within the Databricks Community. Exchange insights and solutions with fellow data engineers.
cancel
Showing results for 
Search instead for 
Did you mean: 

Set Workflow Job Concurrency Limit

sage5616
Valued Contributor

Hi Everyone,

I need a job to be triggered every 5 minutes. However, if that job is already running, it must not be triggered again until that run is finished. Hence, I need to set the maximum run concurrency for that job to only one instance at a time.

What needs to be configured to achieve that? Any recommendations and pointers would be much appreciated 😀

Best Regards

1 ACCEPTED SOLUTION

Accepted Solutions

Anonymous
Not applicable

@Michael Okulik​ :

To ensure that a Databricks job is not triggered again until a running instance of the job is completed, you can set the maximum concurrency for the job to 1. Here's how you can configure this in Databricks:

  1. Go to the Databricks workspace and navigate to the job you want to configure.
  2. Click on the job name to open the job details page.
  3. Click on the "Edit" button to edit the job configuration.
  4. In the "Advanced" tab, scroll down to the "Concurrency" section.
  5. Set the "Maximum number of runs" to 1.
  6. Click on the "Save" button to save the job configuration.

With this configuration, if the job is already running, the next scheduled run will be skipped until the previous run is completed.

View solution in original post

1 REPLY 1

Anonymous
Not applicable

@Michael Okulik​ :

To ensure that a Databricks job is not triggered again until a running instance of the job is completed, you can set the maximum concurrency for the job to 1. Here's how you can configure this in Databricks:

  1. Go to the Databricks workspace and navigate to the job you want to configure.
  2. Click on the job name to open the job details page.
  3. Click on the "Edit" button to edit the job configuration.
  4. In the "Advanced" tab, scroll down to the "Concurrency" section.
  5. Set the "Maximum number of runs" to 1.
  6. Click on the "Save" button to save the job configuration.

With this configuration, if the job is already running, the next scheduled run will be skipped until the previous run is completed.

Join 100K+ Data Experts: Register Now & Grow with Us!

Excited to expand your horizons with us? Click here to Register and begin your journey to success!

Already a member? Login and join your local regional user group! If there isn’t one near you, fill out this form and we’ll create one for you to join!