Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-8695

different criteria used for determining slaveOk connection in parallel cursor code and Replica set code

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: Internal Client
    • None
    • Fully Compatible
    • ALL
    • Sharding 2017-03-27, Sharding 2017-08-21
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      ... the parallel cursor code assumes the slaveOk option is set, while the criteria is now more complex (dbclient_rs.cpp::_isQueryOkToSecondary).

      If the slaveOk option is set, the parallel cursor assumes it is ok if the primary is unavailable for a version check, since the query may go to an unversioned secondary in any case. However, other queries/commands that go to secondaries are missed in this check.

            Assignee:
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            Reporter:
            greg_10gen Greg Studer (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: