Skip to contents

This is a long-running operation, which blocks until Clusters on Databricks reach RUNNING state with the timeout of 20 minutes, that you can change via timeout parameter. By default, the state of Databricks Clusters is reported to console. You can change this behavior by changing the callback parameter.

Usage

start_cluster_and_wait(
  client,
  cluster_id,
  timeout = 20,
  callback = cli_reporter
)

Arguments

client

Required. Instance of DatabricksClient()

cluster_id

Required. The cluster to be started.

timeout

Time to wait for the operation to complete in minutes.

callback

Function to report the status of the operation. By default, it reports to console.

Details

Starts a terminated Spark cluster with the supplied ID. This works similar to createCluster except:

  • The previous cluster id and attributes are preserved. * The cluster starts with the last specified cluster size. * If the previous cluster was an autoscaling cluster, the current cluster starts with the minimum number of nodes. * If the cluster is not currently in a TERMINATED state, nothing will happen. * Clusters launched to run a job cannot be started.