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: 

Best sequence of using Vacuum, optimize, fsck repair and refresh commands.

Nis
New Contributor II

I have a delta table whose size will increases gradually now we have around 1.5 crores of rows while running vacuum command on that table i am getting the below error.

ERROR: Job aborted due to stage failure: Task 7 in stage 491.0 failed 4 times, most recent failure: Lost task 7.4 in stage 481.0 (TID 4116) (10.154.64.26 executor 7): ExecutorLostFailure (executor 7 exited caused by one of the running tasks) Reason: Executor heartbeat timed out after 177186 ms

and also wanted to know the best order of using

VACUUM table RETAIN 168 HOURS

optimize table;

fsck repair table table;

REFRESH table table;

1 REPLY 1

jose_gonzalez
Moderator
Moderator

Do you have access to the Executor 7 logs? is there a high GC or some other events that is making the heartbeat timeout? would you be able to check the failed stages?

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