Share via

I'm creating a single node compute in Azure Databricks, but it remains at "Finding instances for new nodes, acquiring more instances if necessary"

Alan Zhang 1 Reputation point
2025-10-06T04:27:28.5166667+00:00

I'm creating a single node compute (lowest CPU and memory requirement) in Azure Databricks, but it remains at "Finding instances for new nodes, acquiring more instances if necessary" for 30 minutes (still in that state as of this writing).

I'm on a corporate subscription (not on free or student subscription).

Azure Databricks
Azure Databricks

An Apache Spark-based analytics platform optimized for Azure.


2 answers

Sort by: Most helpful
  1. Anonymous
    2025-10-07T12:15:15.8433333+00:00

    Hi @alan zhang

    I hope the steps provided above were helpful. Please let me know if there's anything else I can assist you with.

    Thanks,
    Vrishabh

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments

  2. Anonymous
    2025-10-06T07:39:20.3333333+00:00

    Hi @alan zhang

    Here are some recommended actions to address this issue -

    Regional Capacity or SKU Availability

    • The requested VM size (even for the smallest SKU) may not be available in your selected region due to capacity constraints.
    • Action:
      • Check the https://status.azure.com for regional capacity issues.
        • Try changing the cluster location to another region where the SKU is available.

    Subscription Quota Limits

    Network Configuration Issues

    • If your workspace is deployed in a custom VNet, misconfigured routes or firewalls can block Databricks control plane from reaching the compute nodes.
    • Action:
      • Ensure outbound connectivity on port 443 to Databricks control plane endpoints.

    Resource Contention or Spot Instances

    • If you are using spot instances or a highly demanded SKU (e.g., GPU-enabled), provisioning delays can occur.
    • Action:
      • Switch to an on-demand instance type.
        • Reduce cluster size or disable autoscaling temporarily.

    Troubleshooting steps -

    • Always check event logs in the Databricks UI for detailed error messages.
    • If the cluster remains in pending state beyond 30 minutes, terminate and retry after verifying quotas and network settings.
    • For persistent issues, raise a support ticket with Azure, including cluster configuration and event logs.

    Recommended Microsoft Learn Links

    Thanks,
    Vrishabh

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.