Azure DocumentDB Mongo cluster stuck with 409 conflict: operation already in-progress

Hello ASC-Solutions,

Also please go through below insights;

It looks like your Azure Cosmos DB for MongoDB vCore cluster is stuck in an UpdateFailed/Failed provisioning state with publicNetworkAccess disabled, and now every attempt to flip that setting just returns a “409 Conflict – operation already in progress.” Here’s what usually helps in these scenarios:

1. Wait a few minutes and re-check
   • Sometimes the control-plane operation finishes but doesn’t immediately clear the lock. Give it 5–10 minutes, then re-run a simple CLI show command:

     
          az cosmosdb mongodb vcore cluster show \
     
            --name lightreportapprisk \
     
            --resource-group RG-Lightreport-MongoDB
     
     

   • If it still shows UpdateFailed/Failed and you get 409 on any update, move to the next step.
2. Inspect disk usage on each replica
   • A hanging update often ties back to resource exhaustion on the underlying replica nodes (e.g. WAL growth, broken replication slots).
   • In the portal go to Monitoring → Metrics → Storage used (Per node) or use CLI:

     
          az cosmosdb mongodb vcore replica list \
     
            --cluster-name lightreportapprisk \
     
            --resource-group RG-Lightreport-MongoDB
     
     

   • If any node is at or near capacity, that needs to be cleaned up.
3. Delete old write-ahead logs (WAL) via CLI
   • The doc recommends deleting WAL logs to free space. For each replica you identified:

     
          az cosmosdb mongodb vcore replica delete-log \
     
            --name lightreportapprisk \
     
            --resource-group RG-Lightreport-MongoDB \
     
            --replica-name <replica-node-name> \
     
            --log-type wal
     
     

   • After freeing up disk, give it a couple of minutes and then retry the publicNetworkAccess update:

     
          az cosmosdb mongodb vcore cluster update \
     
            --name lightreportapprisk \
     
            --resource-group RG-Lightreport-MongoDB \
     
            --public-network-access Enabled
     
     

4. If you still hit “409 Conflict”
   • Control-plane cancellation APIs aren’t public for vCore clusters, so you’ll need to open a support case. In your case details include: • Subscription ID • All correlation IDs from failed Activity Log entries • Timestamps of your delete-log commands and any CLI errors
5. Follow-up questions for more context
   • Can you confirm if any of the replica nodes are at > 80% disk utilization?
   • Have you already tried the delete-log --log-type wal command on each replica? Any errors there?
   • Do you have any locks (resource locks) on the RG-Lightreport-MongoDB resource group or the cluster itself?
   • Could you share the full CLI error output when you run the az cosmosdb mongodb vcore cluster update command?

Hope this helps get you un-stuck. Once the disk issue is cleared, the stuck update should finish and you’ll be able to re-enable public access. If it still won’t budge, raise a support ticket with the additional correlation IDs so the service team can cancel the hanging control-plane operation.

Reference list

• Resolving Connectivity Issues with Cosmos DB vCore Cluster https://learn.microsoft.com/azure/cosmos-db/mongodb/vcore/troubleshoot-update-stuck
• Configure Server Parameters & Clear WAL Logs https://learn.microsoft.com/azure/cosmos-db/mongodb/vcore/how-to-scale-cluster#server-parameters
• Handling 409 Conflicts in Azure Resources https://learn.microsoft.com/azure/azure-resource-manager/troubleshooting/conflict-errors

Hello **ASC-Solutions
**We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.