Share via

can not run cluster due to limit exhausted

kupendar reddy 0 Reputation points
2026-05-22T06:21:03.3033333+00:00

User's image

while creating databricks resource in azure i have selected the 15 days free trial, does that causing an issue while creating and running notebooks though a job compute cluster

Azure Databricks
Azure Databricks

An Apache Spark-based analytics platform optimized for Azure.

0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Pilladi Padma Sai Manisha 8,405 Reputation points Microsoft External Staff Moderator
    2026-05-25T05:49:10.8766667+00:00

    Hi kupendar reddy,
    The error indicates that the Databricks workspace is running on a free-trial or subscription-limited Azure account, and the cluster cannot be provisioned because the available credits or quota have been exhausted. Azure free trial subscriptions are not eligible for quota increases, and the subscription must be upgraded to Pay-As-You-Go if you need to run larger clusters or request additional quota.

    Recommended steps:

    Upgrade the Azure subscription to Pay-As-You-Go and remove the spending limit if it is enabled. Microsoft documents that spending limits can block usage on free accounts, and removing the limit requires an active payment method.

    Request the required vCPU quota in the target region after the subscription is eligible. Microsoft provides a regional quota request flow for increasing compute quotas.

    Retry the cluster creation in the existing Databricks workspace after the subscription and quota changes are completed.

    Microsoft Documentation:

    Was this answer helpful?

  2. AI answer

    2026-05-22T06:21:17.9433333+00:00

    Yes. The error is caused by exhausting the free Databricks quota/credits, which prevents new compute (clusters) from starting.

    In Databricks Free Edition or trial workspaces, usage is limited by a fair usage policy. When the quota or credits are exceeded, Databricks shuts down compute resources and blocks further cluster starts for the rest of the day (or, in extreme cases, the rest of the month). Data and settings remain, but jobs and clusters cannot run until limits reset or the account is upgraded with a paid plan and valid payment method.

    To resolve this:

    1. Wait until the daily/monthly limit resets and try again, or
    2. Upgrade the workspace by adding a payment method and moving off the free/trial tier so that clusters and job compute can start normally.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

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.