MetricSign
EN|NLRequest Access
Medium severitycluster

Power BI Refresh Error:
INSTANCE_POOL_MAX_CAPACITY_REACHED

What does this error mean?

A Databricks cluster could not be created or scaled because the instance pool it is attached to has reached its configured maximum capacity. No additional instances can be allocated from the pool.

Common causes

  • 1Multiple jobs started simultaneously, all requesting clusters from the same pool
  • 2The pool maximum capacity is set too low for peak concurrent workloads
  • 3A long-running job is holding pool instances that would otherwise be available for new clusters
  • 4Auto-scaling of existing clusters consumed all remaining pool capacity

How to fix it

  1. 1Increase the maximum capacity of the instance pool in the Databricks pool settings
  2. 2Review which clusters are currently using the pool and whether any can be terminated
  3. 3Stagger job start times to avoid all jobs competing for the pool at the same time
  4. 4Consider creating a second pool for lower-priority workloads
  5. 5Configure a fallback pool or allow clusters to launch outside the pool when the pool is exhausted

Frequently asked questions

Does the pool automatically increase capacity?

No — the pool maximum capacity is a hard limit set by an admin. It must be manually increased in the pool settings.

Can I monitor pool utilization?

Yes — the Databricks UI shows current pool utilization. You can also use the Instance Pools API to query pool state programmatically.

Other cluster errors