CosmosDB for postgresql stuck in Provisioning state

Vipal Mehta 45 Reputation points
2023-09-28T17:13:19.2133333+00:00

I am planning to use Read Replicas for my Cosmos DB for postgresql. I started with creating a replica of my existing DB instance on East US region.

The status shows as created on Deployment page, but the DB instance shows provisioning state and it is not allowing to do any actions on the Replica instance, nor it is allowing to promoting it as an independent cluster, which I wanted to test.

It has been 6 hours since I had created the Read replica, but the Deployment page shows as Deployment is in progress.

The resource on that page is shown as below -

Resource Type Status

chq-dev-postgres-read Azure Cosmos DB for PostgreSQL Cluster Created.

Kindly help with this, I have a requirement for Disaster recovery using Read replicas. Attaching the relevant snapshots

Please note that there might be a possibility that data from primary instance might replicate data to the secondary, but the data is not that large that it can take upto 6 hours. Also there are no metrics(Lag,CPU,Memory) on the replica instance.

Azure Cosmos DB
Azure Cosmos DB
An Azure NoSQL database service for app development.
Azure Database for PostgreSQL
{count} vote

1 answer

Sort by: Most helpful
  1. A, Kowsalya (Cognizant) 20 Reputation points
    2025-08-28T07:34:01.4333333+00:00

    I am trying to start our PostgreSQL instance, but it has been stuck in the provisioning status for the past hour.

     

    Can you please help on this

    __Azure Cosmos DB for PostgreSQL Cluster-à__devagenticcosmosdbpostgresql

    Subscription ID-7b052470-c07f-49aa-b8e7-46194651bc83

    0 comments No comments

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.