- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-12-2022 12:39 AM
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.
- Labels:
-
Databricks Runtime
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-13-2022 11:37 PM
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-17-2022 01:52 AM
Hi, I am getting the same error. Can @DARSHAN BARGAL please help?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-17-2022 06:44 AM
Same, Cluster failed to start.
$HolderPlacementLockTimeout = terminatedinstance error. Any help so far?
