Uploaded image for project: 'Node.js Driver'
  1. Node.js Driver
  2. NODE-2946

readPreference is ignored

    • Type: Icon: Bug Bug
    • Resolution: Works as Designed
    • Priority: Icon: Critical - P2 Critical - P2
    • None
    • Affects Version/s: 3.6.1, 4.0.0
    • Component/s: Shell
    • None

      It seems there has been a regression when going from v3.5 to v3.6 of the driver in terms of supporting readPreference. No matter what read preference I specify in the connection string, I always end up on the primary.

      This remains a problem with v4.0 of the driver.

      This is a problem for mongosh because users can't connect to a secondary or analytics node in Atlas as they would expect (see MONGOSH-487).

            Assignee:
            eric.adum@mongodb.com Eric Adum (Inactive)
            Reporter:
            massimiliano.marcon@mongodb.com Massimiliano Marcon
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: