Databricks job keep getting failed due to executor lost.

amitkmaurya — Thu, 02 May 2024 08:50:56 GMT

Getting following error while saving a dataframe partitioned by two columns.

Job aborted due to stage failure: Task 5774 in stage 33.0 failed 4 times, most recent failure: Lost task 5774.3 in stage 33.0 (TID 7736) (13.2.96.110 executor 7): ExecutorLostFailure (executor 7 exited caused by one of the running tasks) Reason: Command exited with code 137

Please help me why I am getting this error and how can this be solved.

Driver + executor 64gb/16cores

Re: Databricks job keep getting failed due to executor lost.

amitkmaurya — Fri, 17 May 2024 06:10:56 GMT

Hi,

I have solved the problem with the same workers and driver.

In my case data skewness was the problem.

Adding repartition to the dataframe just before writing, evenly distributed the data across the nodes and this stage failure resolved.

Thanks @Retired_mod for your insoghts.

topic Databricks job keep getting failed due to executor lost. in Data Engineering

Databricks job keep getting failed due to executor lost.

Re: Databricks job keep getting failed due to executor lost.