cancel
Showing results for 
Search instead for 
Did you mean: 
Community Platform Discussions
Connect with fellow community members to discuss general topics related to the Databricks platform, industry trends, and best practices. Share experiences, ask questions, and foster collaboration within the community.
cancel
Showing results for 
Search instead for 
Did you mean: 

Container lifetime?

mrstevegross
Contributor

When launching a job via "Create and trigger a one-time run" (docs), when using a custom image (docs), what's the lifetime of the container? Does it create the cluster, start the container, run the job, then terminate the container? Or does the running container persist and get re-used by subsequent jobs?

1 ACCEPTED SOLUTION

Accepted Solutions

Alberto_Umana
Databricks Employee
Databricks Employee

Hi @mrstevegross 

  1. Cluster Creation: When you submit a job using the "Create and trigger a one-time run" API, a new cluster is created if one is not specified.
  2. Container Start: The custom Docker image specified in the cluster configuration is used to start the container.
  3. Job Execution: The job runs within this container.
  4. Container Termination: After the job completes, the container is terminated along with the cluster.

The container does not persist and is not reused by subsequent jobs. Each job submission that requires a new cluster will start a new container based on the specified custom image, run the job, and then terminate the container and cluster upon completion.

View solution in original post

1 REPLY 1

Alberto_Umana
Databricks Employee
Databricks Employee

Hi @mrstevegross 

  1. Cluster Creation: When you submit a job using the "Create and trigger a one-time run" API, a new cluster is created if one is not specified.
  2. Container Start: The custom Docker image specified in the cluster configuration is used to start the container.
  3. Job Execution: The job runs within this container.
  4. Container Termination: After the job completes, the container is terminated along with the cluster.

The container does not persist and is not reused by subsequent jobs. Each job submission that requires a new cluster will start a new container based on the specified custom image, run the job, and then terminate the container and cluster upon completion.

Join Us as a Local Community Builder!

Passionate about hosting events and connecting people? Help us grow a vibrant local community—sign up today to get started!

Sign Up Now