cancel
Showing results for 
Search instead for 
Did you mean: 
Data Engineering
cancel
Showing results for 
Search instead for 
Did you mean: 

Cluster terminated.Reason:Unexpected launch failure

msoczka
New Contributor II

Using Community Edition. Cluster starts up and immediately terminates with the following error message.

Why would that be?

Message

Cluster terminated.Reason:Unexpected launch failure

An unexpected error was encountered while setting up the cluster. Please retry and contact Databricks if the problem persists.

Internal error message: com.databricks.backend.manager.instance.InstanceHolder$PlacementLockTimeout: Could not acquire placement lock context = findExistingInstanceById.

1 ACCEPTED SOLUTION

Accepted Solutions

User16753724663
Valued Contributor

Hi @Maciej Soczka​ 

We have some internal service interruptions due to which we had this issue. Our engineering has applied the fix and the cluster startup works as expected.

Sincerely apologies for the inconvenience caused here.

Regards,

Darshan

View solution in original post

3 REPLIES 3

User16753724663
Valued Contributor

Hi @Maciej Soczka​ 

We have some internal service interruptions due to which we had this issue. Our engineering has applied the fix and the cluster startup works as expected.

Sincerely apologies for the inconvenience caused here.

Regards,

Darshan

Manav
New Contributor II

Hi, I am getting the same error. Can @DARSHAN BARGAL​  please help?

Same, Cluster failed to start.

$HolderPlacementLockTimeout = terminatedinstance error. Any help so far?

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.