Uploaded image for project: 'C# Driver'
  1. C# Driver
  2. CSHARP-2631

Several MongoConnectionException's per hour in production backend logs

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 2.7.3
    • Component/s: Connectivity
    • None
    • Environment:
      Azure, VM Windows Server Datacenter 2019, Net Core Runtime 2.2.3.27414
      MongoDB Atlas M30 ReplicaSet.

      Hello!

      In production backend logs I see permanent exceptions (around 10 per hour) like this:
      https://pastebin.com/PFbdZUug

      ```
      MongoDB.Driver.MongoConnectionException: An exception occurred while receiving a message from the server. MongoDB.Driver.MongoConnectionException: An exception occurred while receiving a message from the server.  System.IO.IOException: Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.  System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond\r\n    End of inner exception stack trace 
      ```

      If I correctly understood, for clients this exception looks like 500 http error.
      In test environment, this error not reproduced.

      In atlas replica set logs, nothing like MongoConnectionException's or any other connection problem.

      Could you describe this behavior of mongodb C# driver and suggest a workaround for these situations?

      If you need any metrics, I could share atlas monitoring charts or something else if you need it.

            Assignee:
            wan.bachtiar@mongodb.com Wan Bachtiar
            Reporter:
            t.myagkikh Timofey Myagkikh
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: