Uploaded image for project: 'Compass '
  1. Compass
  2. COMPASS-2928

One set of incorrect Atlas connection details affects later attempts to connect

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 1.16.0
    • Compass

    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.

      Attachments

        Activity

          People

            Unassigned Unassigned
            matt.javaly@mongodb.com Matthew Javaly
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: