Using Azure functions with Azure Atlas cluster, tier upgrade makes function unresponsive

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Cannot Reproduce
    • Priority: Major - P3
    • None
    • Affects Version/s: 2.9.3
    • Component/s: None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            James Kovacs
            Reporter:
            Francisco Alanis
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: