Share via

Cosmos DB for MongoDB vCore stuck in Updating and unreachable

Carlos Sosa 25 Reputation points
2026-04-14T19:56:59.7933333+00:00

I need urgent assistance with my Azure Cosmos DB for MongoDB vCore cluster.

The cluster was showing sustained CPU around 90%. After approximately 3:07 PM, the Azure Monitor CPU graph started showing uneven/sparse points instead of a solid line, while staying around the same high level.

Mongo clients are now unable to connect and return:

MongoServerSelectionError: Server selection timed out after 30000 ms

I attempted to scale up the vCore tier to recover service availability, but the cluster is now stuck in “Updating” status.

Thank you, Carlos Sosa

Azure Cosmos DB
Azure Cosmos DB

An Azure NoSQL database service for app development.

Answer accepted by question author

  1. Manoj Kumar Boyini 13,930 Reputation points Microsoft External Staff Moderator
    2026-04-27T15:46:17.1333333+00:00

    Hi @Carlos Sosa

    The incident has been successfully mitigated after service health monitoring reported the cluster as healthy multiple times within a short interval. As part of the remediation, operational recovery actions were executed, including container restart procedures. A workflow automation process was also initiated to assist with recovery and was stopped once the service stabilized.

    During the investigation, a missing socket file was identified as a result of a recent pgmongo container upgrade. This was corrected using established troubleshooting and recovery guidelines. Following these actions, monitoring systems confirmed that the cluster returned to a healthy and stable state.

    Please let us know if you have any questions or concerns.

    0 comments

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest

Your answer

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