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: 

com.databricks.backend.common.rpc.DriverStoppedException

ac567
New Contributor III

com.databricks.backend.common.rpc.DriverStoppedException: Driver down cause: driver state change (exit code: 143)

facing this cluster issue while i deploy and run my workflow through asset bundle. i have tried everything to update in spark configuration in asset bundle but exact cause is unknown.

1 ACCEPTED SOLUTION

Accepted Solutions

ac567
New Contributor III

i have increased driver memory and it worked. thanks for reply

View solution in original post

3 REPLIES 3

Alberto_Umana
Databricks Employee
Databricks Employee

Hello @ac567,

The error message "com.databricks.backend.common.rpc.DriverStoppedException: Driver down cause: driver state change (exit code: 143)" typically indicates that the driver process was terminated due to an Out of Memory (OOM) condition. This is similar to the exit code 137, which also signifies an OOM error.

Have you validated driver logs of the cluster?

ac567
New Contributor III

i have increased driver memory and it worked. thanks for reply

Alberto_Umana
Databricks Employee
Databricks Employee

Awesome, good to hear!

Connect with Databricks Users in Your Area

Join a Regional User Group to connect with local Databricks users. Events will be happening in your city, and you won’t want to miss the chance to attend and share knowledge.

If there isn’t a group near you, start one and help create a community that brings people together.

Request a New Group