Timeout when selecting a server after inactivity

FrankNielsen · 2022-02-27T15:53:32.249Z

Thx for the reply, it was worth waiting for.

I have looked around your Jira but i am unable to find any roadmap for the v2.15.0 release, can you reveal anything - is it within weeks or months?

Cheers, Frank

James_Kovacs · 2022-03-01T22:33:08.921Z

Hi, @FrankNielsen,

Glad that I could be of assistance. We are wrapping up some features that we want to include in the 2.15.0 release. Insert usual disclaimer about forward-looking statements, plans could change due to unforeseen circumstances, etc., etc. With that said, the 2.15.0 release is weeks away, not months, though I don’t know for sure exactly when.

James

Yogesh_Satpute · 2022-04-07T06:05:23.011Z

Hello,

Is there a fix for this issue? I am also facing the same issue. I am using AWS + DocumentDB + SSH Tunnel. When I trying to connect to

Document DB from MongoDBCompass from my local laptop it works.
When I use AWS Ubuntu EC2 for tunneling from my local laptop, I could see DocumentDB shell and I can execute the commands as well.

However when I try to connect to AWS DocumentDB from .Net application, I get below exception. I am using the same connection string in Compass and .Net code.

A timeout occurred after 30000ms selecting a server using CompositeServerSelector{ Selectors = MongoDB.Driver.MongoClient+AreSessionsSupportedServerSelector, LatencyLimitingServerSelector{ AllowedLatencyRange = 00:00:00.0150000 }, OperationsCountServerSelector }. Client view of cluster state is { ClusterId : “1”, ConnectionMode : “Direct”, Type : “Unknown”, State : “Disconnected”, Servers : [{ ServerId: “{ ClusterId : 1, EndPoint : “Unspecified/documentdb-test.cluster-c7jldipe45vl.ap-south-1.docdb.amazonaws.com:27017” }”, EndPoint: “Unspecified/documentdb-test.cluster-c7jldipe45vl.ap-south-1.docdb.amazonaws.com:27017”, ReasonChanged: “NotSpecified”, State: “Disconnected”, ServerVersion: , TopologyVersion: , Type: “Unknown”, HeartbeatException: “MongoDB.Driver.MongoConnectionException: An exception occurred while opening a connection to the server. —> 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 172.31.27.19:27017
at System.Net.Sockets.Socket.Connect(IPAddress[] addresses, Int32 port)
at System.Net.Sockets.Socket.Connect(String host, Int32 port)
at MongoDB.Driver.Core.Connections.TcpStreamFactory.Connect(Socket socket, EndPoint endPoint, CancellationToken cancellationToken)
at MongoDB.Driver.Core.Connections.TcpStreamFactory.CreateStream(EndPoint endPoint, CancellationToken cancellationToken)
at MongoDB.Driver.Core.Connections.SslStreamFactory.CreateStream(EndPoint endPoint, CancellationToken cancellationToken)
at MongoDB.Driver.Core.Connections.BinaryConnection.OpenHelper(CancellationToken cancellationToken)
— End of inner exception stack trace —
at MongoDB.Driver.Core.Connections.BinaryConnection.OpenHelper(CancellationToken cancellationToken)
at MongoDB.Driver.Core.Connections.BinaryConnection.Open(CancellationToken cancellationToken)
at MongoDB.Driver.Core.Servers.ServerMonitor.InitializeConnection(CancellationToken cancellationToken)
at MongoDB.Driver.Core.Servers.ServerMonitor.Heartbeat(CancellationToken cancellationToken)”, LastHeartbeatTimestamp: “2022-04-07T05:48:53.4181477Z”, LastUpdateTimestamp: “2022-04-07T05:48:53.4241461Z” }] }.

Pleas help.

Thanks,
Yogesh

FrankNielsen · 2022-04-07T08:59:37.704Z

A short follow up, since mognodb driver release v2.15.0 we have not experienced any problems running with the SRV connection string format.

Cheers, Frank

PS: @Yogesh_Satpute i think your problem is a general first time connection problem!?

Developer_BB · 2022-08-04T08:45:55.646Z

The exception is there while using 2.17.1 version of the driver, and following the connection string format given by Atlas MongoDB (by checking the Connect->Connect from Application option). I am also trying to get a solution for this exception.
Following is the exception:
A timeout occurred after 30000ms selecting a server using CompositeServerSelector{ Selectors = MongoDB.Driver.MongoClient+AreSessionsSupportedServerSelector, LatencyLimitingServerSelector{ AllowedLatencyRange = 00:00:00.0150000 }, OperationsCountServerSelector }. Client view of cluster state is { ClusterId : “1”, Type : “Unknown”, State : “Disconnected”, Servers : }.

In this exception it is mentioned that the type is unknown, state is disconnected, server list is empty etc). The servers etc are not mentioned as part of the connection string which I obtained from the AtlasDB->Connect option. I do not know how to proceed and what to do at the moment.

Yaroslav_Vasilenko · 2022-08-05T11:17:52.687Z

Hello, we also use the 2.17.1 version and have the same problem.

James_Kovacs · 2022-08-05T19:04:52.575Z

Some things to check:

Are you able to connect via mongosh or another driver?
If mongodb+srv:// is failing, are you able to connect via the mongodb:// style connection string?
Have you verified that your network allow list includes your app server (or workstation)?
Are you using AWS PrivateLink or similar technology? If so, have you tried disabling it and connecting? (Not saying you shouldn’t use PrivateLink, but trying to isolate whether the problem is with your network configuration or something else.)

Given this sounds like a network connectivity/configuration issue rather than a driver bug, I would recommend reaching out to our Atlas Support Team by clicking the in-app chat icon in the lower right corner of MongoDB Atlas.

Sincerely,
James

Yilmaz_Durmaz · 2022-08-06T09:45:34.323Z

Anytime a “timeout” error occurs, the first thing to check should be the “network access” control on the server. Most of the time, a timeout is related to an improperly set IP list. to test this possibility, login to your Atlas cluster (or find your private server config files) and head to the security section to allow access from anywhere and test the app that way. also check other security settings so you can at least connect with mongo or mongosh from console, or with Compass.

Next is the IP address of the host pc of the application. Having a static domain name does not guarantee having a static IP. your cloud provider might be changing the IP address of the host where your app resides if you don’t have a static IP subscription. they are, after all, virtual PCs or containers and will most possibly be restarted with different IP addresses regularly (disaster recovery, load balancing, etc.). If you have set strict network access in your MongoDB server, then your app will have no chance but give a timeout. In case you host the app on a PC in your own infrastructure, then make sure you give static IP to that PC.

if you can eliminate these two possibilities, please add these details to your posts so help can find you faster.

Developer_BB · 2022-08-08T06:03:06.390Z

The IP is given as 0.0.0.0 inside Atlas Mongo DB network access option.
I can not set static ip because of work place restrictions. Also there are no proxy settings enforced.
The strange thing now is that the access to MongoDB in Atlas is possible since Friday. There has been no changes in the source code, it is the same as when I posted the issue in this forum. It is all strange to me. Does it have anything to do with the fact that I am using shared/free server/cluster option hosted somewhere, and there could be network congestion due to multiple requests from different places to this setup?

Yilmaz_Durmaz · 2022-08-08T11:17:06.984Z

“access anywhere” kinda removes all restrictions but there are still many ways to cripple the network access on the app side (before finally blaming a driver). your app seems to work now but may stop again, so best to understand where else the network may diverge expectations. unfortunately, it is like debugging a program and it won’t be apparent immediately what causes the problem.

you have said “since Friday”, can you please test your app today/tomorrow again!? it now is pretty possible that your network has a week-long restriction on ports so employees would not surf distracting websites. If your app will again give timeouts today and tomorrow, you need to speak to your administration.

Developer_BB · 2022-08-08T11:33:40.840Z

Thank you for the reply.
There was no intention to blame anything or anyone, thought this was a support forum.
I already explained there are IT restrictions as per company policy, but do not know up to what extent and where all those restrictions are. Had I known, then I did not have to think much.

I close my further communication on this topic here.

Yilmaz_Durmaz · 2022-08-08T11:57:38.750Z

@Developer_BB Please take a breath first. I am sorry you have offended, but I had/have no intention to offend anyone here.

I do not have any way to test your own app and infrastructure on-premise, so I was trying to say what else you can test. we need to first eliminate probable causes, then check for unexpected ones.

Veerakondalu_Pallati · 2022-12-04T13:58:13.639Z

Have you resolved this issue. I have struggling to find solution for this.
I am facing the same issue in aws lambda. Please find the details below:

Application details: .NET Core application (lambda). .NET mongodb driver (2.18.0), Serverless mongodb instance.

Personal Laptop or Local environment
I have .NET core lamda application and was not working, so I changed DNS to google. It started working in local laptop.

Deployed Lambda function
When I deployed the application to aws lambda, it is not working. I have added DataAccess and network access also in Atlas.

I tried to connect to serverless using mongosh in Cloud 9 machine from the same VPC where lambda is condfigured. I am able to connect to serverless instance.

Please help me why I am unable to connect to Serverless mongo instance from lambda.

Please let me know if you need more details.
@James_Kovacs

Veerakondalu_Pallati · 2022-12-04T14:00:13.678Z

Have you find the solution for this problem?

Johann_Sigurdsson · 2023-11-16T16:55:36.138Z

I’ve been struggling with this for months now. Finally got it working locally.

My company has an AWS hosted MongoDB Atlas cluster which I’m connecting to via office VPN, and I’m running an ASP.NET 6 web application with version 2.22.0 MongoDB C# driver.

Connecting from my local MongoDB Compass to the Atlas cluster? No problem.
Connecting from my local application to a locally running MongoDB server? No problem.
Connecting from my local application to the Atlas cluster? Random and frequent server selection timeout failures during initialization, followed by pretty smooth performance after the application successfully breaks through during a re-attempt.

The problem doesn’t seem to be affecting our production environment. That or my logging configuration is way worse than I thought.

Anyway, I re-configured my local user secrets to use the legacy “2.4 or later” connection string format obtained from Atlas (the one without “+srv” in it). I’m no longer experiencing poor initialization performance when running my app locally.

Working connection string format:

mongodb://username:password@shard1hostname:27017,shard2hostname:27017,shard3hostname:27017/?ssl=true&replicaSet=replicaSetName&authSource=admin&retryWrites=true&w=majority

Hope this helps someone. Good luck.

Hermann_Baumgartl · 2023-11-22T11:34:12.408Z

We are facing the same issue with a WPF app on .net Framework 4.7.2 with MongoDB C# driver 2.22.0.

Connection from Compass or Studio3T works
Connection from our Python apps works
Connecting to a local MongoDB works
Connecting from our WPF application to our Atlas clusters randomly works.

Best case the initialization of a new MongoClient() takes about 15s, but then the connection works. Sometimes the new MongoClient() takes about 400ms but then the first query to the cluster raises an error:

System.TimeoutException
  HResult=0x80131505
  Message=A timeout occurred after 30000ms selecting a server using CompositeServerSelector{ Selectors = ReadPreferenceServerSelector{ ReadPreference = { Mode : Secondary } }, LatencyLimitingServerSelector{ AllowedLatencyRange = 00:00:00.0150000 }, OperationsCountServerSelector }. Client view of cluster state is { ClusterId : "2", ConnectionMode : "ReplicaSet", Type : "ReplicaSet", State : "Disconnected", Servers : [] }.
  Source=MongoDB.Driver.Core

The error seems to be mostly unaffected by cluster size (M10, M40 and M50 tested).
The workaround by @Johann_Sigurdsson works for now, however this needs fixing.

James_Kovacs · 2023-11-24T01:29:18.714Z

Hi, @Johann_Sigurdsson and @Hermann_Baumgartl,

I understand that you’re having connectivity problems when using mongodb+srv:// connection strings. The .NET/C# Driver resolves the associated SRV and TXT records and then resolves the hostnames returned from the SRV response. (The TXT record contains additional options such as replicaSet, authSource, and loadBalanced.) Under the hood, the driver relies on DnsClient.NET to resolve SRV and TXT records and relies on the OS’s DNS resolver for FQDN resolution.

Examining the TimeoutException, I can see that Servers : [], which means that the topology is empty. This can occur if the replica set name in the TXT record does not match the replica set name returned during heartbeats. You can view the replica set name in the TXT record via:

dig -t TXT CLUSTERNAME.PROJECTID.mongodb.net

For example, if your connection string is mongodb+srv://user:pwd@my-cluster-name.9zzzz.mongodb.net/?retryWrites=true&w=majority, then you can run the following command to find the associated TXT record:

dig -t TXT my-cluster-name.9zzzz.mongodb.net

When you connect to your cluster using mongosh, you can run db.hello() to manually heartbeat with a cluster node. This will return the replica set name as setName.

The replica set name in the TXT record must match the replica set name returned by cluster members. If your connection string says that you’re connecting to replicaSet=atlas-abc123-shard-0 but the nodes say that they’re part of setName:atlas-xyz987-shard-0, then those nodes will be removed from the topology since they belong to the wrong replica set.

Replica set names are configured automatically in Atlas and are not modifiable by users. They are also not updated after cluster creation. Thus it is unexpected that the replica set name in the TXT record and returned by the cluster members would differ.

There are other edge case scenarios where a misconfigured cluster can result in an empty topology, but these misconfigurations aren’t possible in Atlas. These scenarios would require reusing hostnames for new clusters, which Atlas does not do.

I have attempted to reproduce the reported behaviour but have so far been unsuccessful in observing the problem. If you have a self-contained repro that reproducibly elicits the behaviour, I would be happy to investigate further. Thanks in advance for any additional information that you can provide.

Sincerely,
James

Hermann_Baumgartl · 2023-11-24T09:58:16.177Z

Hi, @James_Kovacs

at least for our application, the error cannot be reproduced with 100% “success” rate. In our app the MongoClient is created when the user activates a certain UserControl as singleton. Usually the creation of the MongoClient is slow (about 30s), but the queries work. If it takes 30s the connection/client works. If the new MongoClient(connectionString) takes less than 1s, it is safe to say that the first query throws an TimeoutException. However, we can reproduce the error reliably by closing the app, wait for 1 minuten and opening the app again. It’s a ~15% chance of getting the error within 10 minuten.

I reproduced the error and followed your instructions on comparing the TXT record and the db.hello() response. setName from db.hello() and the replicatSet from nslookup are the same.

We also opened a support case, where we could share some more information including an example of the code used. The case number is: 01225910. I also attached a minimum example to reproduce the error in this case.

Best regards,
Hermann

James_Kovacs · 2023-11-24T17:14:51.979Z

Hi, @Hermann_Baumgartl,

Thank you for reproducing the problem and checking the replica set name in the TXT record and from the heartbeat.

The cold start time for a MongoClient is on the order of a few hundred milliseconds. This includes DNS lookups, establishing monitoring connections to cluster members, and creating an authenticated connection in the connection pool. So it is unexpected that MongoClient creation would take around 30 seconds.

When the creation is fast (<1s), I would not expect a timeout exception to be thrown either. The MongoClient will block discovering the cluster topology while performing server selection so that the operation can be routed to the correct node.

This is definitely worth digging into deeper and opening a support case is the right way to go. Our Support Team will loop in the .NET/C# Team as needed during the investigation.

Sincerely,
James

Willis_Chou1 · 2024-04-21T10:52:38.673Z

Hi, @James_Kovacs
I am facing the same issue but haven’t found a solution so far. Could you please share more information with the community? Thank you!