[CSHARP-3258] Using Azure functions with Azure Atlas cluster, tier upgrade makes function unresponsive Created: 18/Nov/20  Updated: 04/Dec/20  Resolved: 04/Dec/20

Status: Closed
Project: C# Driver
Component/s: None
Affects Version/s: 2.9.3
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Francisco Alanis Assignee: James Kovacs
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Case:

 Description   

Repro steps:

1. Create resources on Azure to be able to deploy an F# Azure function
2. Create an Azure cluster in MongoDB Atlas
3. Create an F# function that exposes a REST API with a single call (doDbStuff) that inserts and finds documents.
4. Call this function continuously from 4 or 5 different threads/processes.
5. With the traffic from 4, do a failover. This behaves as expected.
6. With the traffic from 4, do a cluster tier upgrade (e.g. M20 to M30). Expected: similar behavior as 5. Actual: function can't contact cluster for about 8 to 10 minutes if the function is deployed as a Windows Function or indefinitely if deployed as a Docker (containerized) function.

Request: driver should be resilient to Atlas Azure cluster tier upgrades.


Generated at Wed Feb 07 21:44:49 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.