[COMPASS-3556] querySrv ETIMEOUT when connecting to Atlas with SRV Created: 08/Apr/19  Updated: 04/Jul/20  Resolved: 27/Jan/20

Status: Closed
Project: Compass
Component/s: Connectivity
Affects Version/s: 1.17.0
Fix Version/s: 1.20.4

Type: Bug Priority: Minor - P4
Reporter: Nic Cottrell Assignee: Lucas Hrabovsky (Inactive)
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

MacOS 10.14.3


Attachments: PNG File Screen Shot 2019-04-08 at 16.26.19.png    
Issue Links:
Related

 Description   

I've just had a problem with Compass connecting to an Atlas cluster. It appears to be related to some sort of DNS caching (either as macOS or inside Compass itself).

The steps:

  1. Try to connect to Atlas via a SRV record, after ~20 seconds I get querySrv ETIMEOUT _mongod._tcp.<CLUSTER>.mongodb.net (see screenshot)
  2. Tested via Mongo shell and SRV and can connect fine
  3. Tried different Wifi networks, no change
  4. Restarted Compass and used the same Favourited settings, and can connect now.

The Atlas cluster is an M0, and we checked the logs. Only interesting entries were that the cluster was hitting weekly bandwidth limits and was being throttled.

I also changed the password via the Atlas UI today, so it's possible that somehow that got Compass into an unstable state.
 

 



 Comments   
Comment by shaan bhattacharya [ 04/Jul/20 ]

Is there any solution to it?

I'm facing the same issue ...
Can we reopen the bug??
@Lucas

 

Comment by Massimiliano Marcon [ 27/Jan/20 ]

The entire connect stack and driver has been updated in 1.20. I am going to assume this issue is gone.

Comment by Jan Krystufek [ 23/Aug/19 ]

I have the same issue with 1.18.0 on Windows 10.

Generated at Wed Feb 07 22:33:33 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.