[COMPASS-2928] One set of incorrect Atlas connection details affects later attempts to connect Created: 06/Jun/18  Updated: 29/Oct/23  Resolved: 27/Sep/18

Status: Closed
Project: Compass
Component/s: Compass
Affects Version/s: None
Fix Version/s: 1.16.0

Type: Bug Priority: Major - P3
Reporter: Matthew Javaly Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: replica-set
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

When trying to connect to the Atlas cluster for M001 (connection details in the lesson text), I was able to successfully connect using the given credentials.

When I tried to reproduce a student's issue by connecting without a RS name, I got this error:

An error occurred while loading navigation: 'not master and slaveOk=false': It is recommended to change your read preference in the connection dialog to Primary Preferred or Secondary Preferred or provide a replica set name for a full topology connection.

It was clear that I (and the student) needed to specify the name of the replica set. But when I added the RS name back to Compass, I received the same error. Every attempt after the first failed attempt was a failure as well. It didn't successfully connect again until I restarted Compass, so I think it's caching something about the failed attempt.

I am using version 1.13.1, the one currently on the Compass downloads page.



 Comments   
Comment by Durran Jordan [ 27/Sep/18 ]

Fixed in 1.16 beta series out now.

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