Why your Redis Cloud Database Resize or Scaling Failed (insufficient capacity in selected zone) – Redis Knowledge Base

When you resize or scale a Redis Cloud database, the platform must provision additional infrastructure in the selected cloud provider zone. If that zone does not have enough available capacity at that moment, the request fails and the database may enter a provisioning error state. In some cases, this can also block deletion and result in continued charges.

This guide helps you quickly diagnose the issue, recover from stuck states, and prevent future failures through Quick Fixes, Step-by-Step Instructions, and Common Scenarios.

Quick Fix

What you’re seeing	What to do next
Resize or scaling failed with capacity/stockout error	Retry later or reduce requested size
Error mentions zone, VM type, or stockout	Try a different zone or region
Database stuck in provisioning error	Contact Support to clear or delete it
Delete button is unavailable	Requires backend reset by Support
Database still being billed while unusable	Request immediate deletion via Support

Common scenarios

Scenario	What’s happening	Recommended action
Scaling up memory or throughput fails immediately	Zone cannot allocate required resources	Retry with smaller increase or later time
Repeated failures in same zone	Zone is capacity constrained	Move workload to a different zone
Database stuck after failed resize	Provisioning did not complete or roll back	Contact Support to reset state
Cannot delete database after failure	Resource is locked in provisioning state	Support must intervene
Unexpected charges while database is unusable	Database/subscription still exists	Request deletion of database and subscription

Applies to

Redis Cloud (Essentials, Pro, Flex)
AWS, GCP, Azure
All environments

Step-by-Step Instructions

1. Confirm the failure is capacity-related

Look for error messages such as:

ZONE_RESOURCE_POOL_EXHAUSTED_WITH_DETAILS
“VM type unavailable in selected zone”
“Stockout” or “insufficient capacity”
Provisioning failure tied to a specific zone

If present, this confirms a zone capacity issue.

2. Check database state

In the Redis Cloud Console:

If status is Active → retry scaling or proceed with normal actions
If status is Pending or Provisioning error → continue below

3. If the database is active

Retry the configuration change:
- Reduce scale size (smaller memory/throughput increase), or
- Retry after some time
If failures persist:
- Consider using a different zone or region

4. If the database is stuck (Provisioning error)

This cannot be resolved from the UI.

Collect:

Account / organization name
Subscription ID
Database ID (BDB ID)
Cloud provider, region, and zone
Time and type of change attempted
Full error message

Then contact Redis Support and request:

Clearing the provisioning state
or
Deletion of the database (and subscription if needed)

5. Delete database once unblocked

After Support clears the issue:

Go to Configuration → Danger zone
Select Delete database
Optionally select Delete subscription
Confirm deletion

Important: Billing continues until the database and/or subscription is deleted.

Why this happens

This is caused by cloud provider capacity limits, not Redis configuration or billing issues.

Redis Cloud relies on the cloud provider (AWS, GCP, Azure) to allocate infrastructure in a specific zone. If that zone:

Has no available instances of the required type, or
Is temporarily exhausted (stockout)

then the operation fails.

Prevention best practices

Scale gradually
Avoid large, sudden increases in memory or throughput.

Avoid constrained zones
If failures repeat, use a different zone or region.

Validate after every change
Ensure database returns to Active state before moving on.

Act quickly on failures
Provisioning errors should be addressed immediately to avoid charges.

Clean up unused databases
Especially important for test or temporary environments.

Key takeaways

Capacity failures are zonal infrastructure issues
Failed operations do not partially apply
Stuck databases require Support intervention
Billing continues until resources are deleted

Related to