Don't consider readPreference "primary" as equivalent to 'slaveOk' in OP_QUERY find path

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 3.6.4, 3.7.2
    • Affects Version/s: 3.0.15, 3.2.17, 3.4.10, 3.6.0-rc1
    • Component/s: Querying
    • None
    • Fully Compatible
    • ALL
    • v3.6
    • Query 2018-01-29
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      In db/query/find.cpp, we check if it's safe to serve the current read, but we pass the value of slaveOk based on whether there is any readPrefernce provided, rather than checking that the read preference is not "primary". This could potentially allow queries run via this path to execute against a secondary, even if they were run with the "primary" read preference.

            Assignee:
            Bernard Gorman
            Reporter:
            Spencer Brody (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: