ResourceCountExceedsLimitDueToTemplate

Karthi Krish 0 Reputation points
2023-08-03T04:19:13.6466667+00:00

run failed with error message

Unexpected failure while waiting for the cluster (0802-115024-5ao65fbu) to be ready: Cluster 0802-115024-5ao65fbu is in unexpected state Terminated: AZURE_QUOTA_EXCEEDED_EXCEPTION(CLIENT_ERROR): azure_error_code:ResourceCountExceedsLimitDueToTemplate,azure_error_message:Subscription (Free Trail) has a quota of 3 for resources of type PublicIpAddress with sku SkuNotSpecified. Subscription currently has 1 resources and the template contains 8 new resources of the this type which exceeds the quota. Please contact support to increase the quota for resource type PublicIpAddress,databricks_error_message:Error code: ResourceCountExceedsLimitDueToTemplate, error message: Subscription (Free Trail) has a quota of 3 for resources of type PublicIpAddress with sku SkuNotSpecified. Subscription currently has 1 resources and the template contains 8 new re ...

*WARNING: message truncated. Skipped 129 bytes of output

Azure Databricks
Azure Databricks
An Apache Spark-based analytics platform optimized for Azure.
2,540 questions
{count} votes

1 answer

Sort by: Most helpful
  1. PRADEEPCHEEKATLA 90,661 Reputation points Moderator
    2023-08-03T09:43:53.52+00:00

    @Karthi Krish - Thanks for the question and using MS Q&A platform.

    Problem:

    Databricks clusters use one public IP address per node (including the driver node). Azure subscriptions have public IP address limits per region. Thus, cluster creation and scale-up operations may fail if they would cause the number of public IP addresses allocated to that subscription in that region to exceed the limit. This limit also includes public IP addresses allocated for non-Databricks usage, such as custom user-defined VMs.

    In general, clusters only consume public IP addresses while they are active. However, PublicIPCountLimitReached errors may continue to occur for a short period of time even after other clusters are terminated. This is because Databricks temporarily caches Azure resources when a cluster is terminated. Resource caching is by design, since it significantly reduces the latency of cluster startup and autoscaling in many common scenarios.

    Solution:

    If your subscription has already reached its public IP address limit for a given region, then you should do one or the other of the following.

    • Create new clusters in a different Databricks workspace. The other workspace must be located in a region in which you have not reached your subscription's public IP address limit.
    • Request to increase your public IP address limit. Choose Quota as the Issue Type, and Networking as the Quota Type. User's image
    • In Details, request a Public IP Address quota increase. For example, if your limit is currently 60, and you want to create a 100-node cluster, request a limit increase to 160.
      User's image

    For more details, refer to Issue: Cloud provider launch failure while setting up the cluster (PublicIPCountLimitReached).

    Important! Note: Azure free trial/Student/Pass subscription are not eligible for a quota request. You need to upgrade to a Pay-As-You-Go subscription to increase the quota

    If you still have questions, you can chat with sales team to get more information.

    User's image

    Hope this helps. Do let us know if you any further queries.


    If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.


Your answer

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