Postgres for Cosmos DB stuck creating standby

Question

Hi, Was wondering if anyone encountered this before. I had a basic postgres Cosmos setup for evaluation, then i scaled up the machine as it started to need a few more resources. Now it's been stuck "Creating standby" for a few days. I'm running high availability with a single node.

I have limited permissions and cant send support tickets.

Answer 1

Hi @Bill Nunney,

Welcome to the Microsoft Q&A and thank you for posting your questions here.

As I understand it, your setup is stuck in the 'Creating standby' state for a long time.

It seems like your primary node might have failed and the failover process is taking longer than expected. When high availability is enabled, Azure Cosmos DB for PostgreSQL runs one standby node for each primary node in the cluster. The standby node is used to take over if the primary node fails.

If you are seeing "Creating standby" for a few days, it might be possible that the failover process is taking longer than expected. You can check the Overview page for your cluster in the Azure portal to see if there are any alerts or notifications related to the failover process. If there are no alerts or notifications, you can try restarting the primary node to see if it triggers the failover process.

For more information, please refer to these links:

https://learn.microsoft.com/en-us/azure/cosmos-db/postgresql/concepts-high-availability

https://learn.microsoft.com/en-us/azure/cosmos-db/postgresql/howto-high-availability

If the above steps do not resolve the issue, it might be best to create a support ticket. If you have a support plan, could you please file a support ticket for deeper investigation and do share the SR# with us? In case if you don't have a support plan, please let us know here.

Hope this helps. Do let us know if you have 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.