cancel
Showing results for 
Search instead for 
Did you mean: 
Get Started Discussions
cancel
Showing results for 
Search instead for 
Did you mean: 

what are the different types life_cycle_state in databricks for job cluster

shreyassharmabh
New Contributor II

We are trying to get cluster life_cycle_state using API and we are able to get various values as below
RUNNING
PENDING
TERMINATED
INTERNAL_ERROR

Is there any other values apart from above values it would be a great help.

1 ACCEPTED SOLUTION

Accepted Solutions

Kaniz
Community Manager
Community Manager
Hi @shreyassharmabh, Based on the provided information, the possible values for the life_cycle_state of a cluster are:- 
  • PENDING: The run has been triggered, and the cluster and execution context are being prepared
  •  RUNNING: The task of this run is being executed.
  • TERMINATING: The task of this run has been completed, and the cluster and execution context are being cleaned up.
  • TERMINATED: The task of this run has been completed, and the cluster and execution context have been cleaned up. This state is terminal.
  • SKIPPED: This run was aborted because a previous run of the same job was already active. This state is terminal.
  •  INTERNAL_ERROR: An exceptional state that indicates a failure in the Jobs service, such as network failure over a long period. If a run on a new cluster ends in the INTERNAL_ERROR state, the Jobs service terminates the cluster as soon as possible. This state is terminal.
  • Therefore, there are no other values apart from the ones mentioned above.
  • Sources:
    https://docs.databricks.com/workflows/jobs/jobs-2.0-api.html

View solution in original post

1 REPLY 1

Kaniz
Community Manager
Community Manager
Hi @shreyassharmabh, Based on the provided information, the possible values for the life_cycle_state of a cluster are:- 
  • PENDING: The run has been triggered, and the cluster and execution context are being prepared
  •  RUNNING: The task of this run is being executed.
  • TERMINATING: The task of this run has been completed, and the cluster and execution context are being cleaned up.
  • TERMINATED: The task of this run has been completed, and the cluster and execution context have been cleaned up. This state is terminal.
  • SKIPPED: This run was aborted because a previous run of the same job was already active. This state is terminal.
  •  INTERNAL_ERROR: An exceptional state that indicates a failure in the Jobs service, such as network failure over a long period. If a run on a new cluster ends in the INTERNAL_ERROR state, the Jobs service terminates the cluster as soon as possible. This state is terminal.
  • Therefore, there are no other values apart from the ones mentioned above.
  • Sources:
    https://docs.databricks.com/workflows/jobs/jobs-2.0-api.html
Welcome to Databricks Community: Lets learn, network and celebrate together

Join our fast-growing data practitioner and expert community of 80K+ members, ready to discover, help and collaborate together while making meaningful connections. 

Click here to register and join today! 

Engage in exciting technical discussions, join a group with your peers and meet our Featured Members.