SQL Warehouse stuck on "Cluster Start-up Delayed

nidhin
New Contributor III

Hi everyone,

I'm running into an issue with my Starter Warehouse on Databricks and would appreciate any help or pointers.

Problem: My SQL Warehouse has been stuck in a Starting state with the following warning:

Cluster Start-up Delayed. Please wait while we continue to try and start the cluster. No action is required from you.
cluster-id: 0603-142345-jqh97kz4

It hasn't progressed past this state despite waiting.

Warehouse details:
- Name: Starter Warehouse (ID: 666b4657765a75b7)
- Type: Pro
- Cluster size: Small
- Scaling: Min 1 / Max 1
- Auto stop: 60 minutes of inactivity
- Channel: Current (v 2026.10)

What I've tried so far:
- Waited for an extended period
- The warning says no action is required, but the cluster hasn't started

Is this a known intermittent issue with resource availability? Is there a recommended wait time before taking action (e.g., stopping and restarting the warehouse)?

Any advice from the community or Databricks team would be greatly appreciated. Thanks in advance!

rdokala
New Contributor III

This typically points to delayed compute provisioning behind the SQL Warehouse, often due to temporary capacity/resource availability or a transient startup issue.

A few things I would try:

1. Stop and restart the SQL Warehouse
If it has been stuck for more than 15–30 minutes, manually stop it and start it again.

2. Check Databricks status page
Confirm whether there is an active incident or degradation in your cloud/region.

3. Try a different warehouse size
Temporarily switch from Small to Medium and start it again. Sometimes a different size can provision successfully if a specific capacity pool is constrained.

4. Review Events / cluster logs
Check the warehouse events to see whether the issue is capacity, cloud provider quota, network, policy, or permissions related.

6. Open a Databricks support ticket
In practice, if a SQL Warehouse is stuck in Starting for more than 20–30 minutes, I would stop/restart first. If it repeats, try resizing or use another warehouse, then raise it with Databricks support.